7 Replies Latest reply on Aug 3, 2013 5:53 AM by Heiko Green

    CONNECTION_TIMEDOUT message=HQ119032

    raysen_jia Newbie

      Dear Team,

       

      I have encountered this problem, I use 2.3.0.CR1

       

      Anybody know what is the problem?

       

      Caused by: HornetQException[errorType=CONNECTION_TIMEDOUT message=HQ119032: Timed out waiting to receive cluster topology. Group:null]

                at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:884)

                at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:583)

                ... 13 more

       

       

      Thanks.

      Raysen Jia

        • 1. Re: CONNECTION_TIMEDOUT message=HQ119032
          fahri cap Newbie

          Hi raysen;

           

          Have you found any solution to this problem. I am getting the same problem with the Jboss version 7.2 Final .

           

          Thanks in advance..

          • 2. Re: CONNECTION_TIMEDOUT message=HQ119032
            Justin Bertram Master

            Would need more details to be able to assist.  What is the use-case here?  What is the configuration?  Is the problem reproducible?  If so, how?

            • 3. Re: CONNECTION_TIMEDOUT message=HQ119032
              Heiko Green Newbie

              same problem here.

               

              using jboss 7.2 final. Config: standalone-full.xml.

               

              wondering becase no cluster config is used.

               

              02:51:57,684 ERROR [de.pantarhei.esa2i.index.IndexServiceDispatcher] (http-/0.0.0.0:10080-1) Failed to create session factory: javax.jms.JMSException: Failed to create session factory

                  at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:587)

                  at org.hornetq.jms.client.HornetQConnectionFactory.createQueueConnection(HornetQConnectionFactory.java:119)

                  at org.hornetq.jms.client.HornetQConnectionFactory.createQueueConnection(HornetQConnectionFactory.java:114)

                  at de.pantarhei.esa2i.index.IndexServiceDispatcher.addToIndexQueue(IndexServiceDispatcher.java:200) [esa2iEJB.jar:]

                  at de.pantarhei.esa2i.index.IndexServiceDispatcher.addToIndexQueue(IndexServiceDispatcher.java:189) [esa2iEJB.jar:]

                  at de.pantarhei.esa2i.facade.IndexServlet.proccessEttRequest(IndexServlet.java:141) [classes:]

                  at de.pantarhei.esa2i.facade.IndexServlet.doPost(IndexServlet.java:87) [classes:]

                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]

                  at de.pantarhei.esa2i.facade.IndexServlet.service(IndexServlet.java:110) [classes:]

                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]

                  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

                  at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

              Caused by: HornetQException[errorType=CONNECTION_TIMEDOUT message=HQ119032: Timed out waiting to receive cluster topology. Group:null]

                  at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:884)

                  at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:583)

                  ... 22 more

               

              conf:

               


              <subsystem xmlns="urn:jboss:domain:messaging:1.3">

              <hornetq-server>

              <persistence-enabled>true</persistence-enabled>

              <journal-file-size>102400</journal-file-size>

              <journal-min-files>50</journal-min-files>

               


              <connectors>

              <netty-connector name="netty" socket-binding="messaging"/>

              <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

              <param key="batch-delay" value="50"/>

              </netty-connector>

              <in-vm-connector name="in-vm" server-id="0"/>

              </connectors>

               


              <acceptors>

              <netty-acceptor name="netty" socket-binding="messaging"/>

              <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

              <param key="batch-delay" value="50"/>

              <param key="direct-deliver" value="false"/>

              </netty-acceptor>

              <in-vm-acceptor name="in-vm" server-id="0"/>

              </acceptors>

               


              <security-settings>

              <security-setting match="#">

              <permission type="send" roles="guest"/>

              <permission type="consume" roles="guest"/>

              <permission type="createNonDurableQueue" roles="guest"/>

              <permission type="deleteNonDurableQueue" roles="guest"/>

              </security-setting>

              </security-settings>

               


              <address-settings>

              <address-setting match="#">

              <dead-letter-address>jms.queue.DLQ</dead-letter-address>

              <expiry-address>jms.queue.ExpiryQueue</expiry-address>

              <redelivery-delay>0</redelivery-delay>

              <max-size-bytes>500485760</max-size-bytes>

              <address-full-policy>BLOCK</address-full-policy>

              <message-counter-history-day-limit>10</message-counter-history-day-limit>

              </address-setting>

              </address-settings>

               


              <jms-connection-factories>

              <connection-factory name="InVmConnectionFactory">

              <connectors>

              <connector-ref connector-name="in-vm"/>

              </connectors>

              <entries>

              <entry name="java:/ConnectionFactory"/>

              </entries>

              <block-on-non-durable-send>false</block-on-non-durable-send>

              <block-on-durable-send>false</block-on-durable-send>

              </connection-factory>

              <connection-factory name="RemoteConnectionFactory">

              <connectors>

              <connector-ref connector-name="netty"/>

              </connectors>

              <entries>

              <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>

              </entries>

              </connection-factory>

              <pooled-connection-factory name="hornetq-ra">

              <transaction mode="xa"/>

              <connectors>

              <connector-ref connector-name="in-vm"/>

              </connectors>

              <entries>

              <entry name="java:/JmsXA"/>

              </entries>

              </pooled-connection-factory>

              </jms-connection-factories>

               


              <jms-destinations>

              <jms-queue name="ArtikelIndex">

              <entry name="queue/ArtikelIndex"/>

              </jms-queue>

              <jms-queue name="ProjekteIndex">

              <entry name="queue/ProjekteIndex"/>

              </jms-queue>

              <jms-queue name="GremienIndex">

              <entry name="queue/GremienIndex"/>

              </jms-queue>

              <jms-queue name="DinMitgliederIndex">

              <entry name="queue/DinMitgliederIndex"/>

              </jms-queue>

              <jms-queue name="SixIndex">

              <entry name="queue/SixIndex"/>

              </jms-queue>

              <jms-queue name="SortIndex">

              <entry name="queue/SortIndex"/>

              </jms-queue>

              <jms-queue name="AutorenIndex">

              <entry name="queue/AutorenIndex"/>

              </jms-queue>

              <jms-queue name="DefaultIndex">

              <entry name="queue/DefaultIndex"/>

              </jms-queue>

              </jms-destinations>

              </hornetq-server>

              </subsystem>

               

              any ideas?

               

               


              • 4. Re: CONNECTION_TIMEDOUT message=HQ119032
                Clebert Suconic Master

                It seems a connectivity issue for me. Take a look if there's anything holding you on the firewal. You're not even being able to hit an error on the connectors, so I suspect a firewal issue.

                • 5. Re: CONNECTION_TIMEDOUT message=HQ119032
                  Heiko Green Newbie

                  hmmm, dont think so. client and server are on the same host, same JVM. in-vm connector is used.

                  • 6. Re: CONNECTION_TIMEDOUT message=HQ119032
                    Heiko Green Newbie

                    new exception:

                     

                    13:30:32,065 WARN  [org.hornetq.jms.server] (Thread-1792 (HornetQ-client-global-threads-10214029)) Notified of connection failure in xa discovery, we will retry on the next recovery: 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_25]

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

                        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

                    • 7. Re: CONNECTION_TIMEDOUT message=HQ119032
                      Heiko Green Newbie

                      any ideas to solve this problem ?

                       

                      if this occours, system will hang on full gc:

                       

                      S0 S1 P YGC YGCTFGCFGCT GCT

                       

                      9.88   7.50  82.51  36.22  96.12   3506  558.25125  239.919  798.169
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00  41.25   0.00  36.22  96.12   3506  566.24726  239.919  806.166
                        0.00   0.00   2.02  25.31  96.80   3506  566.24726  283.683  849.930

                       

                       

                      fullgc 25 to 26 needs 44 sec !!!!

                       

                       

                      11:43:45,304 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]

                      11:43:45,339 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 94a9aee5-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,344 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 94a9aee5-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,413 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]

                      11:43:45,414 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 9385ef4e-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,414 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 9385ef4e-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,414 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]

                      11:43:45,414 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 94d48f97-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,415 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 94d48f97-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,489 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]

                      11:43:45,489 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 94dcf342-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,490 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 94dcf342-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,530 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]

                      11:43:45,530 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 94c6108c-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,537 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 94c6108c-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,546 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]

                      11:43:45,550 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222100: Client connection failed, clearing up resources for session 94d1f777-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,550 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222158: Cleared up resources for session 94d1f777-fb80-11e2-bbe4-a1f5c6ad90d3

                      11:43:45,416 WARN  [org.hornetq.jms.server] (Thread-973 (HornetQ-client-global-threads-868555035)) HQ122017: Notified of connection failure in xa recovery connectionFactory for provider ClientSessionFactoryImpl [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=8f42040a-fb80-11e2-bbe4-a1f5c6ad90d3, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryGroupConfiguration=null], connectorConfig=TransportConfiguration(name=8f42040a-fb80-11e2-bbe4-a1f5c6ad90d3, 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_25]

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

                          at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]