Java upgrade from Java11 to Java 17

s.p...@gmail.com

unread,

Aug 16, 2024, 2:26:06 PMAug 16

to Jenkins Users

After upgrading Java to Java 17 Jenkins is not working. Upgraded all the plugins as well. It is installed on windows server .The service is looping between start and stop. Jenkins is not coming up.

Version: Jenkins 2.452.3

Mark Waite

unread,

Aug 16, 2024, 2:34:17 PMAug 16

to Jenkins Users

On Friday, August 16, 2024 at 12:26:06 PM UTC-6 you wrote:

After upgrading Java to Java 17 Jenkins is not working. Upgraded all the plugins as well. It is installed on windows server .The service is looping between start and stop. Jenkins is not coming up.

Version: Jenkins 2.452.3

I'm sorry to hear that. In order for others to help you, they'll need much more information than "Jenkins is not working". "How to report an issue" describes the type of information that is needed so that others can help you.

Mark Waite

s.p...@gmail.com

unread,

Aug 16, 2024, 2:51:08 PMAug 16

to Jenkins Users

Sorry Mark, if I'm not clear. I updated the Java path in Jenkins.xml to Java17 and restarted Jenkins from the Windows service. However, the service automatically starts and stops Jenkins. When I try to access the Jenkins application it throws a message that, the site is unreachable. When the Java path is reverted to Java 11, it works fine.

Mark Waite

unread,

Aug 16, 2024, 3:11:21 PMAug 16

to Jenkins Users

On Friday, August 16, 2024 at 12:51:08 PM UTC-6 you wrote:

Sorry Mark, if I'm not clear. I updated the Java path in Jenkins.xml to Java17 and restarted Jenkins from the Windows service. However, the service automatically starts and stops Jenkins. When I try to access the Jenkins application it throws a message that, the site is unreachable. When the Java path is reverted to Java 11, it works fine.

You've now provided another bit of information describing things that you did. You updated the Java path in jenkins.xml to Java 17 and restarted the Windows service. That's not nearly enough information for others to suggest steps that you can take to resolve the issue. The page that I included in the first link says:

The Description should be comprehensive to allow others to understand the problem or improvement request immediately. A few suggestions on what to include (again, mostly applicable to bug reports):

Did the issue occur after an upgrade of Jenkins or any plugins? If so, what was/were the previous version(s), what is/are the current version(s)? Does downgrading resolve the issue? For plugins, the previous versions can often be seen in Plugin Manager (where it offers to downgrade to the previous version).
Include log output and stack traces of error messages from the UI or any client programs.
Provide a complete step-by-step description of how to reproduce the problem. We cannot see your screen, so be comprehensive. Consider switching the Jenkins UI to English by changing your web browser’s configuration to get the labels right.
If possible, provide information on the circumstances the issue occurs with (or doesn’t), e.g. "only when starting the agent via SSH", "only when using Tomcat as container", etc. – this may be some work, but it’ll make reproducing and fixing the issue much easier!
Does the issue occur with a new Jenkins installation not reusing any old configuration or data? Try to reproduce the problem with a pristine Jenkins installation with as little customization as possible.

You didn't include log output. What do the Windows log messages report that describe why the service started and then stopped?

You didn't include a step-by-step description of how to reproduce the problem.

You didn't provide details of the circumstances where the problem occurs. For example, what is the exact path of the Java 17 installation that you've placed in the jenkins.xml file? What are the other contents of the jenkins.xml file?