Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chuck,
>
> Caldarale, Charles R wrote:
>>> From: Bill Davidson [mailto:bill...@gmail.com]
>>> Subject: Fun with the JVM crashing.
>>
>>> I&
Rainer Jung wrote:
In case you only want to exclude few methods from compilation,
-XX:CompileCommand=exclude,com/myCompany/servlets/sales/blah/some,method
will do it.
Since we put this change into production, we haven't seen the problem.
Thank you so much.
-
Rainer Jung wrote:
You can track compilation with -XX:+PrintCompilation.
[...various other options...]
Wow. I never realized you could do stuff like that. Neat.
Thanks!
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apac
On 06.02.2009 02:37, Bill Davidson wrote:
I've submitted this to Sun a few times. No response. I was hoping
someone here might have an idea of what to look for.
Tomcat 6.0.18
RedHat 5.2Server
Sun JVM
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at p
> Caldarale, Charles R wrote:
>>> From: Bill Davidson [mailto:bill...@gmail.com]
>>> Subject: Fun with the JVM crashing.
>>
>>> I'm thinking that the JVM shouldn't be getting SIGSEGV's.
>>
>> You're right about that. However,
Hi Bill
My development workstation is a 64 bit Ubuntu 8.04. I've had numerous
problems with SIGSEGV crashes when I run my applications under Eclipse
3.3, but the same machine also runs the same applications from the same
version(s) of tomcat (6.0.14,6.0.16 and 6.0.18) I found that what seemed
> From: Caldarale, Charles R
> Subject: RE: Fun with the JVM crashing.
>
> > Maybe I should try reverting to 6u7?
>
> That would be my next step.
You could install a 32-bit JVM; that would give you the option of running
either -server or -client. If the 32-bit -server mode
> From: Bill Davidson [mailto:bill...@gmail.com]
> Subject: Re: Fun with the JVM crashing.
>
> Maybe I should try reverting to 6u7?
That would be my next step.
> I was thinking it might make the CompileTask issue go away.
Well it does, because the JVM won't use the compilers
Bill Davidson wrote:
Caldarale, Charles R wrote:
Major changes went in between 6u7 and 6u10.
Maybe I should try reverting to 6u7?
Dammit. Looking back through my old hs_err*.log files,
it also happened with 6u7.
-
To unsub
Caldarale, Charles R wrote:
Major changes went in between 6u7 and 6u10.
Maybe I should try reverting to 6u7?
I'm wondering if -Xint might help.
Only if you want performance to go into the toilet - that's
> interpreter mode, also know as really, really, abominably slow.
I was thinking it m
> From: Bill Davidson [mailto:bill...@gmail.com]
> Subject: Re: Fun with the JVM crashing.
>
> However, it has happened on three different boxes,
> always with the same CompileTask mentioned.
That pretty much eliminates hardware.
> BTW, it also happened with 6u10.
Major chang
Caldarale, Charles R wrote:
Only if that shows up repeatedly.
It does.
I'm thinking that the JVM shouldn't be getting SIGSEGV's.
You're right about that. However, it could also be an OS or
> hardware problem. You might want to run some serious memory
> tests on the box, just to eliminate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: Bill Davidson [mailto:bill...@gmail.com]
>> Subject: Fun with the JVM crashing.
>
>> I'm thinking that the JVM shouldn't be getting SIGSEGV's.
>
> You're ri
> From: Bill Davidson [mailto:bill...@gmail.com]
> Subject: Fun with the JVM crashing.
> I'm wondering if that CompileTask is what's causing the problem.
Only if that shows up repeatedly.
> I'm thinking that the JVM shouldn't be getting SIGSEGV's.
You&#x
I've submitted this to Sun a few times. No response. I was hoping
someone here might have an idea of what to look for.
Tomcat 6.0.18
RedHat 5.2Server
Sun JVM
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x2b68e6a1db57, pid=10229, tid=11030
15 matches
Mail list logo
