Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

InvocationTargetException on FishEye

I just noticed that one of our FishEye instances throws HTTP 500 errors on image related requests.


javax.servlet.ServletException: java.lang.reflect.InvocationTargetException 
Could not initialize class javax.imageio.ImageIO



javax.servlet.ServletException: java.lang.reflect.InvocationTargetException
Could not initialize class org.jfree.chart.encoders.ImageEncoderFactory

On Tuesday the 5th I updated both instances from 4.8.1 to 4.8.2, I assume the problem appeared after the update.

The Log Analyzer doesn't find anything, the server log is not more helpful (can't post it here as it exceeds the maximum post length).

Where can I start to debug this further? 

1 answer

1 accepted

1 vote
Answer accepted
Moses Thomas Community Leader May 09, 2020

@Gerald Schneider  Since you have upgraded, you will need to add  the below in the block quote  if  you dont have  in   Environment variables 




Please give feed back.

Kind regards,


This solved the problem.

Maybe this option should be set directly in FishEye when it is necessary now?

Moses Thomas Community Leader May 12, 2020

Well it depends on how  you performed the upgrade, i also think that  if you do it via  the   installer,  in Windows you would need to un-install first  as stated here

Upgrading Fisheye on Windows   it is supposed to  be auto added.  In Unix like OS, I always extract new version installation  files  and see what changed  in the required files  and then add it to my existing file during upgrade  so that i don't miss any thing.

Well, that's exactly what I do. I extract the new version and make all necessary changes to the new files, I don't copy over files from the previous version.

Moses Thomas Community Leader May 12, 2020

@Gerald Schneider  Then it definitely has to do with the java  Open JDK  version that  you are using. Mostly likely the package is missing.

Setting the option works for me for java jdk8u242-b08. Doesn't seem to work for jdk8u252-b09, though. It really seems that the package is missing there.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

197 views 1 6
Read article

Atlassian Community Events