tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl" <c...@etrak-plus.com>
Subject Re: jvm exits without trace
Date Wed, 24 Feb 2010 11:42:43 GMT
Taylan,

I am the person who started the "Tomcat dies suddenly" thread which I still 
haven't resolved.  I am curious about the pattern of failures you are 
experiencing because they may provide some clues to my problem.  In my case, 
the system will run for 15 minutes to 10 days before failing (most of the 
time it is several days to a week.)  It appears to die from a seg fault in 
the JVM (I am using Sun 1.6.0_18 but have tried previous versions)... you 
may be able to see the cause of the failure from the core file (the core 
files on my systems were in several directories so you may have to do a 
'find' to locate them.)  Load may be a factor but the failures generally 
come after the load has been heavy for a while.  I am running a couple of 
applications and it seems the failures are more frequent when people are 
hitting the additional apps (the primary app is always used, the remaining 
apps are used sporatically.)

How does this compare to what you are experiencing?

Thanks,

Carl

----- Original Message ----- 
From: "Taylan Develioglu" <tdevelioglu@ebuddy.com>
To: "Tomcat Users List" <users@tomcat.apache.org>; <pid@pidster.com>
Sent: Wednesday, February 24, 2010 5:09 AM
Subject: Re: jvm exits without trace


> The GC log shows plenty of heap space left in all the spaces.
>
> I purposely didn't bother replacing the variables because I figured they
> would not be relevant.
>
> But if you think they might provide clues they're as follows:
>
> JAVA_HEAP_SIZE=18432M
> JAVA_EDEN_SIZE=$(($(echo $JAVA_HEAP_SIZE|sed 's/M$\|G$//')/6))M
> JAVA_PERM_SIZE=128M
> JAVA_STCK_SIZE=128K
>
> EDEN_SIZE is 1/6th of total heap.
>
> And I said there was nothing in the system logs.
> But you get a couple of points for trying.
>
> On Wed, 2010-02-24 at 10:44 +0100, Pid wrote:
>> On 24/02/2010 09:36, Taylan Develioglu wrote:
>> > I thought I'd add the connector definitions too, :
>> >
>> >     <Connector port="80"
>> > protocol="org.apache.coyote.http11.Http11AprProtocol"
>> >                 compression="1024" keepAliveTimeout="60000"
>> > maxKeepAliveRequests="-1"
>> >                 enableLookups="false" redirectPort="443" 
>> > maxThreads="150"
>> > pollerSize="32768"
>> >                 pollerThreadCount="4"/>
>> >
>> >      <Connector port="443"
>> > protocol="org.apache.coyote.http11.Http11AprProtocol" SSLEnabled="true"
>> >                 enableLookups="false" maxThreads="10" scheme="https"
>> > secure="true"
>> >                 SSLCertificateFile="/etc/ssl/private/something.crt"
>> >                 SSLCertificateKeyFile="/etc/ssl/private/something.key"
>> >                 SSLCACertificateFile="/etc/ssl/certs/ca.crt"/>
>> >
>> >
>> > On Wed, 2010-02-24 at 10:23 +0100, Taylan Develioglu wrote:
>> >> Hi,
>> >>
>> >> I have jvm's, running tomcat and our application, exiting 
>> >> mysteriously,
>> >> and was wondering if anyone could give me some advice on how to debug
>> >> this thing.
>> >>
>> >> There is nothing in catalina.out, nor our application logs, and no
>> >> hotspot error file. GC log looks normal. No trace in system logs.
>> >>
>> >> I am left completely clueless :(, has anyone dealt with a problem like
>> >> this before?
>> >>
>> >> Any help appreciated.
>> >>
>> >> - Tomcat 6.0.24
>> >> - TC native 1.1.18
>> >> - APR 1.3.9
>> >> - Sun JDK 6u18
>> >> - Debian Lenny, 2.6.31.10-amd64
>> >>
>> >> 2 servlets, one as ROOT. 2 HTTP connectors that use TCNative/APR.
>> >>
>> >> JAVA_OPTS ( ):
>> >>
>> >>      -verbose:gc
>> >>      -Djava.awt.headless=true
>> >>      -Dsun.net.inetaddr.ttl=60
>> >>      -Dfile.encoding=UTF-8
>> >>      -Djava.io.tmpdir=$TMP_DIR
>> >>      -Djava.library.path=/usr/local/lib
>> >>      -Djava.endorsed.dirs=$CATALINA_BASE/endorsed
>> >>      -Dcatalina.base=$CATALINA_BASE
>> >>      -Dcatalina.home=$CATALINA_HOME
>> >>      -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>> >> -Djava.util.logging.config.file="$CATALINA_BASE/conf/logging.properties"
>> >>      -XX:+PrintGCDetails
>> >>      -Xloggc:$CATALINA_BASE/logs/gc.log
>> >>      -XX:+UseConcMarkSweepGC
>> >>      -XX:CMSInitiatingOccupancyFraction=70
>> >>      -Xms$JAVA_HEAP_SIZE
>> >>      -Xmx$JAVA_HEAP_SIZE
>> >>      -XX:NewSize=$JAVA_EDEN_SIZE
>> >>      -XX:MaxNewSize=$JAVA_EDEN_SIZE
>> >>      -XX:PermSize=$JAVA_PERM_SIZE
>> >>      -XX:MaxPermSize=$JAVA_PERM_SIZE
>> >>      -Xss$JAVA_STCK_SIZE
>> >>      -XX:+UseLargePages
>>
>> There's no actual heap size settings in the above.  But you get a couple
>> of points for trying.
>>
>> Google "Linux Out Of Memory killer" or "OOM Killer" and then check the
>> server logs carefully.  (e.g. /var/log/messages)
>>
>>
>> p
>>
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
> 


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


Mime
View raw message