0 Replies Latest reply on Aug 11, 2014 2:58 AM by Stephan Pelikan

    JBoss AS 7.2.0: HornetQ warnings every day at 00:30

    Stephan Pelikan Newbie

      Hi everybody,

       

      I want to use JBoss AS 7.2.0 but running at night it gives this warnings:

      00:32:55,744 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212107: Connection failure has been detected: HQ119034: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

      00:32:55,752 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 34a06632-1f4c-11e4-b8ce-f7a4da65325c

      00:32:55,757 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 34a06632-1f4c-11e4-b8ce-f7a4da65325c

      00:32:55,777 WARN  [org.hornetq.jms.server] (Thread-4 (HornetQ-client-global-threads-754027464)) HQ122017: Notified of connection failure in xa recovery connectionFactory for provider ClientSessionFactoryImpl [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=24461b8a-1f01-11e4-b8ce-f7a4da65325c, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryGroupConfiguration=null], connectorConfig=TransportConfiguration(name=24461b8a-1f01-11e4-b8ce-f7a4da65325c, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0, backupConfig=null] will attempt reconnect on next pass: HornetQException[errorType=NOT_CONNECTED message=HQ119025: Channel disconnected]

              at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:418) [hornetq-core-client-2.3.0.CR1.jar:]

              at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:214) [hornetq-server-2.3.0.CR1.jar:]

              at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.0.CR1.jar:]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]

              at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]

      It is a JBoss 7.2.0 running standalone-full.xml. My application does not use JMS at the moment. The application does not seem to be effected by this, but we plan to use JMS. Java is 1.7.0_60 running on Linux (Linux pha0ss03 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux). On Startup the log says:

      11:21:51,903 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/appl/jboss-as-7.2.0.Final/standalone/data/messagingjournal,bindingsDirectory=/appl/jboss-as-7.2.0.Final/standalone/data/messagingbindings,largeMessagesDirectory=/appl/jboss-as-7.2.0.Final/standalone/data/messaginglargemessages,pagingDirectory=/appl/jboss-as-7.2.0.Final/standalone/data/messagingpaging)

      11:21:51,912 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221008: Waiting to obtain live lock

      11:21:52,024 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221017: Using NIO Journal

       

      11:21:52,317 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221039: Waiting to obtain live lock

      11:21:52,318 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221040: Live Server Obtained live lock

      11:21:54,198 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 192.168.220.17:5445 for CORE protocol

      11:21:54,217 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 192.168.220.17:5455 for CORE protocol

      11:21:54,245 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221009: Server is now live

      11:21:54,246 INFO  [org.hornetq.core.server] (MSC service thread 1-2) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [233560e5-1d74-11e4-b4ef-dde66b111f7e]

      11:21:57,806 INFO  [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started

       

      11:21:57,815 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra

       

       

      According to http://docs.jboss.org/hornetq/2.2.2.Final/user-manual/en/html/client-reconnection.html I added

      <retry-interval>1000</retry-interval>

      <retry-interval-multiplier>1.5</retry-interval-multiplier>

      <max-retry-interval>60000</max-retry-interval>

      <reconnect-attempts>1000</reconnect-attempts>

      to standalone-full.xml (<connection-factory name="InVmConnectionFactory">, <connection-factory name="RemoteConnectionFactory"> and <pooled-connection-factory name="hornetq-ra">) but it has no effect.

       

      Any suggestions what this is or how to avoid it?