Unable start Jenkins after upgrading java version to 1.8.Jenkins 1.159.And facing below exception

258 views
Skip to first unread message

Divya Reddy

unread,
Feb 8, 2016, 1:58:07 AM2/8/16
to Jenkins Users
org.jvnet.hudson.reactor.ReactorException: hudson.util.IOException2: Unable to read C:\Users\support\.jenkins\config.xml
	at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
	at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
	at jenkins.model.Jenkins.executeReactor(Jenkins.java:904)
	at jenkins.model.Jenkins.<init>(Jenkins.java:804)
	at hudson.model.Hudson.<init>(Hudson.java:81)
	at hudson.model.Hudson.<init>(Hudson.java:77)
	at hudson.WebAppMain$2.run(WebAppMain.java:214)
Caused by: hudson.util.IOException2: Unable to read C:\Users\support\.jenkins\config.xml
	at hudson.XmlFile.unmarshal(XmlFile.java:170)
	at jenkins.model.Jenkins$16.run(Jenkins.java:2515)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: com.thoughtworks.xstream.converters.ConversionException: -1 : -1
---- Debugging information ----
message             : -1
cause-exception     : java.lang.ArrayIndexOutOfBoundsException
cause-message       : -1
class               : hudson.model.Hudson
required-type       : hudson.model.Hudson
converter-type      : hudson.util.RobustReflectionConverter
path                : /hudson/disabledAdministrativeMonitors
line number         : 3
version             : null
-------------------------------

Victor Martinez

unread,
Feb 8, 2016, 3:13:02 AM2/8/16
to Jenkins Users
Does C:\Users\support\.jenkins\config.xml file exist? Is that the same as It used to be? You can force the Jenkins Home location:

I hope it helps

Baptiste Mathus

unread,
Feb 8, 2016, 3:18:30 AM2/8/16
to jenkins...@googlegroups.com

Hi,
If you're actually using the 1.159 (and not 1.591 or something) version, then it's a known issue. And (most likely) will never be fixed on such an old Jenkins version (likely a typo though, would make roughly a 8/9 years old version)

In this case your only short term solution is to revert to the previous JDK as this version is *very* old (can't check exactly now).

Beware also that this is a many years old version so planning a Jenkins upgrade might be recommended. Head for LTS versions in that case.

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b60f9c04-8928-4009-84b3-121c0cc3f57b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Divya

unread,
Feb 8, 2016, 4:26:02 AM2/8/16
to Jenkins Users, m...@batmat.net
Thanks!!!.
Can you give me steps that to be followed while upgrading Jenkins as am very new to it.
Am using Jenkins.war file in normal local windows machine.

ThanksInAdvance

Gurusharan S

unread,
Feb 21, 2016, 12:01:36 PM2/21/16
to Jenkins Users, m...@batmat.net, div...@gmail.com
Hello Divya,

Since you are using a local war file for deployment, you can simply do the following:
1. Get the latest version of the war file from the official site or from the link that you see in the 'Manage Jenkins' page.
2. Stop your tomcat or whatever server you are running.
3. Replace the old jenkins.war with the new one.
4. Start the server.

Hope this helps.

Bye for now,
Gurusharan S.

BEDJAOUI DJOUNAYDI

unread,
Oct 23, 2017, 10:28:01 AM10/23/17
to Jenkins Users
Hello,

Stop the Jenkins server.
rename directory: C:\Users\support \.jenkins by C:\Users\support\.Old_jenkins
Replace the old jenkins.war with the new one
restart Jenkins .


Good luck.

Reply all
Reply to author
Forward
0 new messages