3 Replies Latest reply on Aug 30, 2002 12:57 PM by Howard

    Redhat 7.2 + JBoss 3.0.0 + Tomcat 4.0.3 + JDK 1.3.1_04 Probl

    Howard Newbie

      Hi all,

      I am having some problem keeping my Jboss server running, the environment is as follows,

      JBoss 3.0.0 with Tomcat 4.0.3
      Sun JDK 1.3.1_04
      Redhat Linux 7.2
      - kernal 2.4.7-10
      - glibc 2.2.4-13

      The server starts without any complain, but the JVM will crash after a period of time and causing the server instance to stop. An error file is generated and logged following this message.

      The error seems like a JVM bug to me, but I have checked everywhere on Sun's bugParade, the only suggesction I got is upgrade to JDK1.3, which I AM using already. Just wondering if anyone here has came across the similiar problem and perhaps can give me some pointer on the resolution to this.

      Thanks a bunch in adavance!!!

      Howard

      ########## Error Message ###############################

      Unexpected Signal : 11 occurred at PC=0x4018a07c
      Function name=mark_and_follow__9MarkSweepPP7oopDesc
      Library=/usr/java/jdk/jre/lib/i386/client/libjvm.so


      Dynamic libraries:
      08048000-0804c000 r-xp 00000000 03:02 983200 /usr/java/jdk/bin/i386/native_threads/java
      0804c000-0804d000 rw-p 00003000 03:02 983200 /usr/java/jdk/bin/i386/native_threads/java
      40000000-40016000 r-xp 00000000 03:02 1523731 /lib/ld-2.2.4.so
      40016000-40017000 rw-p 00015000 03:02 1523731 /lib/ld-2.2.4.so
      40017000-40018000 r--p 00000000 03:02 1097732 /usr/lib/locale/en_US/LC_IDENTIFICATION
      40018000-40019000 r--p 00000000 03:02 557079 /usr/lib/locale/en_US/LC_MEASUREMENT
      40019000-4001a000 r--p 00000000 03:02 81932 /usr/lib/locale/en_US/LC_TELEPHONE
      4001a000-4001b000 r--p 00000000 03:02 81934 /usr/lib/locale/en_US/LC_ADDRESS

      ..so on so on...

      4e03b000-4e03f000 r--s 00000000 03:02 213244 /tmp/jar_cache11824.tmp (deleted)
      4e43f000-4e440000 r--s 00000000 03:02 655559 /usr/java/jboss/server/default/tmp/deploy/server/default/deploy/web.warContent/79.web.warContent
      4e440000-4e441000 r--s 00000000 03:02 655559 /usr/java/jboss/server/default/tmp/deploy/server/default/deploy/web.warContent/79.web.warContent
      4e441000-4e442000 r--s 00000000 03:02 655559 /usr/java/jboss/server/default/tmp/deploy/server/default/deploy/web.warContent/79.web.warContent

      Local Time = Sat Aug 3 04:06:09 2002
      Elapsed Time = 9284
      #
      # HotSpot Virtual Machine Error : 11
      # Error ID : 4F530E43505002BD
      # Please report this error at
      # http://java.sun.com/cgi-bin/bugreport.cgi
      #
      # Java VM: Java HotSpot(TM) Client VM (1.3.1_04-b02 mixed mode)
      #

      ###########################################

        • 1. Re: Redhat 7.2 + JBoss 3.0.0 + Tomcat 4.0.3 + JDK 1.3.1_04 P
          Steve Park Newbie

          I use IBM's jdk 1.3.0 instead. It's available for free download at developerworks.ibm.com. I had problems when I moved to 1.3.1 so I went back to 1.3.0. Good luck!

          • 2. Re: Redhat 7.2 + JBoss 3.0.0 + Tomcat 4.0.3 + JDK 1.3.1_04 P
            E. A. Graham Jr. Newbie

            1) Try using the 1.4 SDK instead.
            2) The 2.4.7 kernel, if I remember correctly, was pretty much considered a lemon in many respects. Upgrade your kernel (I've got 2.4.9).

            I've been running JBoss under a small load for weeks without any hiccups, burps, or any other problem.

            • 3. Re: Redhat 7.2 + JBoss 3.0.0 + Tomcat 4.0.3 + JDK 1.3.1_04 P
              Howard Newbie

              Thanks a lot for the reply guys. I tried put on JDK1.4.0, but still no luck, I upgraded the glibc package, no luck, I upgraded the distrubtion to 7.3, which is kernel 2.4.18, still no luck...it's driving me nuts!

              The funny thing is I had another machine that has exactly the same configuration and setting, Redhat 7.3, JDK1.3.1_04, JBoss3.0.0, and that one is running FINE!! Is it possible the hardware difference is causing this problem? The machine that's crashing is useing PII-600 with AOpen board, the machine that's working is using DURON 650.

              The other finding I had is, although JDK1.4.0 doesn't solve the problem, but the JVM stays up a lot longer, about couple days or so, compare to a 10 minutes span from JDK1.3.1

              I will try using IBM SDK, and let's hope it works fine.

              Thanks a lot again for the reply.