tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ognjen Blagojevic <ogn...@etf.bg.ac.rs>
Subject [OT] Re: jvm exits without trace
Date Tue, 16 Mar 2010 16:04:33 GMT
Hi,

"Tomcat dies suddenly" thread was exciting almost as "Prison Break" TV 
series. I couldn't wait to find out what would be solution to the 
problem, and I must admit that just downgrading to lower sub-sub-sub 
version JVM left me a bit disappointed. :)

Regards,
Ognjen

Carl wrote:
> Taylan,
> 
> I have had a similar problem that is yet unsolved (see the thread 
> 'Tomcat dies suddenly'.)  In my case, the death left a core file which 
> showed the JVM stopped with a seg fault.  A week ago yesterday, we 
> switched to the Sun 1.6.0_7 JVM (from 1.6.0_17 and 1.6.0_17) (Chuck 
> suggested this) and so far, it is running even though we have had loads 
> and usages similar to those that caused crashes in the past.
> 
> Therefore, you might consider trying that JVM.
> 
> Hope I haven't jinxed myself by saying it is still up.
> 
> Thanks,
> 
> Carl
> 
> ----- Original Message ----- From: "Taylan Develioglu" 
> <tdevelioglu@ebuddy.com>
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Sent: Tuesday, March 16, 2010 7:41 AM
> Subject: Re: jvm exits without trace
> 
> 
>> With parent I meant the main JVM process as opposed to forked processes
>> or threads, sorry to confuse you there. Stracing the threads generates
>> too much data to store so I had to settle with the parent process.
>>
>> To answer your other questions.
>>
>> The code is 100% pure java, why it causes this messy crash is still
>> unclear but development is working to figure it out.
>>
>> I'll follow up when we find out more, but I'm not sure if we're likely
>> to dig into the root cause, working around it is more of a priority
>> right now than debugging the jvm.
>>
>>
>> On Mon, 2010-03-15 at 17:08 +0100, Christopher Schultz wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Taylan,
>>>
>>> On 3/15/2010 10:19 AM, Taylan Develioglu wrote:
>>> > The cause for the crashes was in our own application code, we're
>>> > currently investigating the exact reason.
>>>
>>> Yeah, I'd like to second Chuck's question: was it native code?
>>>
>>> > A strace of the parent process shows killed by sigsegv, why or how 
>>> this
>>> > can happen is still unclear.
>>>
>>> So, the parent was being killed? What was the parent of the JVM?
>>>
>>> > Thanks to everyone that gave their assistance.
>>>
>>> Definitely follow-up to let us all know what you've uncovered... this
>>> was certainly a weird situation.
>>>
>>> - -chris
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.10 (MingW32)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAkueW4wACgkQ9CaO5/Lv0PAdhgCfa32vlcsMI5ELCNcLSjjV+S/o
>>> FZEAnjvjXgAwxjejTXexGO//89TyeF+r
>>> =BPtZ
>>> -----END PGP SIGNATURE-----
>>>
>>> ---------------------------------------------------------------------
>>> 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