[OPENEJB-999] ClassNotFoundException when deploying openejb.war

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1
• Fix Version/s: 3.2, 4.0
• Environment: Tomcat 6.0.18 under Windows XP; The same with Tomcat 5.5, didn't test other versions.; Java version: 1.6.0_11-b03 ; OpenEJB version: 3.1 (not tested with 3.0)
• Assignee: Jonathan Gallimore
• Reporter: Alberto López
• Created: 13/Feb/09 14:56
• Updated: 29/Jun/11 13:25
• Resolved: 29/Jun/11 13:25

Description

When deploying the openejb .war for Tomcat the following Exception is thrown:

OpenEJB init-params:
java.lang.ClassNotFoundException: org.apache.openejb.tomcat.loader.TomcatHook
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
at org.apache.openejb.tomcat.loader.TomcatEmbedder.embed(TomcatEmbedder.java:71)
at org.apache.openejb.tomcat.loader.LoaderServlet.init(LoaderServlet.java:44)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1172)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:992)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4058)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4371)
at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3099)
at org.apache.catalina.manager.ManagerServlet.reload(ManagerServlet.java:916)
at org.apache.catalina.manager.HTMLManagerServlet.reload(HTMLManagerServlet.java:536)
at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)

After some research it seems that this may be related to the Tomcat installation path:

Aparently it occurs when the is an "+" character on the path

Under exactly the same conditions, a Tomcat installation on the first path fails, while a similar installation on the second path works fine:

C:\Desarrollo\Libs+Tools\Apache\Tomcat-6.0.18\webapps

This one works fine: C:\Archivos de programa\Desarrollo\Tomcat-6.0.18