[NTLUG:Discuss] Problem with blackdown JDK on RH 7

[Neil Aggarwal]

Hello:

I am runnning a machine with 2 processors with RedHat 7.0, Blackdown JDK
1.3
with the classic mode since HotSpot crashed, apache 1.3.17, and tomcat
3.2.1.

The machine boots up and runs fine for a long time, but anywhere from 4
hours to
a day after I start it, and then I get this output from tomcat:

   SIGSEGV   11*  segmentation violation
       si_signo [11]: SIGSEGV   11*  segmentation violation
       si_errno [0]: Success
       si_code [0]: SI_USER [pid: 0, uid: 0]
           stackpointer=0x44dff874

   Full thread dump Classic VM (Blackdown-1.3.0-FCS, native threads):
       "Keep-Alive-Timer:server2.jammconsulting.com" (TID:0x40ecdf20,
   sys_thread_t:0x44c6ff10, state:R, native ID:0x4a6bd7) prio=8
       "Thread-971" (TID:0x40ee3278, sys_thread_t:0x8565308, state:CW,
native
   ID:0x4a67d6) prio=5
           at java.lang.Object.wait(Native Method)
           at java.util.TimerThread.mainLoop(Timer.java:432)
           at java.util.TimerThread.run(Timer.java:385)
       "Thread-970" (TID:0x40eaaa40, sys_thread_t:0x85654c8, state:CW,
native
   ID:0x4a4bd4) prio=5
           at java.lang.Object.wait(Native Method)
           at java.util.TimerThread.mainLoop(Timer.java:432)
           at java.util.TimerThread.run(Timer.java:385)
   Monitor Cache Dump:
       java.util.TaskQueue at 40EB9470/4101FBA8: <unowned>
           Waiting to be notified:
               "Thread-258" (0x8373650)
       java.util.TaskQueue at 40EB14D0/410927D0: <unowned>
           Waiting to be notified:
               "Thread-484" (0x845a9c8)
       java.util.TaskQueue at 40ED12D0/41145BD8: <unowned>
           Waiting to be notified:
               <unknown thread> (0x44c1c7a0)
       java.util.TaskQueue at 40E99628/4101A6D0: <unowned>
           Waiting to be notified:
               "Thread-239" (0x83714f8)
       java.util.TaskQueue at 40DFA0F8/41018670: <unowned>
           Waiting to be notified:
               "Thread-222" (0x445c5690)
       java.util.TaskQueue at 40EE91D8/40FCBC20: <unowned>
           Waiting to be notified:
               "Thread-63" (0x8329358)
       java.util.TaskQueue at 40EA9580/4102C2F8: <unowned>
           Waiting to be notified:
               "Thread-327" (0x44a18290)
       java.util.TaskQueue at 40EB15E8/410790E8: <unowned>
           Waiting to be notified:
               "Thread-486" (0x845ac10)
       java.util.TaskQueue at 40EE9068/40FC7BD0: <unowned>

   [Many more threads are here, but I will skip it for brevity]

           Waiting to be notified:
               <unknown thread> (0x44c72f70)
       java.util.TaskQueue at 40EDED80/414F2D58: <unowned>
           Waiting to be notified:
               "Thread-706" (0x84f0fd0)
      
org.apache.tomcat.util.ThreadPool$ControlRunnable at 40EEEED0/40FFCA90:
   <unowned>
           Waiting to be notified:
               "Thread-201" (0x44597ea8)
       java.util.TaskQueue at 40E96958/4103F150: <unowned>
           Waiting to be notified:
               "Thread-407" (0x44a2b428)
       java.util.TaskQueue at 40EA6A40/414C5BB0: <unowned>
           Waiting to be notified:
               "Thread-957" (0x85658f8)
       java.util.TaskQueue at 40EC6C60/41260F48: <unowned>
           Waiting to be notified:
               "Thread-966" (0x44a92b30)
   Registered Monitor Dump:
       utf8 hash table: <unowned>
       JNI pinning lock: <unowned>
       JNI global reference lock: <unowned>
       BinClass lock: <unowned>
       Class linking lock: <unowned>
       System class loader lock: <unowned>
       Code rewrite lock: <unowned>
       Heap lock: <unowned>
       Monitor cache lock: owner
"Keep-Alive-Timer:server2.jammconsulting.com"
   (0x44c6ff10) 1 entry
       Thread queue lock: owner
"Keep-Alive-Timer:server2.jammconsulting.com"
   (0x44c6ff10) 1 entry
           Waiting to be notified:
               "Thread-34" (0x80541d8)
       Monitor registry: owner
"Keep-Alive-Timer:server2.jammconsulting.com"
   (0x44c6ff10) 1 entry

If I do a ps -aux, I have a tremendous number of processes that look
like this:
  root      9681  0.0  0.0     0    0 ?        Z    10:33   0:00 [java
<defunct>]

And I have to restart the machine.

Has anyone seen this? Is there a fix or workaround?

Thanks,
   Neil.



--
Neil Aggarwal
JAMM Consulting, Inc. -- (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development -- Java, JSP, servlets, databases