Hi all,
I am trying to start tomcat with Yourkit(2014 build 14098), and get the following error:
Sep 04, 2014 10:04:40 AM org.apache.catalina.startup.HostConfig deployDescriptor
SEVERE: Error deploying configuration descriptor C:\apache-tomcat-7.0.55\conf\Catalina\localhost\ROOT.xml
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1862)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
We are using the following descriptor, in order to connect to the database.
ROOT.xml
==========
<Context>
<Resource name="jdbc/EmployeeDB" auth="Container" type="javax.sql.DataSource"
maxActive="2000" maxIdle="10" maxWait="10000" validationQuery="SELECT 1" testOnBorrow="true"
username="root" password="admin" driverClassName="com.mysql.jdbc.Driver"
removeAbandoned="true" removeAbandonedTimeout="3000" logAbandoned="false"
url="jdbc:mysql://localhost:3306/test?autoReconnect=true"/>
</Context>
Any idea how to solve this ?
Thanks,
Eran.
Tomcat+YJP: deploy descriptor error
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Tomcat+YJP: deploy descriptor error
Hello Eran
We've answered by email.
In short: it seems we've found the problem, and the next build will fix it. We've sent you a download link of a new agent library with the proposed fix.
Best regards,
Anton
We've answered by email.
In short: it seems we've found the problem, and the next build will fix it. We've sent you a download link of a new agent library with the proposed fix.
Best regards,
Anton