Hi.

Steve Burling wrote:
I'm starting the process of upgrading our Tomcat/Cocoon install, currently Tomcat 5.0.16 and Cocoon 2.1.3, wanting to move to Tomcat 5.5.9 and Cocoon 2.1.7. I've run into a problem that I can't explain, and hope that someone else has seen (and solved!) the problem.

Our web/Tomcat/Cocoon server is a Sun ES3500, running Solaris 8 (uname says SunOS hostname 5.8 Generic_117350-25 sun4u sparc). A vanilla install of Tomcat, with an un-modified server.xml, starts up just fine. If I copy the cocoon.war file that results from un-tarring the Cocoon 2.1.7 distribution and typing "build.sh war" into Tomcat's webapps directory, the Tomcat startup hangs right after logging "Scheduler Cocoon_$_Wed_Aug_03_11:26:06_EDT_2005 started."



Does the server hangs or crashes? If it's hanging, you could try to take severals JVM threads dumps (kill -3 on the JVM pid) and using something like http://yusuke.homeip.net/samurai/ to try to determine where is the lock.

Regards.

--
Aurélien

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to