1 Reply Latest reply on Aug 25, 2010 1:31 AM by Armin Haaf

    detected failure on control connection

    Armin Haaf Newbie

      in our cluster with 3 nodes we get the following warnings

       

      2010-07-01 15:26:41,646 WARN  [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] [T:206] org.jboss.remoting.transport.bisocket.BisocketServerInvoke
      r$ControlMonitorTimerTask@236d517d: detected failure on control connection Thread[control: Socket[addr=/10.199.18.12,port=46677,localport=49926],5,jboss] (3j0
      02-b6u5j-gayr2q3g-1-gb257m80-9dhq: requesting new control connection

       

       

      today the message occured on the first node 290 times, the second 179 times and on the third 8 times

       

      we are using jboss as 5.1 with jboss-remoting 2.5.2-SP2 and messaging 1.4.6-GA

       

      it seems that this warning did not produce any problems. But every 3-4 days a nodes serverpeer dies (client connection no longer possible, jmx info about client connections did not return)

        • 1. Re: detected failure on control connection
          Armin Haaf Newbie

          now we have a problem with that issue. we havn't seen that warning since a long time, but since 2 days we get it again, and after the warning a cluster nodes jms did not work anymore. All clients loose their connection (node MessageDrivenBeans as well as remote clients)

           

          this makes messaging unusable on that node and we have to restart the node.

           

          Its now always at the same time when we are doing some batch jobs. Maybe this is a load/gc induced problem?