Tomcat 5.0 and diablo-jdk-1.3.1 crash

[Panagiotis Astithas]

Olivier Vautrin wrote:
> It is a Pentium 133 Mhz with 32MB RAM.
> 
> I tried with another JDK: the JDK-1.4.2 (not the diablo-jdk). I doesn't work
> but I have an other kind of error. The java start for 10-20 seconds and then
> crash with the following log:
> 
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack
> location
> Mar 22, 2004 8:39:43 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on port 8180
> Mar 22, 2004 8:39:44 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 35894 ms
> Mar 22, 2004 8:39:48 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Mar 22, 2004 8:39:48 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
> Mar 22, 2004 8:39:48 PM org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> Mar 22, 2004 8:39:49 PM org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment ( non-jmx )
> Mar 22, 2004 8:39:49 PM org.apache.catalina.core.StandardHostDeployer
> install
> INFO: Processing Context configuration file URL
> file:/usr/local/jakarta-tomcat5.0/conf/Catalina/localhost/admin.xml
> 
> Unexpected Signal : 11 occurred at PC=0x2A6D15D4
> Function=[Unknown.]
> Library=(N/A)
> 
> NOTE: We are unable to locate the function name symbol for the error
>       just occurred. Please refer to release documentation for possible
>       reason and solutions.
> 
> 
> Current Java thread:
> 
> Dynamic libraries:
> Can not get information for pid = 243
> 
> Heap at VM Abort:
> Heap
>  def new generation   total 576K, used 378K [0x2c770000, 0x2c810000,
> 0x2cc50000)
>   eden space 512K,  67% used [0x2c770000, 0x2c7c6fc8, 0x2c7f0000)
>   from space 64K,  48% used [0x2c800000, 0x2c807b58, 0x2c810000)
>   to   space 64K,   0% used [0x2c7f0000, 0x2c7f0000, 0x2c800000)
>  tenured generation   total 1936K, used 1616K [0x2cc50000, 0x2ce34000,
> 0x30770000)
>    the space 1936K,  83% used [0x2cc50000, 0x2cde4038, 0x2cde4200,
> 0x2ce34000)
>  compacting perm gen  total 5376K, used 5311K [0x30770000, 0x30cb0000,
> 0x34770000)
>    the space 5376K,  98% used [0x30770000, 0x30c9ff88, 0x30ca0000,
> 0x30cb0000)
> 
> Local Time = Mon Mar 22 20:39:52 2004
> Elapsed Time = 55
> #
> # HotSpot Virtual Machine Error : 11
> # Error ID : 4F530E43505002EF
> # Please report this error at
> # http://java.sun.com/cgi-bin/bugreport.cgi
> #
> # Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 mixed mode)
> #
> # An error report file has been saved as hs_err_pid243.log.
> # Please refer to the file for further information.
> #
> 
> During this time, only the port 8180 (coyote) is listening:
> 
> -su-2.05b# netstat -a
> Active Internet connections (including servers)
> Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
> tcp4     402      0  10.0.0.1.8180          10.0.0.11.1616
> ESTABLISHED
> tcp4       0      0  *.8180                 *.*                    LISTEN
> tcp4       0      0  localhost.1030         localhost.1029         TIME_WAIT
> tcp4       0    353  10.0.0.1.telnet        10.0.0.11.1612
> ESTABLISHED
> tcp4       0      0  10.0.0.1.telnet        10.0.0.11.1605
> ESTABLISHED
> [...]
> 
> Is that normal? Normally, the port 8080 should be listening also, no?
> I tried also the JDK-1.3, but this one crashed during the port installation.
> 
> Any idea about all this?

Have you ruled out the possibility of faulty RAM? Since this is a rather 
old machine I would be suspicious.

Cheers,
-- 
Panagiotis Astithas
Electrical & Computer Engineer, PhD
Network Management Center
National Technical University of Athens, Greece