My approach is to get something (a JVM) that works and then gradually change
until it breaks. Then, I know what is causing the problem. To date, I
haven't been able to get a JVM that works.
In my case, it might be something in my application that is causing the
crash on 64 bit Slackware as there are many people running 64 bit on Linux
without a problem. If it is my application, then any 64 bit JVM I throw at
it should crash.
On the other hand, if the 1.6.0_7 JVM works, then it is likely a bug in one
of the changes that brings the JVM to the current version. Time will tell.
Thanks,
Carl
----- Original Message -----
From: "André Warnier" <aw@ice-sa.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Tuesday, March 16, 2010 3:20 PM
Subject: Re: [OT] Re: jvm exits without trace
> Ognjen Blagojevic wrote:
>> 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. :)
>>
> +1
> It sounds quite like the standard tech support solution for Windows
> problems : de-install, re-install; and if that does not help, push the
> reset button.
>
> ---------------------------------------------------------------------
> 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
|