Thanks Danny,
My first approach will be to upgrade the JVM as Stefano suggested, reset
my threads back up to where I want them and if the problem persists with
latest stable JVM then I will submit to sun.
Thanks
Danny Angus wrote:
Hans,
The details you have provided would be better going t
Hans,
The details you have provided would be better going to Sun.
However it would also be interesting if we could work out why your
deployment resulted in this crash.
Lots of blocked threads suggests something funny somewhere. But quite
probably not James related.
d.
On 3/26/07, Hans Liebenbe
Upgrade your JVM.
When the JVM crashes with SIGSEGV it is not an application problem but a
JVM problem.
Stefano
Hans Liebenberg ha scritto:
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb788acd1, pid=13147, tid=2380995504
#
# Java VM: Java H
Hi,
I recently upgraded to James 2.3, and since then James is crashing. Here
is the info I have.
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
OS: linux
Some config.xml values of possi
