tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <knst.koli...@gmail.com>
Subject 5.5.x branch cannot run
Date Tue, 09 Jun 2009 13:14:51 GMT
I built TC 5.5 distributive from current tc5.5.x, and it is broken:

The tester app, that is run during building a release, returns status
400 for all requests, e.g.

FAIL [GET /index.jsp HTTP/1.0] Expected status=200, got status=400

and the build/build/catalina.out contains:

SEVERE: Error deploying configuration descriptor admin.xml
java.lang.NoClassDefFoundError: org/apache/catalina/util/RequestUtil
	at org.apache.naming.resources.FileDirContext.normalize(FileDirContext.java:777)
	at org.apache.naming.resources.FileDirContext.file(FileDirContext.java:820)
	at org.apache.naming.resources.FileDirContext.listBindings(FileDirContext.java:333)
	at org.apache.naming.resources.ProxyDirContext.listBindings(ProxyDirContext.java:516)
	at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:175)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4073)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
	at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
	at org.apache.catalina.core.StandardService.start(StandardService.java:448)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

etc. for all the other web applications.

The RequestUtil is compiled and is present in /server/lib/catalina.jar,
but FileDirContext class is in /common/lib/naming-resources.jar
and does not see it.

PS: When we fix this, the expected result from tester app is two
FAIL'ures. It is how it
was a week ago. The two failures do not show up if you will call
run-tester target without calling
clean-tester before it. That is, if those JSP pages are already
compiled and Tomcat was
restarted after their compilation.

I suppose that 4.1 will have the same problem.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message