Re: [jetty-users] IllegalArgumentException: Java in XmlConfiguration

[Jan Bartel <janb@xxxxxxxxxxx>]

Hi,

There's not enough to go on here. I would run jetty in dry-run mode to see the kind of command line that would be generated to check which xml files will be parsed and in what order ( java -jar $JETTY_HOME/start.jar --dry-run ). Then I'd make sure that you've got startup debug turned on (use  --debug option), see what it says. You should be able to get a line-number out of the xml parser as to what it's parsing.

If you want more eyeballs on it, then I'd post the (sanitized if necessary) output from all of the above.

Jan

On Fri, 25 Oct 2024 at 09:31, Shan Parikh via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

Hi, 

I am currently running Jetty 11 and looking to upgrade to Jetty 12 because of the upcoming end of life for Jetty 11 in Jan 2025. 

I’ve currently upgraded the Jetty home directory to contain the new files, and upgraded the modules we add accordingly: 

--add-modules=server,ee10-deploy,ee10-webapp,https,ssl,session-cache-hash,rewrite,ssl-reload,session-store-file,ext,logging-jetty,console-capture,jaas,inetaccess

However, I am seeing an IllegalArgumentException on ‘Java’ when trying to run the webserver. 

2024-10-24 14:49:12.715:DEBUG:oejx.XmlConfiguration:main: XML {jetty.deploy.defaultsDescriptor=/webserver/jetty-1.12.0.12/jetty_home/etc/webdefault-ee10.xml, jetty.deploy.containerScanJarPattern=.*/jakarta.servlet-api-[^/]*\.jar$|.*jakarta.servlet.jsp.jstl-.*\.jar$, jetty.deploy.webInfScanJarPattern=null, jetty.deploy.servletContainerInitializerExclusionPattern=null}.put(jetty.deploy.servletContainerInitializerExclusionPattern,null) 2024-10-24 14:49:12.715:DEBUG:oejx.XmlConfiguration:main: XML {jetty.deploy.servletContainerInitializerOrder=null, jetty.deploy.defaultsDescriptor=/webserver/jetty-1.12.0.12/jetty_home/etc/webdefault-ee10.xml, jetty.deploy.containerScanJarPattern=.*/jakarta.servlet-api-[^/]*\.jar$|.*jakarta.servlet.jsp.jstl-.*\.jar$, jetty.deploy.webInfScanJarPattern=null, jetty.deploy.servletContainerInitializerExclusionPattern=null}.put(jetty.deploy.servletContainerInitializerOrder,null) 2024-10-24 14:49:12.715:DEBUG:oejuc.ContainerLifeCycle:main: DeploymentManager@7a4ccb53 added {class org.eclipse.jetty.deploy.providers.ContextProvider@7b02881e[file:///webserver/jetty-1.12.0.12/jetty_base/webapps/],MANAGED} 2024-10-24 14:49:12.715:WARN :oejx.XmlConfiguration:main: Unable to execute XmlConfiguration java.lang.IllegalArgumentException: Java at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:2011) Exception in thread "main" java.lang.IllegalArgumentException: Java at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:2011)

The last XML we see parsed is 

2024-10-24 14:49:12.706:DEBUG:oejx.XmlConfiguration:main: Parsing xml file /webserver/jetty-1.12.0.12/jetty_home/etc/jetty-ee10-deploy.xml

However, both this XML and the last XML mentioned (webdefault-ee10.xml) are part of the Jetty code. 

I understand that there will be code changes necessary to adopt Jetty 12, but it seems that I'm not even getting to the point where I run our server code. 

Are there any deployment steps I could be missing that might help with this issue? 

Thanks, 

Shan Parikh

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users

--

Jan Bartel <janb@xxxxxxxxxxx>

www.webtide.com
Expert assistance from the creators of Jetty and CometD