Hi
Caldarale, Charles R Wrote:
parent=gnu.gcj.runtime.SystemClassLoader
You need to use a real JVM (HotSpot, JRockit, IBM), not a toy one.
Remove gcj from your system as quickly as possible.
It seems like jpackage.org packages is having dependency towards gcj. Do
you know perhaps about another
On 2 June 2010 09:13, David Karlsen dav...@delonic.no wrote:
Caldarale, Charles R Wrote:
parent=gnu.gcj.runtime.SystemClassLoader
You need to use a real JVM (HotSpot, JRockit, IBM), not a toy one.
Remove gcj from your system as quickly as possible.
It seems like jpackage.org packages is
Hi
Problems fixed. It was a mismatch between JVM-versions. Upgrading
Tomcat, did not automaticly upgrade JVM. Seems like when building the
Tomcat packages, it did not take into account checking the JVM for wrong
version. Upgrading the JVM to the latest GCJ version solved the problem.
Thanks.
Peter Crowther wrote:
On 2 June 2010 09:13, David Karlsen dav...@delonic.no wrote:
Caldarale, Charles R Wrote:
parent=gnu.gcj.runtime.SystemClassLoader
You need to use a real JVM (HotSpot, JRockit, IBM), not a toy one.
Remove gcj from your system as quickly as possible.
It seems like
Dear list
I have recently been running Tomcat 5 on my server, without problems.
After an upgrade to Tomcat 6, however I get errors. During the upgrade I
manually removed all the Tomcat 5 packages, and dependent packages
before I installed new Tomcat 6 packages from the jpackage.org repo. The
On 01/06/2010 13:20, David Karlsen wrote:
Dear list
I have recently been running Tomcat 5 on my server, without problems.
After an upgrade to Tomcat 6, however I get errors. During the upgrade I
manually removed all the Tomcat 5 packages, and dependent packages
before I installed new
From: David Karlsen [mailto:dav...@delonic.no]
Subject: Problems after upgrading to Tomcat6
parent=gnu.gcj.runtime.SystemClassLoader
You need to use a real JVM (HotSpot, JRockit, IBM), not a toy one. Remove gcj
from your system as quickly as possible.
- Chuck
THIS COMMUNICATION MAY
