[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] Old war file doesn't work with new jetty
|
Hi,
On Wed, May 17, 2017 at 6:14 PM, Hoffman, Richard D.
<RDHoffman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Thanks for your help. Here is the stack trace. Would it also help to see the .xml configuration file?
>
> 2017-05-17 12:11:01.049:INFO:oejs.Server:main: jetty-9.2.21.v20170120
> 2017-05-17 12:11:01.067:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/usr/local/jetty-distribution-9.2.21.v20170120/webapps/] at interval 1
> 2017-05-17 12:11:01.114:WARN:oejx.XmlConfiguration:main: Config error at <New id="openiddb" class="org.eclipse.jetty.plus.jndi.Resource"><Arg/><Arg>jdbc/openid</Arg><Arg>|???<New class="com.mchange.v2.c3p0.ComboPooledDataSource"><Set name="driverClass">com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource</Set><Set name="JdbcUrl">jdbc:mysql://127.0.0.1:3306/openid</Set><Set name="User">zteam</Set><Set name="Password">C@llAdm1nAcct..</Set></New>|??</Arg></New> java.lang.ClassNotFoundException: com.mchange.v2.c3p0.ComboPooledDataSource in file:/usr/local/jetty-distribution-9.2.21.v20170120/webapps/openid.xml
> 2017-05-17 12:11:01.115:WARN:oejd.DeploymentManager:main: Unable to reach node goal: started
> java.lang.ClassNotFoundException: com.mchange.v2.c3p0.ComboPooledDataSource
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.jetty.util.Loader.loadClass(Loader.java:86)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:364)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:754)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.itemValue(XmlConfiguration.java:1125)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.value(XmlConfiguration.java:1030)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:775)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:423)
> at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:354)
> at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:262)
> at org.eclipse.jetty.deploy.providers.WebAppProvider.createContextHandler(WebAppProvider.java:287)
> at org.eclipse.jetty.deploy.App.getContextHandler(App.java:101)
> at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:36)
> at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
> at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
> at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
> at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
> at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:461)
> at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
> at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:609)
> at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
> at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
> at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
> at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1255)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.jetty.start.Main.invokeMain(Main.java:321)
> at org.eclipse.jetty.start.Main.start(Main.java:817)
> at org.eclipse.jetty.start.Main.main(Main.java:112)
> 2017-05-17 12:11:01.392:INFO:oejs.ServerConnector:main: Started ServerConnector@26be92ad{SSL-http/1.1}{0.0.0.0:443}
> 2017-05-17 12:11:01.393:INFO:oejs.Server:main: Started @4655ms
> 2017-05-17 12:11:11.379:INFO:oejs.ServerConnector:Thread-1: Stopped ServerConnector@26be92ad{SSL-http/1.1}{0.0.0.0:443}
Stack trace shows that the server is deploying your web application,
it is parsing a Jetty XML file that references the class you cannot
find, so it's the server that is trying to load that class.
Therefore, you must put the jar into the server classpath. It may have
been that hightide7 had the connection pool classes already in the
server classpath.
See http://www.eclipse.org/jetty/documentation/current/jndi-datasource-examples.html.
We recommend HikariCP rather than C3P0.
I also recommend that while you are upgrading, you go straight to
9.4.x rather than 9.2.x, unless you have to stay on JDK 7 (which also
is not recommended).
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
