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 to affect the thing the most was 'loading up' the JVM. My app is actually 5 different wars - I get the most problems when all of them are loaded.

I found it so frustrating that I've actually procured a 2nd 64 bit machine to try to see what common factors there are. For example, I was going to see if Eclipse 3.4 was better than 3.3.

I tried b4 thru b16 and it seems to have made no difference.

No real answer here, just me giving you some more background data.

Regards

Alan Chaney


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 pc=0x00002b68e6a1db57, pid=10229, tid=1103006016
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b16 mixed mode linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x564b57]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x000000004bfe5c00): JavaThread "CompilerThread0" daemon [_thread_in_native, id=10244, stack(0x0000000041ae8000,0x0000000041be9000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000000

.....

Current CompileTask:
C2:2525 com.myCompany.servlets.sales.blah.some.method(Lcom/myCompany/servlets/someClass;Lcom/myCompany/servlets/otherClass;Lcom/oreilly/servlet/ParameterParser;)V (425 bytes)

......

-------------

I'm wondering if that CompileTask is what's causing the problem.
I'm thinking that the JVM shouldn't be getting SIGSEGV's.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



!DSPAM:498b962676632009820482!


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to