Bug 35907 - Java JVM crashes
Summary: Java JVM crashes
Status: RESOLVED INVALID
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: Common (show other bugs)
Version: unspecified
Hardware: Sun SunOS
: P2 critical (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords: JDK1.4
: 35908 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-07-28 06:18 UTC by Rajendra Kotturi
Modified: 2008-10-05 03:08 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rajendra Kotturi 2005-07-28 06:18:29 UTC
The tomcat JVM crashes without any reason. The JAVA version we use is Java 
HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode). It crashes with the following 
error.

Unexpected Signal : 10 occurred at PC=0xF98FC78C

 Function=com.sun.tools.javac.v8.code.ClassReader.list
(Ljava/lang/String;Ljava/lang/String;
[Ljava/lang/String;Lcom/sun/tools/javac/v8/code/Symbol$PackageSymbol;)V 
(compiled Java code)
Library=(N/A)

Current Java thread:

Dynamic libraries:
0x10000         /home/bodev/tomcat41/jdk/bin/java
0xff350000      /usr/lib/libthread.so.1
0xff340000      /usr/lib/libdl.so.1
0xff200000      /usr/lib/libc.so.1
0xff390000      /usr/platform/SUNW,Sun-Fire-V440/lib/libc_psr.so.1
0xfe000000      /home/bodev/tomcat41/jdk/jre/lib/sparc/client/libjvm.so
0xff2d0000      /usr/lib/libCrun.so.1
0xff1e0000      /usr/lib/libsocket.so.1
0xff100000      /usr/lib/libnsl.so.1
0xff0b0000      /usr/lib/libm.so.1
0xff1c0000      /usr/lib/libsched.so.1
0xff090000      /usr/lib/libmp.so.2
0xff050000
/home/bodev/tomcat41/jdk/jre/lib/sparc/native_threads/libhpi.so
0xff030000      /usr/lib/nss_files.so.1
0xfe7d0000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libverify.so
0xfe790000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libjava.so
0xfe760000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libzip.so
0xe16d0000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libnet.so
0xdd300000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libawt.so
0xe4080000      /home/bodev/tomcat41/jdk/jre/lib/sparc/libmlib_image.so
0xe4010000      
> /home/bodev/tomcat41/jdk/jre/lib/sparc/motif21/libmawt.so
0xdd080000      /usr/dt/lib/libXm.so.4
0xe4390000      /usr/openwin/lib/libXt.so.4
0xe42d0000      /usr/openwin/lib/libXext.so.0
0xe42b0000      /usr/openwin/lib/libXtst.so.1
0xdcf80000      /usr/openwin/lib/libX11.so.4
0xe41a0000      /usr/openwin/lib/libdps.so.5
0xe1fe0000      /usr/openwin/lib/libSM.so.6
0xe1fb0000      /usr/openwin/lib/libICE.so.6

Heap at VM Abort:
Heap
 par new generation   total 9536K, used 6673K [0xe5000000, 0xe5960000,
0xe6000000)
  eden space 9472K,  70% used [0xe5000000, 0xe56845a0, 0xe5940000)
  from space 64K,   0% used [0xe5940000, 0xe5940000, 0xe5950000)
  to   space 64K,   0% used [0xe5950000, 0xe5950000, 0xe5960000)
 concurrent mark-sweep generation total 148032K, used 88815K
> [0xe6000000,
0xef090000, 0xf5000000)
 concurrent-mark-sweep perm gen total 37720K, used 22630K 
[0xf5000000, 0xf74d6000, 0xf9000000)

Local Time = Wed May 18 21:55:53 2005 Elapsed Time = 77789 # # 
HotSpot Virtual Machine Error : 10 # Error ID : 4F530E43505002EF 01 
# Please report this error at # 
http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode) #
Comment 1 Tim Funk 2005-07-28 12:37:27 UTC
*** Bug 35908 has been marked as a duplicate of this bug. ***
Comment 2 Tim Funk 2005-07-28 12:39:23 UTC
From the trace - it looks like javac is barfing which is a Sun bug. Please be
sure that all patches are applied and if needed - use the fork option for
compiling jsps.

Otherwise - this is not a tomcat bug.
Comment 3 Rajendra Kotturi 2005-07-28 19:24:42 UTC
(In reply to comment #2)
> From the trace - it looks like javac is barfing which is a Sun bug. Please be
> sure that all patches are applied and if needed - use the fork option for
> compiling jsps.
> Otherwise - this is not a tomcat bug.
In our case the JSPs are compiled at runttime by tomcat. Can you please tell me 
how to use fork option for compiling JSPs ? Do you mean we should pre-compile 
all modified or new JSPs before accessing them ?

Comment 4 Rajendra Kotturi 2005-07-28 19:39:51 UTC
(In reply to comment #2)
> From the trace - it looks like javac is barfing which is a Sun bug. Please be
> sure that all patches are applied and if needed - use the fork option for
> compiling jsps.
> Otherwise - this is not a tomcat bug.
In our case the tomcat compiles the new and modified JSP pages. Can you please 
let us know how to make tomcat use the fork option for compiling jsps ? I am 
not aware of using fork option in general. Should we be do pre-compiling of JSP 
pages before accessing them ?