nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Use older JRE with newer JIRA? (6.4.11 w/ 1.8.0_40-b25)?

Stephen Hayden_r7pekc

We're having connection reset issues syncing w/ AD with 6.4.11 (w/ JRE 1.8.0_51-b16). Since we'd previously tested 6.4.9 we tried the JRE from that, 1.8.0_40-b25, and that solved our issue.

Is there a reason to be wary of using an older JRE with a newer instance, or can we move forward for now with this mix? I've got a support ticket in but asking the community so we can decide on our plans for the weekend upgrading our production instance.

The kb addressing this connection issue didn't help remedy the problem - https://confluence.atlassian.com/display/JIRAKB/JIRA+Connection+reset+error+when+synchronising+with+Active+Directory+2012r2

Thanks!

Accepted answers

Rodrigo Girardi Adami

Hi Stephen,

AFAIK, there is are no issues using an older JRE with the application. Usually we recommend to upgrade to the latest in order to resolve bugs, but sometimes the new versions may introduce new bugs too and we might need to downgrade the JRE in the process.