5 Replies Latest reply on Nov 30, 2011 7:59 AM by gr j

    STOMP Websocket Client DISCONNECTED

    gr j Newbie

      Hello Every one. I am a new bee on in hornet nest,

      I am experimenting stomp websocket example on hornetQ 2.1.2 and 2.2.5 versions.

      Connected with Both Java STOMP Websocket Client and Javascript client ( located at hornetqxxx/examples/jms/stomp-websockets/chat/index.html).

       

      Every thing I am testing on my local box. surprisingly 2.1.2 is never got disconnected even for days it is working. But HornetQ 2.2.5 version disconnects after 1 minute ? I dont know is it  a hornetq issue or NETTY websocket issue ?

       

      I am struggling to find how it is working on 2.1.2 but the same test case is failing on newer version ?

       

      I tried connect-ttl configuration parameters but non of these are working .

       

      Can some one show pointers on this issue ?

       

      Thanks

      GR

        • 1. Re: STOMP Websocket Client DISCONNECTED
          Yong Hao Gao Master

          You have a test case?

           

          Thanks

          Howard

          • 2. Re: STOMP Websocket Client DISCONNECTED
            Clebert Suconic Master

            Can you test on the next version?

             

            svn co http://anonsvn.jboss.org/repos/hornetq/branches/Branch_2_2_EAP/ myVersion

            cd myVersion

            ./build.sh

             

             

            Stomp 1.0 don't have ping support and we currently only implement stomp 1.0. so you have to make sure you send some stuff.

             

             

            I know of some guys using it seriously without any issues,

            • 3. Re: STOMP Websocket Client DISCONNECTED
              gr j Newbie

              I will poste the test client code which is based on netty-tools project.

               

              Here I am attaching the log file generated with hornetq 2.2.5 version

               

              Might be the log left some clues.

               

              [main] 19:09:51,552 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer]  Starting HornetQ Server

              [main] 19:09:52,627 WARNING [org.hornetq.core.deployers.impl.FileConfigurationParser]  AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

              [main] 19:09:52,775 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/largemessages,pagingDirectory=data/paging)

              [main] 19:09:52,777 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  Waiting to obtain live lock

              [main] 19:09:52,824 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager]  Using NIO Journal

              [main] 19:09:52,842 WARNING [org.hornetq.core.server.impl.HornetQServerImpl]  Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

              [main] 19:09:53,010 INFO [org.hornetq.core.server.impl.FileLockNodeManager]  Waiting to obtain live lock

              [main] 19:09:53,010 INFO [org.hornetq.core.server.impl.FileLockNodeManager]  Live Server Obtained live lock

              [main] 19:09:53,690 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  trying to deploy queue jms.topic.chat

              [main] 19:09:53,880 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:61614 for STOMP_WS protocol

              [main] 19:09:53,882 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:5445 for CORE protocol

              [main] 19:09:53,884 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  Server is now live

              [main] 19:09:53,885 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  HornetQ Server version 2.2.5.Final (HQ_2_2_5_FINAL_AS7, 121) [a0583c46-1ae7-11e1-832e-889ffa69cf02] started

              [hornetq-failure-check-thread] 19:12:39,894 WARNING [org.hornetq.core.protocol.stomp.StompConnection]  Connection failure has been detected: Did not receive data from /127.0.0.1:55998. 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=3]

              [hornetq-failure-check-thread] 19:12:39,896 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Client connection failed, clearing up resources for session bc7e80f9-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 19:12:39,900 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Cleared up resources for session bc7e80f9-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 19:12:57,914 WARNING [org.hornetq.core.protocol.stomp.StompConnection]  Connection failure has been detected: Did not receive data from /127.0.0.1:56005. 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=3]

              [hornetq-failure-check-thread] 19:12:57,915 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Client connection failed, clearing up resources for session c6f8637c-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 19:12:57,917 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Cleared up resources for session c6f8637c-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 19:13:29,924 WARNING [org.hornetq.core.protocol.stomp.StompConnection]  Connection failure has been detected: Did not receive data from /127.0.0.1:56008. 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=3]

              [hornetq-failure-check-thread] 19:13:29,925 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Client connection failed, clearing up resources for session da24d5ff-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 19:13:29,927 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Cleared up resources for session da24d5ff-1ae7-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 21:48:11,116 WARNING [org.hornetq.core.protocol.stomp.StompConnection]  Connection failure has been detected: Did not receive data from /127.0.0.1:58847. 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=3]

              [hornetq-failure-check-thread] 21:48:11,118 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Client connection failed, clearing up resources for session 75da14a2-1afd-11e1-832e-889ffa69cf02

              [hornetq-failure-check-thread] 21:48:11,121 WARNING [org.hornetq.core.server.impl.ServerSessionImpl]  Cleared up resources for session 75da14a2-1afd-11e1-832e-889ffa69cf02

               

               

               

              ********************************************************************************************************

              HornetQ 2.1.2 log file ,

               

              [main] 19:01:50,690 INFO [org.hornetq.integration.bootstrap.HornetQBootstrapServer]  Starting HornetQ Server

              [main] 19:01:51,748 WARNING [org.hornetq.core.deployers.impl.FileConfigurationParser]  AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

              [main] 19:01:51,806 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  live server is starting..

              [main] 19:01:51,841 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager]  Using NIO Journal

              [main] 19:01:51,866 WARNING [org.hornetq.core.server.impl.HornetQServerImpl]  Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

              [main] 19:01:53,065 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE protocol

              [main] 19:01:53,068 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]  Started Netty Acceptor version 3.2.1.Final-r2319 localhost:61614 for STOMP_WS protocol

              [main] 19:01:53,070 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  HornetQ Server version 2.1.2.Final (Colmeia, 120) started

               

               

              Thanks

              GR

              • 4. Re: STOMP Websocket Client DISCONNECTED
                Clebert Suconic Master

                it would be better if you posted some information / investigation and a test. Just to maximize our (and yours) time.

                • 5. Re: STOMP Websocket Client DISCONNECTED
                  gr j Newbie

                  By adding following parameter to hornetq-configuration.xml is making Disconnecting connection.

                   

                  <connection-ttl-override>86400000</connection-ttl-override>

                  I tried to understand the code which is causing the disconnection and it is FailureCheckAndFlushThread.java

                  the ttl parameter is assigned if  ttl-override is configured in xml.

                   

                  So far I can tweak this parameter and make it working. My next test cases would be Test in LAN and over Internet.

                   

                  Thanks for sharing the link

                  svn co http://anonsvn.jboss.org/repos/hornetq/branches/Branch_2_2_EAP/ myVersion

                   

                  I will test STOMP 1.1 will solve the problem all together.

                   

                   

                  But I still don't understand the how hornetq2.1.2 is working out of the box ? I guessing there is bug which got fixed in 2.2.5

                   

                  Thanks

                  GR