]>
To: "Tomcat Users List"
Sent: Friday, June 29, 2007 8:46 PM
Subject: Re: Using Tomcat 5.5.23 with jdk 1.6.0_1
Hi Caldarale,
Thanks for your comments. I had the same compatibility problem on Fedora,
by
copying the tool.jar - although it is not a good idea- it worked out.
Anyway
to:[EMAIL PROTECTED]
> Subject: Re: Using Tomcat 5.5.23 with jdk 1.6.0_1
>
> Defaultly tomcat 5.5 only support up to JDK5. If you wanna run your
> application which was written by JDK 6, you can use Tomcat 6 + JDK 6.
Not true. JDK 6 is fully upward compatible with JDK 5.
> If you
if you have the whole dump we can look into it deeper, my guess is that
its a JVM bug or a combo of JVM/OS
Filip
Christopher Hartung wrote:
Hi there,
we are using Tomcat 5.5.23 with jdk 1.6.0_1. But sometimes we get
errors like this:
#
# An unexpected error has been detected by Java
> From: Li [mailto:[EMAIL PROTECTED]
> Subject: Re: Using Tomcat 5.5.23 with jdk 1.6.0_1
>
> Defaultly tomcat 5.5 only support up to JDK5. If you wanna run your
> application which was written by JDK 6, you can use Tomcat 6 + JDK 6.
Not true. JDK 6 is fully upward compatible wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Li,
Li wrote:
> Defaultly tomcat 5.5 only support up to JDK5. If you wanna run your
> application which was written by JDK 6, you can use Tomcat 6 + JDK 6.
Still, Tomcat shouldn't segfault the VM due to a version incompatibility.
My guess is that he
.
Regards
Li
On 6/29/07, Christopher Hartung <[EMAIL PROTECTED]> wrote:
Hi there,
we are using Tomcat 5.5.23 with jdk 1.6.0_1. But sometimes we get errors
like this:
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x002a958a666a, pid=852
Hi there,
we are using Tomcat 5.5.23 with jdk 1.6.0_1. But sometimes we get errors
like this:
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x002a958a666a, pid=8528, tid=1082333536
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0-b105
