You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Walter Brameld <wb...@newrivernet.com> on 2001/05/24 19:48:22 UTC
Segmentation Fault on Tomcat startup
I'm running Tomcat on a Redhat 7.0 box. I downloaded the Jetspeed 1.3a1
binaries and put the jetspeed.war file in the webapps directory. When I
try to start Tomcat, it seg faults. Tomcat was working fine before I
installed Jetspeed, and it works fine again if I remove the
jetspeed.war and the jetspeed subdirectory. Here is the output from the
startup:
[root@jacob bin]# ./tomcat.sh run
Using
classpath: /usr/local/tomcat/lib/ant.jar:/usr/local/tomcat/lib/jasper.jar:/usr/local/tomcat/lib/jaxp.jar:/usr/local/tomcat/lib/parser.jar:/usr/local/tomcat/lib/servlet.jar:/usr/local/tomcat/lib/test:/usr/local/tomcat/lib/webserver.jar:/usr/local/jdk/lib/tools.jar:/usr/local/jdk/lib/tools.jar
2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /examples )
2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /admin )
Starting tomcat. Check logs/tomcat.log for error messages
2001-05-24 01:38:41 - ContextManager: Adding context Ctx( )
2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /test )
2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /jetspeed )
initializing all services using org.apache.tomcat.facade.ServletConfigImpl
initializing service: ResourcesService
./tomcat.sh: line 178: 9252 Segmentation fault $JAVACMD $TOMCAT_OPTS
-Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat "$@"
There is nothing in the Tomcat logs to indicate any kind of error. Any
idea why it's crashing?
Walter Brameld
wbrameld@newrivernet.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Segmentation Fault on Tomcat startup
Posted by Santiago Gala <sg...@hisitech.com>.
Walter Brameld wrote:
> I'm running Tomcat on a Redhat 7.0 box. I downloaded the Jetspeed 1.3a1
> binaries and put the jetspeed.war file in the webapps directory. When I
> try to start Tomcat, it seg faults. Tomcat was working fine before I
> installed Jetspeed, and it works fine again if I remove the
> jetspeed.war and the jetspeed subdirectory. Here is the output from the
> startup:
>
> [root@jacob bin]# ./tomcat.sh run
> Using
> classpath: /usr/local/tomcat/lib/ant.jar:/usr/local/tomcat/lib/jasper.jar:/usr/local/tomcat/lib/jaxp.jar:/usr/local/tomcat/lib/parser.jar:/usr/local/tomcat/lib/servlet.jar:/usr/local/tomcat/lib/test:/usr/local/tomcat/lib/webserver.jar:/usr/local/jdk/lib/tools.jar:/usr/local/jdk/lib/tools.jar
> 2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /examples )
> 2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /admin )
> Starting tomcat. Check logs/tomcat.log for error messages
> 2001-05-24 01:38:41 - ContextManager: Adding context Ctx( )
> 2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /test )
> 2001-05-24 01:38:41 - ContextManager: Adding context Ctx( /jetspeed )
> initializing all services using org.apache.tomcat.facade.ServletConfigImpl
> initializing service: ResourcesService
> ./tomcat.sh: line 178: 9252 Segmentation fault $JAVACMD $TOMCAT_OPTS
> -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat "$@"
>
> There is nothing in the Tomcat logs to indicate any kind of error. Any
> idea why it's crashing?
>
We could, if you reported the jdk version you are using. A SEG_FAULT
indicates a bug in the java virtual machine. The Hotspot machines have
shown several of those. In multiprocessor machines, there is a
workaround for some of these. Another possibility is to upgrade to a
final release. 1.3.0_02 seems to work fine.
Other reason for having SEG_FAULTS is when the JVM gets out of memory,
since not all of the native code mallocs,... are checked. So, you can
also try to increase process memory limits for the JVM.
The fact that it happens only with "big" wars, like jetspeed, has little
to no relation with the problem, only that you are stressing more the
JVM, both memory and threading. Jetspeed is pure java, so any
segmentation fault is a jdk/jre problem.
> Walter Brameld
> wbrameld@newrivernet.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org