1 Reply Latest reply on Jan 13, 2010 9:23 PM by Chi Man Lei

    Failed to register MBean Error and FuseMSB crashed with dump n Java Runtime

    Chi Man Lei Newbie

      I upgraded our FuseMSB recently to 5.3.0.5. However, it seems it is not that stable due to "Failed to register MBean" error. this error kept popping up in the log and eventually a fatal error was detected and the broker was crashed.

       

      here is the extraction from the log file. there was a dump file was generated. I can attached that later today.

       

      anyone else encountered similar issues before? I searched thru google and it looks like some old bugs that caused memory leak. I am not quite sure and thus seek for any feedback and help here. any suggestions or advices will be highly appreciated!

       

      thank you very much in advance!

       

      Chi

       

       

      WARN  ManagedTransportConnection     - Failed to register MBean: org.apache.activemq:BrokerName=prd_femb02,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/10.81.97.141_42141

      2286339.317:

      WARN  ManagedTransportConnection     - Failed to register MBean: org.apache.activemq:BrokerName=prd_femb02,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/10.81.97.141_42157

      2286345.702:

      2286350.816:

      WARN  ManagedTransportConnection     - Failed to register MBean: org.apache.activemq:BrokerName=prd_femb02,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/10.81.32.143_44457

      #

      1. A fatal error has been detected by the Java Runtime Environment:

      #

      1. SIGSEGV (0xb) at pc=0xb767f069, pid=2962, tid=3220466576

      #

      1. JRE version: 6.0_16-b01

      2. Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode linux-x86 )

      3. Problematic frame:

      #

      1. An error report file with more information is saved as:

      2. /opt/deploy/env/frontend_emb/fuse-message-broker/shared/system/hs_err_pid2962.log