1 2 Previous Next 27 Replies Latest reply on Dec 10, 2013 9:36 AM by Justin Bertram

    Can not forward request to another clustered server

    mike just Master

      As I understand, when I configured two clustered server, if one server is down, another should be able to get and continue the current running process from the down server.

      But after I tested and found this is not the case.

       

      I configured two servers clustered running in one machine and started some work in one server, but when I shut down one server, this process does not continue in another server. It just stopped.

      What is the problem?  Do I understand wrong about clustering mechanism or I have not configured the clustered correctly?

       

      I made it run in another thread cluster memember not registered

        • 1. Re: Can not forward request to another clustered server
          mike just Master

          I am not sure if this is related. There is such warning message in another server's (server2) log when I shut down one server (server1). Is this causing the request not continuing from server 1 to server2?

           

          2013-12-02 15:58:57,734;[Thread-14 (HornetQ-client-global-threads-459395714)];WARN ;org.hornetq.core.server;HQ222141: Connection failed with failedOver=false: HornetQException[errorType=INTERNAL_ERROR message=HQ119015: Exception in Netty transport]
            at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.exceptionCaught(HornetQChannelHandler.java:107)
            at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:130)
            at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
            at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787)
            at org.jboss.netty.channel.SimpleChannelUpstreamHandler.exceptionCaught(SimpleChannelUpstreamHandler.java:153)
            at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:112)
            at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
            at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
            at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525)
            at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:77)
            at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)
            at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
            at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
            at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
            at java.lang.Thread.run(Thread.java:619)
          Caused by: java.net.SocketException: Connection reset
            at java.net.SocketInputStream.read(SocketInputStream.java:168)
            at java.net.SocketInputStream.read(SocketInputStream.java:182)
            at java.io.FilterInputStream.read(FilterInputStream.java:66)
            at java.io.PushbackInputStream.read(PushbackInputStream.java:122)
            at org.jboss.netty.channel.socket.oio.OioWorker.process(OioWorker.java:64)
            at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:73)
            at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)
            ... 4 more
          
          

           

          This is also logged in another thread Warning message in the log if shutting down one clustered server

          • 2. Re: Can not forward request to another clustered server
            Wolf-Dieter Fink Master

            Mike,

             

            Do you see that the cluster is build by having the message "Members :2"?

            what request you mean? What you try to invoke?

            Could you share the code?

            • 3. Re: Re: Can not forward request to another clustered server
              mike just Master

              Hi Wolf-Dieter,

               

              Yes, I did see the message in the log

              2013-12-02 15:40:35,338;[MSC service thread 1-8];INFO ;org.jboss.as.clustering;JBAS010238: Number of cluster members: 2
              

               

               

              I mean just for a function in my application, it is being hanlded via jms. After I committed the request, I see the log in processing in one server for example server1, then I shut down server1, but now in server2, below warning message occurs

              2013-12-02 15:58:57,734;[Thread-14 (HornetQ-client-global-threads-459395714)];WARN ;org.hornetq.core.server;HQ222141: Connection failed with failedOver=false: HornetQException[errorType=INTERNAL_ERROR message=HQ119015: Exception in Netty transport]  
                at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.exceptionCaught(HornetQChannelHandler.java:107)  
                at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:130)  
                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)  
                at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787)  
                at org.jboss.netty.channel.SimpleChannelUpstreamHandler.exceptionCaught(SimpleChannelUpstreamHandler.java:153)  
                at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:112)  
                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)  
                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)  
                at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525)  
                at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:77)  
                at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)  
                at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)  
                at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)  
                at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)  
                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)  
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)  
                at java.lang.Thread.run(Thread.java:619)  
              Caused by: java.net.SocketException: Connection reset  
                at java.net.SocketInputStream.read(SocketInputStream.java:168)  
                at java.net.SocketInputStream.read(SocketInputStream.java:182)  
                at java.io.FilterInputStream.read(FilterInputStream.java:66)  
                at java.io.PushbackInputStream.read(PushbackInputStream.java:122)  
                at org.jboss.netty.channel.socket.oio.OioWorker.process(OioWorker.java:64)  
                at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:73)  
                at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)  
                ... 4 more  
              

               

              and the point is the process does not continue handling on server2. I tried several functions, they are the same case (the process stopped at once when I shut down one server).

              • 4. Re: Can not forward request to another clustered server
                Justin Bertram Master

                Despite the name of the profile, the "ha" profiles don't have HA configured for HornetQ.  The "ha" profiles have HornetQ clustering configured.  In HornetQ, clustering and HA are independent of each other.  The HornetQ User Guide discusses all this in a fair amount of detail.

                 

                In any event, when you kill one server in a cluster the messages on the killed node do not magically get moved to another cluster node.  Therefore any process on the killed node involving a specific message will not continue on another node.

                • 5. Re: Can not forward request to another clustered server
                  mike just Master

                  Thanks Justin.

                   

                  Can you give me the HornetQ user guide link about the clustering related configuration?

                   

                  And what kind of cases can cluster server handle if they can not magically move requests to another?

                  • 6. Re: Can not forward request to another clustered server
                    Justin Bertram Master

                    I'm not sure which version you are using so you can just go to http://www.jboss.org/hornetq/docs.

                     

                    Clustering is all about load-balancing. 

                     

                    If you want HA functionality (e.g. when one server goes down another server picks up the messages from the dead server) then you'll have to configure a live/backup pair.

                    • 7. Re: Can not forward request to another clustered server
                      mike just Master

                      How to configure the live/backup pair? Are they in the hornetq docs link?

                       

                      I looked at HornetQ QuickStart Guide (because I checked jboss eap 6.1.0 alpha1 hornetq version is 2.3.1.cr1) but did not see any cluster related configurations. Can you advise?

                      • 8. Re: Can not forward request to another clustered server
                        Justin Bertram Master

                        How to configure the live/backup pair? Are they in the hornetq docs link?

                        Yes.  There are 2 clearly marked chapters in the HornetQ User Guide.  One for clustering and one for HA.

                         

                         

                        I looked at HornetQ QuickStart Guide (because I checked jboss eap 6.1.0 alpha1 hornetq version is 2.3.1.cr1) but did not see any cluster related configurations. Can you advise?

                        As the name implies, the HornetQ QuickStart Guide is a quick little guide just to get one started with HornetQ.  The abstract for the document even says, "This Quickstart guide will help you get HornetQ up and running in a few minutes and will explain the basics needed to get started."  The HornetQ User Guide is clearly linked from the page I cited, and it contains the documentation you're looking for.  See the links previously provided in this comment.

                        • 9. Re: Can not forward request to another clustered server
                          mike just Master

                          Thanks Justin, you are right. I have found them in Hornetq user guide.

                           

                          One question is, I see a lot of places mentioning hornetq-configuration.xml, but I did not find it under jboss server directory (I am using JBoss eap 6.1.0 alpha1 version). There is no such xml under standlone configuration folder or domain configuration folder. Can you show me where it is?

                          • 10. Re: Can not forward request to another clustered server
                            Justin Bertram Master

                            The HornetQ User Guide is written for standalone HornetQ which uses hornetq-configuration.xml and a few other config files you won't find in AS/EAP/Wildfly.  However, just about everything mentioned related to XML configuration can go into <hornetq-server> in your standalone*.xml or domain.xml.

                            1 of 1 people found this helpful
                            • 11. Re: Can not forward request to another clustered server
                              mike just Master

                              still not able to get it working. Is there any example for this?

                              • 12. Re: Can not forward request to another clustered server
                                Justin Bertram Master

                                There are several clustering and HA examples in the HornetQ distribution.  Although the file structure is different between standalone HornetQ and Wildfly the basic configuration elements should be the same.

                                • 13. Re: Can not forward request to another clustered server
                                  mike just Master

                                  Thanks. Can you show me where they are? Thanks so much.

                                  • 14. Re: Re: Can not forward request to another clustered server
                                    mike just Master

                                    hornetq-server section from server1's standalone-full-ha.xml

                                     

                                    <failover-on-shutdown>true</failover-on-shutdown>
                                                    <shared-store>true</shared-store>
                                                    <persistence-enabled>false</persistence-enabled>
                                                    <security-enabled>false</security-enabled>
                                                    <journal-type>NIO</journal-type>
                                                    <journal-sync-transactional>false</journal-sync-transactional>
                                                    <journal-sync-non-transactional>false</journal-sync-non-transactional>
                                                    <journal-file-size>10485760</journal-file-size>
                                                    <journal-min-files>10</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>
                                    
                                    
                                                    <broadcast-groups>
                                                        <broadcast-group name="bg-group1">
                                                            <socket-binding>messaging-group</socket-binding>
                                                            <broadcast-period>5000</broadcast-period>
                                                            <connector-ref>
                                                                netty
                                                            </connector-ref>
                                                        </broadcast-group>
                                                    </broadcast-groups>
                                    
                                    
                                                    <discovery-groups>
                                                        <discovery-group name="dg-group1">
                                                            <socket-binding>messaging-group</socket-binding>
                                                            <refresh-timeout>10000</refresh-timeout>
                                                        </discovery-group>
                                                    </discovery-groups>
                                    
                                    
                                                    <cluster-connections>
                                                        <cluster-connection name="my-cluster">
                                                            <address>jms</address>
                                                            <connector-ref>netty</connector-ref>
                                                            <discovery-group-ref discovery-group-name="dg-group1"/>
                                                        </cluster-connection>
                                                    </cluster-connections>
                                    
                                    
                                                    <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>104857600</max-size-bytes>
                                                            <page-size-bytes>10485760</page-size-bytes>
                                                            <address-full-policy>PAGE</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>
                                                        </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>
                                                            <client-failure-check-period>2147483646</client-failure-check-period>
                                                            <connection-ttl>-1</connection-ttl>
                                                            <consumer-window-size>10485760</consumer-window-size>
                                                            <confirmation-window-size>10485760</confirmation-window-size>
                                                            <block-on-non-durable-send>false</block-on-non-durable-send>
                                                            <block-on-durable-send>false</block-on-durable-send>
                                                            <reconnect-attempts>-1</reconnect-attempts>
                                                        </pooled-connection-factory>
                                                    </jms-connection-factories>
                                    

                                     

                                    hornetq-server section from server2's standalone-full-ha.xml

                                    <failover-on-shutdown>true</failover-on-shutdown>
                                                    <shared-store>true</shared-store>
                                                    <persistence-enabled>false</persistence-enabled>
                                                    <security-enabled>false</security-enabled>
                                                    <journal-type>NIO</journal-type>
                                                    <journal-file-size>10485760</journal-file-size>
                                                    <journal-min-files>10</journal-min-files>
                                                    <journal-sync-transactional>false</journal-sync-transactional>
                                                    <journal-sync-non-transactional>false</journal-sync-non-transactional>
                                                    <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>
                                                    <broadcast-groups>
                                                        <broadcast-group name="bg-group1">
                                                            <socket-binding>messaging-group</socket-binding>
                                                            <broadcast-period>5000</broadcast-period>
                                                            <connector-ref>netty</connector-ref>
                                                        </broadcast-group>
                                                    </broadcast-groups>
                                                    <discovery-groups>
                                                        <discovery-group name="dg-group1">
                                                            <socket-binding>messaging-group</socket-binding>
                                                            <refresh-timeout>10000</refresh-timeout>
                                                        </discovery-group>
                                                    </discovery-groups>
                                                    <cluster-connections>
                                                        <cluster-connection name="my-cluster">
                                                            <address>jms</address>
                                                            <connector-ref>netty</connector-ref>
                                                            <discovery-group-ref discovery-group-name="dg-group1"/>
                                                        </cluster-connection>
                                                    </cluster-connections>
                                                    <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>
                                                        <!--default for catch all-->
                                                        <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>104857600</max-size-bytes>
                                                            <page-size-bytes>10485760</page-size-bytes>
                                                            <address-full-policy>PAGE</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>
                                                        </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>
                                                            <client-failure-check-period>2147483646</client-failure-check-period>
                                                            <connection-ttl>-1</connection-ttl>
                                                            <reconnect-attempts>-1</reconnect-attempts>
                                                            <confirmation-window-size>10485760</confirmation-window-size>
                                                            <consumer-window-size>10485760</consumer-window-size>
                                                            <block-on-durable-send>false</block-on-durable-send>
                                      <block-on-non-durable-send>false</block-on-non-durable-send>
                                                        </pooled-connection-factory>
                                                    </jms-connection-factories>
                                    

                                     

                                    I have not pasted the jms-destinations since there are a lot of them.

                                     

                                    When one server is shut down by just closing the console, there will be such log information occuring in another server:

                                    2013-12-06 13:31:35,940;[Thread-49 (HornetQ-client-global-threads-884044527)];WARN ;org.hornetq.core.server;HQ222141: Connection failed with failedOver=false: HornetQException[errorType=INTERNAL_ERROR message=HQ119015: Exception in Netty transport]
                                      at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.exceptionCaught(HornetQChannelHandler.java:107)
                                      at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:130)
                                      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
                                      at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787)
                                      at org.jboss.netty.channel.SimpleChannelUpstreamHandler.exceptionCaught(SimpleChannelUpstreamHandler.java:153)
                                      at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:112)
                                      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
                                      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
                                      at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525)
                                      at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:77)
                                      at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)
                                      at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
                                      at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
                                      at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)
                                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                                      at java.lang.Thread.run(Thread.java:619)
                                    Caused by: java.net.SocketException: Connection reset
                                      at java.net.SocketInputStream.read(SocketInputStream.java:168)
                                      at java.net.SocketInputStream.read(SocketInputStream.java:182)
                                      at java.io.FilterInputStream.read(FilterInputStream.java:66)
                                      at java.io.PushbackInputStream.read(PushbackInputStream.java:122)
                                      at org.jboss.netty.channel.socket.oio.OioWorker.process(OioWorker.java:64)
                                      at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:73)
                                      at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51)
                                      ... 4 more
                                    
                                    
                                    2013-12-06 13:31:37,369;[VERIFY_SUSPECT.TimerThread,web,gs1/web];INFO ;org.jboss.as.clustering;JBAS010232: Suspected member: gs2/web
                                    2013-12-06 13:31:37,513;[Incoming-9,shared=udp];INFO ;org.jboss.as.clustering;JBAS010225: New cluster view for partition web (id: 4, delta: -1, merge: false) : [gs1/web]
                                    2013-12-06 13:31:37,514;[Incoming-9,shared=udp];INFO ;org.infinispan.remoting.transport.jgroups.JGroupsTransport;ISPN000094: Received new cluster view: [gs1/web|4] [gs1/web]
                                    2013-12-06 13:32:22,523;[hornetq-failure-check-thread];WARN ;org.hornetq.core.client;HQ212107: Connection failure has been detected: HQ119034: Did not receive data from /127.0.0.1:50104. 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]
                                    2013-12-06 13:32:22,526;[hornetq-failure-check-thread];WARN ;org.hornetq.core.server;HQ222100: Client connection failed, clearing up resources for session 91411375-5e37-11e3-b50c-9f04c7b23a8f
                                    2013-12-06 13:32:22,531;[hornetq-failure-check-thread];WARN ;org.hornetq.core.server;HQ222158: Cleared up resources for session 91411375-5e37-11e3-b50c-9f04c7b23a8f
                                    
                                    

                                     

                                    I supposed the second server can take over the request and continue it successfully but it does not.

                                     

                                    Can you help check if anything not configured correctly? I really have followed the hornetq user manual

                                    Chapter 39. High Availability and Failover

                                    but I am not sure if I have still missed some parameters for the correct configuration.

                                    1 2 Previous Next