Maven2-moduleset error

Hi, I just updated my Jenkins version from 2.401.3 to 2.426.3 and along with that I also updated some of the plugins. Since I have some certification issue I placed the downloaded .jpi plugin manually and started the jenkins. In the jenkins.err.log, I’m getting below error. The jobs were created using Maven integration plugin 3.17 and I have updated them to 3.23. This is kind of blocking taking more time to start up jenkins(5+ hours and still starting) as there too many jobs.

SEVERE	jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading item Demo_SanityTest-FLOW1
com.thoughtworks.xstream.mapper.CannotResolveClassException: com.tikal.jenkins.plugins.multijob.MultiJobProject
	at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:81)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:452)
	at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:46)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:47)
	at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:135)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1464)
	at hudson.util.XStream2.unmarshal(XStream2.java:230)
	at hudson.util.XStream2.unmarshal(XStream2.java:201)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1441)
	at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1330)
	at hudson.XmlFile.read(XmlFile.java:165)
Caused: java.io.IOException: Unable to read D:\JenkinsData\Jenkins\jobs\Demo_SanityTest-FLOW1\config.xml
	at hudson.XmlFile.read(XmlFile.java:167)
	at hudson.model.Items.load(Items.java:375)
	at jenkins.model.Jenkins$13.run(Jenkins.java:3513)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:177)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:305)
	at jenkins.model.Jenkins$5.runTask(Jenkins.java:1170)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:221)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

The class com.tikal.jenkins.plugins.multijob.MultiJobProject is from the plugin Multijob
I assume you have somewhere in the logs of Jenkins earlier some error that this plugin couldn’t be loaded. Check that error and fix it.

1 Like

Thanks for the response. That really helps. Also, I checked the older logs which I had in a backup folder and didn’t notice any error. I had also updated the plugin version of Multijob along with others. I will try downgrading the version to see how it works.

Also, is it fine if I remove the plugin. I’m not sure if I am using this plugin and don’t see any trace of it in config.xml under each jobs.

you definitely have jobs that are based on that plugin otherwise you wouldn’t see the error in the logs.

1 Like

Also, noticing this error. previous issue was minimal but this was the major one causing issue.

2025-03-13 23:15:42.603+0000 [id=54]	SEVERE	jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading item Demo_Test_Master
com.thoughtworks.xstream.mapper.CannotResolveClassException: maven2-moduleset
	at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:81)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:452)
	at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:46)
	at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:125)
	at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:47)
	at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:135)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1464)
	at hudson.util.XStream2.unmarshal(XStream2.java:230)
	at hudson.util.XStream2.unmarshal(XStream2.java:201)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1441)
	at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1330)
	at hudson.XmlFile.read(XmlFile.java:165)
Caused: java.io.IOException: Unable to read D:\Jenkins\Jenkins\jobs\Demo_Test_Master\config.xml
	at hudson.XmlFile.read(XmlFile.java:167)
	at hudson.model.Items.load(Items.java:375)
	at jenkins.model.Jenkins$13.run(Jenkins.java:3513)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:177)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:305)
	at jenkins.model.Jenkins$5.runTask(Jenkins.java:1170)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:221)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

Also, noticed the maven2-moduleset in my config.xml files. is it something related to plugin dependency ?

As you wrote you manually installed the plugins and your Jenkins is 2.426.3 which is over 1 year old it might be that you downloaded the plugins which are too new for your Jenkins and thus can’t be loaded. Due to the requirement for Java 17 and the switch to EE9 with 2.479.x a lot of plugins have been updated to require at least this Jenkins version so you can’t just download the latest hpi/jpi from Jenkins home page and install this.
You should also see under Manage Jenkins when plugins couldn’t be loaded and why.

1 Like

Yeah, thanks for that. Noticed lot of dependency errors in that screen. Currently downgrading as suggested. Will update how it goes. worst part is it took almost 10+ hours to start jenkins