Hi
folks,
I'm posting this, since I know I can get help only from this community.
My application is a heavily multi-threaded java application which is runs
in Linux with the following configuration
OS -
RH9
Kernel -
2.4.20-30.9smp
glibc -
glibc-2.3.2-27.9.7
JVM - SUN
1.4.2
My
ap
Marc Heckmann <[EMAIL PROTECTED]> writes:
> On Wed, Jun 09, 2004 at 11:58:32PM -0700, Hui Huang wrote:
>> The segfault messages look benign - they are the implicit NULL
>> checks within JVM.
>
> But look at the following discussion, Andi Kleen one of the x86_64
> kernel developers says that the ke
On Wed, Jun 09, 2004 at 11:58:32PM -0700, Hui Huang wrote:
> The segfault messages look benign - they are the implicit NULL checks
> within JVM.
But look at the following discussion, Andi Kleen one of the x86_64
kernel developers says that the kernel has been fixed not to log the
messages if it is
Juergen Kreileder wrote:
HotSpot uses SIGSEGV internally. It does on x86 too, but the x86
kernel doesn't have a segfault logger, so you don't get these messages
there. IIRC there's no way to disable the x86_64 segfault logger
without recompiling the kernel.
Oh and when is 1.4.2 64-bit final comi
Marc Heckmann wrote:
Hi,
I am using j2sdk-1.4.2 on Fedora Core 2 x86_64. when starting tomcat
v4.1.30 (haven't tried any other version), I get segfaults and my
webapps do not run properly at all. This happens with either the 32
bit or native 64 bit versions of the SDK. I have tried on 2 separate
m
Radu-Adrian Popescu <[EMAIL PROTECTED]> writes:
> The error codes come in groups of 1-4 at a time, and they're
> alternate.
>
> What's causing this ?
HotSpot uses SIGSEGV internally. It does on x86 too, but the x86
kernel doesn't have a segfault logger, so you don't get these messages
there. II
The segfault messages look benign - they are the implicit NULL checks
within JVM.
Did you see a hang or a crash (i.e. tomcat process is gone,
segfaults in kernel log don't count, they are handled by JVM)?
Is this on HT Xeon? I've heard 2.6.5 in FC2 is not stable (frequent
hang) but 2.6.6 is Ok, loo