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
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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