2 Replies Latest reply on Mar 15, 2005 9:17 AM by trickard

    JBoss failing with log

    trickard
    trickard Mar 7, 2005 2:11 PM

      We are running JBoss3.2.5 on HPUX11.x. We upgraded last fall from 2.4.3 and have been running smoothly since the upgrade. We ran without problems for several years before the upgrade.

      We recently made a small change to a web application and two ejbs that the web app uses. The webapp calls a new method added to one of the beans and this new method calls a new method added to the second bean.

      The ear file has 100 or so beans. The ear was updated with the new files using the sun deploytool and redeployed to the dev and then tst environments.

      Under some circumstances manipulating the web app causes the jboss jvm process to totally disappear. There are no messages written to the console or any log and there is no core dump for the process the PID just vanishes without a trace.

      The failure typically happens on an update in the web app and the display of the returned page just stops at some point and the java process that was running the jboss jvm is simply gone.

      The new code works without errors until the jvm disappears.

      What could client code do that would cause the failure of tomcat/jboss in this way. I didnt think it was possible for client code to do anything, however wrong, that would immediately kill the jboss/tomcat jvm.

      We have had resource issues in the past but have always had failed threads announce their failure before dying and have never had anything kill tomcat or jboss.

      Is anyone aware of this behavior anywhere.

      • 2580 Views
      • Tags:
        • 1. Re: JBoss failing with log
          trickard
          trickard Mar 7, 2005 2:49 PM (in response to trickard)

          I have a stack trace if anyone can see anything from this

          13:44:54,258 INFO [STDOUT] 3/7 01:44:54.257: Pricing Forms Request received (GC
          HUMLEY at 10.101.101.30)

          Unexpected Signal : 11 occurred at PC=0x78C1450C
          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:
          "http-devjb%2F10.101.1.10-8080-Processor25" daemon prio=7 tid=0059c738 nid=121 l
          wp_id=1248290 runnable [0x5659e000..0x5659d4f0]
          Stack_Trace: error while unwinding stack
          ( 0) 0xc678e9e4 report_error__FbPCciN22e + 0x64 [/opt/java1.4/jre/lib/PA_RIS
          C2.0/server/libjvm.sl]
          ( 1) 0xc678e79c report_should_not_reach_here__FPCci + 0x3c [/opt/java1.4/jre
          /lib/PA_RISC2.0/server/libjvm.sl]
          ( 2) 0xc67d0c50 sender__5frameCFP11RegisterMapP8CodeBlob + 0x1a0 [/opt/java1
          .4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 3) 0xc67cdaa0 real_sender__5frameCFP11RegisterMap + 0x20 [/opt/java1.4/jre
          /lib/PA_RISC2.0/server/libjvm.sl]
          ( 4) 0xc6b42054 sender__6vframeCFv + 0x74 [/opt/java1.4/jre/lib/PA_RISC2.0/s
          erver/libjvm.sl]
          ( 5) 0xc6b10738 last_java_vframe__10JavaThreadFP11RegisterMap + 0x138 [/opt/
          java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 6) 0xc6b102ec print_stack__10JavaThreadFv + 0x8c [/opt/java1.4/jre/lib/PA_
          RISC2.0/server/libjvm.sl]
          ( 7) 0xc6a22bdc report_fatal_error__2osSFP12outputStreamPUci + 0x5ec [/opt/j
          ava1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 8) 0xc6a23aec handle_unexpected_exception__2osSFP6ThreadiPUcPv + 0x654 [/o
          pt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 9) 0xc6a2fdfc JVM_handle_hpux_signal__Q2_2os4HpuxSFiP9__siginfoPvT1 + 0x8fc
          [/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          (10) 0xc6a2b62c signalHandler__Q2_2os4HpuxSFiP9__siginfoPv + 0x14 [/opt/java
          1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          (11) 0xc020b6d0 _sigreturn [/usr/lib/libc.2]
          [error occured during error reporting]
          Stack_Trace: error while unwinding stack
          ( 0) 0xc678e9e4 report_error__FbPCciN22e + 0x64 [/opt/java1.4/jre/lib/PA_RIS
          C2.0/server/libjvm.sl]
          ( 1) 0xc678e79c report_should_not_reach_here__FPCci + 0x3c [/opt/java1.4/jre
          /lib/PA_RISC2.0/server/libjvm.sl]
          ( 2) 0xc67d0c50 sender__5frameCFP11RegisterMapP8CodeBlob + 0x1a0 [/opt/java1
          .4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 3) 0xc67cdaa0 real_sender__5frameCFP11RegisterMap + 0x20 [/opt/java1.4/jre
          /lib/PA_RISC2.0/server/libjvm.sl]
          ( 4) 0xc6b42054 sender__6vframeCFv + 0x74 [/opt/java1.4/jre/lib/PA_RISC2.0/s
          erver/libjvm.sl]
          ( 5) 0xc6b10738 last_java_vframe__10JavaThreadFP11RegisterMap + 0x138 [/opt/
          java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 6) 0xc6b102ec print_stack__10JavaThreadFv + 0x8c [/opt/java1.4/jre/lib/PA_
          RISC2.0/server/libjvm.sl]
          ( 7) 0xc6a22bdc report_fatal_error__2osSFP12outputStreamPUci + 0x5ec [/opt/j
          ava1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 8) 0xc6a23aec handle_unexpected_exception__2osSFP6ThreadiPUcPv + 0x654 [/o
          pt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          ( 9) 0xc6a2fdfc JVM_handle_hpux_signal__Q2_2os4HpuxSFiP9__siginfoPvT1 + 0x8fc
          [/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          (10) 0xc6a2b62c signalHandler__Q2_2os4HpuxSFiP9__siginfoPv + 0x14 [/opt/java
          1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
          (11) 0xc020b6d0 _sigreturn [/usr/lib/libc.2]

            • Actions
          • 2. Re: JBoss failing with log
            trickard
            trickard Mar 15, 2005 9:17 AM (in response to trickard)

            We have resolved this problem with an upgrade to the JVM

              • Actions