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!
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.
Cheers,
Rodrigo
You rock. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Stephen. You are welcome. Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hopefully this isn't the cause of my new problem :p https://answers.atlassian.com/questions/26643402/upgraded-from-service-desk-1.x-to-2.x---no-enhanced-people-tab-agent-management-screen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.