JIRA Users seing 'your java version is out of date' message

We have had some reports of some users seeing the message that their java version is out of date when they are using JIRA - why are they seeing this or is there any documentation to specify what their java version should be?  I see documentation for the server that JIRA is installed on but it doesn't mention end user machines to access JIRA?

2 answers

0 votes

It's probably around the screenshot functions - that needs java on the client machine rather than the JIRA server.

It's a Java warning rather than a JIRA one, it's all about the client.

Maybe, but why would the upgrade warning be shown during log in?

You believe it's because the user was taking screenshots and this is why they see this?

It's the only part of JIRA that I know that runs on the client side.  You won't get the error on the server side, other than a warning in the logs

Thanks Nick, they mention they are getting it when accessing the application or when they navigated to screen to change password so not sure they were taking screenshots but can ask.

do we know what version they should have for java client-side that works with this screenshot functionality?


Ah, authentication, it could be something to do with external authentications if you've got something outside JIRA that does it.  There are a couple of authentication products that claim to be compatible with JIRA, but aren't actually, and just do "password safe" type things.  If you're using one of them, and it's java based, that could also trigger the warning.  (There's also a possibility that you've got and add-on that runs some form of servlet on the client machine too - similar to the screenshot function that JIRA ships with, but if it's around password change, it's probably the authentication)

There is a common theme in those possibilities - something in JIRA is trying to get your client machines to run something in Java.  The warning comes because the client machine is out of date.

I have no idea what version you might need, because we don't know what is causing the call to run java on the client.

Thanks -All authentication is done in JIRA - we don't use LDAP.  JIRA is our master for our Confluence integration but no other plugins...

Well, that narrows it down, but I really don't know what could be triggering it now.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,166 views 5 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you