In ` Java – jar start After jar `, jetty throws an exception
•
Java
Run Java - jar start The following error occurred while installing jar The sudo service terminal started working well What seems to be the problem? The web application is not deployed, it is a new installation I have changed the / etc / default / jetty file to start the service
wissen12@wissen12:/usr/share/jetty$java -jar start.jar 7 [main] INFO org.mortbay.util.FileResource - Checking Resource aliases 396 [main] WARN org.mortbay.xml.XmlConfiguration - EXCEPTION java.lang.NoSuchMethodException: class org.mortbay.jetty.Server.setThreadPool(class org.mortbay.thread.QueuedThreadPool) at org.mortbay.xml.XmlConfiguration.set(XmlConfiguration.java:417) at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:231) at org.mortbay.xml.XmlConfiguration.newInstance(XmlConfiguration.java:198) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:880) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.mortbay.start.Main.invokeMain(Main.java:194) at org.mortbay.start.Main.start(Main.java:534) at org.mortbay.start.Main.start(Main.java:441) at org.mortbay.start.Main.main(Main.java:119)
thank you.
Solution
I have the same problem From jetty 7.1 X upgrade to 7.4 X solved it Looking at the source code, it seems that jetty's XML bean processing adds more fallbacks for imprecise type matching in setters
The content of this article comes from the network collection of netizens. It is used as a learning reference. The copyright belongs to the original author.
THE END
二维码