Issue

Your controller installed in a Windows OS fails to restart with a stack trace compatible with the one shown below:

XXXX-XX-XX XXXX [id=XX] INFO jenkins.model.Jenkins#cleanUp: Jenkins stopped
XXXX-XX-XX XXXX [id=XX] WARNING h.s.HttpSessionContextIntegrationFilter2#hasInvalidSessionSeed: Encountered IllegalStateException trying to get a user. System init may not have completed yet. Invalidating user session.
XXXX-XX-XX XXXX [id=XX] WARNING o.e.jetty.server.HttpChannel#handleException: /tcpSlaveAgentListener/java.lang.IllegalStateException: Jenkins.instance is missing.

Environment

• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center
• CloudBees Jenkins Distribution
• Jenkins LTS

Resolution

This error has been reported in some versions of Jenkins, and has been discussed and solved in JENKINS-59992. The fix was included in Jenkins LTS 2.223.

So the proper fix for the issue is to upgrade to a version of the product which is higher than 2.223.

Workaround

The workaround is to manually restart the Windows service in order to get the instance successfully restarted.

Tested product/plugin versions

• CloudBees Jenkins Platform - Client controller 2.190.x.x