Bill Mulert wrote:
>I'm running JDK1.3.1 from Sun on a Mandrake 8.1 box. Tomcat-3.2.3 runs just
>fine until I deploy the Jetspeed war, which causes the JVM running Tomcat to
>segfault as Tomcat starts up. The war file is burst into the webapps/jetspeed
>directory as expected, and Tomcat reports:
>
>2001-10-29 16:22:32 - ContextManager: Adding context Ctx( /examples )
>2001-10-29 16:22:32 - ContextManager: Adding context Ctx( /admin )
>Starting tomcat. Check logs/tomcat.log for error messages
>2001-10-29 16:22:32 - ContextManager: Adding context Ctx( )
>2001-10-29 16:22:32 - ContextManager: Adding context Ctx( /test )
>2001-10-29 16:22:32 - ContextManager: Adding context Ctx( /jetspeed )
>./tomcat.sh: line 181: 2319 Segmentation fault (core dumped) $JAVACMD
>$TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat
>"$@"
>
>There is no logs/tomcat.log file. I have JAVA_HOME and TOMCAT_HOME set
>properly.
>
>I run lots of java based applications on this box including Tomcat, JBoss,
>Ant, XMLC, jCVS, jBuilder and so on. I have tried this with the nightly
>build, with the default download, and with a build I created from the CVS
>sources. They all yield the same result.
>
>Can anyone advise me on how to diagnose or eliminate this problem?
>
It is a well known and unresolved java bug. I can't pop off my head the
bug number.
The workaround is to execute ulimit -s 2048 (or less) before calling
java virtual machine.
The problem is related with how libc 2.2 or higher manage the stack
allocation under Linux. I have patched my java_wrapper to do it
automatically on startup.
Although it has no relation with Jetspeed "per se", any big java
application will crash this way. I have seen this error even building
tomcat from cvs.
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
