1 2 Previous Next 27 Replies Latest reply on Oct 20, 2009 9:29 AM by Ovidiu Guse

    Bridge error because of network problems also influences oth

    Markus Lutum Novice

      Hi Tim, Hi Howard.

      Its me again and I a remoting problem.

      I am using JBM 1.4.2.GA.SP1 with remoting SP11Brew.

      I have 4 Jboss 4.2.3GA instances A B C X (non clustered)

      A C and X are running on the same machine (OVSPC186) using different ports (development)
      B is running on a different one. (NVC1218)

      On X I have configured 2 Bridges to each other instance where one is sending data to the instance and the other one receives data from the instance. So I have 6 Bridges deployed on X.
      Bridge QOS level set to 2 means XA.

      The whole system works fine sending messages around.

      Now a strange thing happens:
      I kill the remote instance B or unplug network cable to simulate network errors. Then the expected thing happens. The bridges to B detect the erros and retry in my defined time of 50s.
      BUT somehow also the other bridges crashing now. I would assume that they are NOT influenced on that B instance problem.
      When I kill the local instance A or C I never saw this behavior.

      This is reproduceable and I thing I have noticed that while I have tested the upgrade from 1.4.0.SP3 to 1.4.0.SP3.CP04 ( in production I am using 1.4.0.SP3 )

      The stacktraces and output of the logger:

      Detection of instance B problems

      09:09:43,546 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AeosB,service=Bridge Detected failure on connection
      javax.jms.JMSException: Failure on underlying remoting connection
       at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
       at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
      09:09:49,515 ERROR [SocketClientInvoker] Got marshalling exception, exiting
      java.net.SocketException: Connection reset
       at java.net.SocketInputStream.read(SocketInputStream.java:168)
       at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
       at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)
       at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
       at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
       at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
       at java.io.FilterInputStream.read(FilterInputStream.java:66)
       at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:988)
       at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:621)
       at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:422)
       at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:133)
       at org.jboss.remoting.ConnectionValidator.doCheckConnectionWithLease(ConnectionValidator.java:548)
       at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:328)
       at java.util.TimerThread.mainLoop(Timer.java:512)
       at java.util.TimerThread.run(Timer.java:462)
      09:09:49,578 ERROR [SocketClientInvoker] Got marshalling exception, exiting
      java.net.SocketException: Connection reset
       at java.net.SocketInputStream.read(SocketInputStream.java:168)
       at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
       at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)
       at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
       at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
       at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
       at java.io.FilterInputStream.read(FilterInputStream.java:66)
       at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:988)
       at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:621)
       at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:422)
       at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:133)
       at org.jboss.remoting.LeasePinger.stopPing(LeasePinger.java:93)
       at org.jboss.remoting.MicroRemoteClientInvoker.terminateLease(MicroRemoteClientInvoker.java:353)
       at org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask.run(ConnectionValidator.java:693)
       at java.util.TimerThread.mainLoop(Timer.java:512)
       at java.util.TimerThread.run(Timer.java:462)
      09:09:49,578 WARN [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslbisocket://nvc1218:44457//?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&stopLeaseOnFailure=true&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
      09:09:49,593 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[g2-rgxo5xrf-1-dqio5xrf-qtzfw4-2227p4]: method getXAResource() did not go through, the interceptor is CLOSED
      09:09:49,640 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:49,640 WARN [Bridge] jboss.messaging:name=IncommingBridge_AeosB,service=Bridge Detected failure on connection
      javax.jms.JMSException: Failure on underlying remoting connection
       at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
       at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
      09:09:49,640 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:47 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:49,703 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:49,718 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:47 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:49,718 WARN [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslbisocket://nvc1218:44457//?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&stopLeaseOnFailure=true&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
      09:09:49,718 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AeosB,service=Bridge Will retry after a pause of 50000 ms
      09:09:49,718 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[t2-w1cj5xrf-1-59rc5xrf-zn9jwb-26z24a]: method getXAResource() did not go through, the interceptor is CLOSED
      09:09:49,734 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:49,734 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:26 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:49,734 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:49,734 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:26 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:49,734 WARN [Bridge] jboss.messaging:name=IncommingBridge_AeosB,service=Bridge Will retry after a pause of 50000 ms
      


      But then 3,5 seconds later the Bridge to C has problems which is the strange thing to investigate. C is on OVSPC186 which is the same machine as this instance X:
      09:09:53,312 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSC,service=Bridge Detected failure on connection
      javax.jms.JMSException: Failure on underlying remoting connection
       at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
       at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
      09:09:56,406 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[w2-iixo5xrf-1-dqio5xrf-qtzfw4-2227p4]: method getXAResource() did not go through, the interceptor is CLOSED
      09:09:56,406 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:56,406 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:51 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:56,406 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
      09:09:56,406 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:6db:49af887e:51 received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
      09:09:56,406 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSC,service=Bridge Will retry after a pause of 50000 ms
      



      here also the debug output. It seems that the connectionValidator detects problems.

      09:09:53,312 DEBUG [org.jboss.remoting.ConnectionValidator] ConnectionValidator[SocketClientInvoker[1ac6103, sslbisocket://OVSPC186:34457], pingPeriod=2000 ms]'s connections is invalid
      09:09:53,312 DEBUG [org.jboss.remoting.InvokerRegistry] decremented SocketClientInvoker[1ac6103, sslbisocket://OVSPC186:34457]'s count, current count 1
      09:09:53,312 DEBUG [org.jboss.remoting.ConnectionValidator] ConnectionValidator[SocketClientInvoker[1ac6103, sslbisocket://OVSPC186:34457], pingPeriod=2000 ms] stopped, returning true
      09:09:53,312 DEBUG [org.jboss.remoting.ConnectionValidator] org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask@1106f61 detected connection failure: stopping LeasePinger
      09:09:53,312 WARN [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=OutgoingBridge_AEOSC,service=Bridge Detected failure on connection
      javax.jms.JMSException: Failure on underlying remoting connection
       at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
       at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
      09:09:53,312 DEBUG [org.jboss.remoting.LeasePinger] LeasePinger[SocketClientInvoker[1333004, sslbisocket://OVSPC186:34457](4p7222-4wfztq-frx5oiqd-1-frx5ovr4-18)] setting disconnect timeout to: -1
      09:09:53,312 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] unregistered connection ConnectionEndpoint[q2-mhxo5xrf-1-dqio5xrf-qtzfw4-2227p4] with remoting session ID ...-frx5oxh7-2k
      09:09:53,312 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] removing callback handler ServerInvokerCallbackHandler[4p7222-4wfztq-frx5oiqd-1-frx5oxh7-2k+4p7222-4wfztq-frx5oiqd-1-frx5oxh7-2n]
      09:09:53,312 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@1933cc from registry
      09:09:53,312 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) removing client callback handler with session id of 4p7222-4wfztq-frx5oiqd-1-frx5oxh7-2k+4p7222-4wfztq-frx5oiqd-1-frx5oxh7-2n.
      09:09:53,312 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] unrecognized listener ID: 4p7222-4wfztq-frx5oiqd-1-frx5oxh7-2n
      09:09:53,312 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@97a376 from registry
      09:09:53,312 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] stopped
      09:09:53,312 DEBUG [org.jboss.remoting.InvokerRegistry] decremented org.jboss.remoting.transport.local.LocalClientInvoker@1b147ab's count, current count 4
      09:09:53,312 DEBUG [org.jboss.remoting.InvokerRegistry] decremented org.jboss.remoting.transport.local.LocalClientInvoker@1d83ac7's count, current count 4
      09:09:54,890 DEBUG [org.jboss.remoting.ConnectionValidator] ConnectionValidator[SocketClientInvoker[1ac6103, sslbisocket://OVSPC186:34457], pingPeriod=2000 ms] shut down lease pinger
      09:09:56,406 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) removing client callback handler with session id of 4p7222-4wfztq-frx5oiqd-1-frx5oxhm-2r+4p7222-4wfztq-frx5oiqd-1-frx5oxi2-2u.
      09:09:56,406 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] shutting down control connection: 4p7222-4wfztq-frx5oiqd-1-frx5oxi2-2u
      09:09:56,406 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@8ce172 from registry
      09:09:56,406 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] stopped
      09:09:56,406 DEBUG [org.jboss.remoting.InvokerRegistry] decremented SocketClientInvoker[1333004, sslbisocket://OVSPC186:34457]'s count, current count 1
      09:09:56,406 DEBUG [org.jboss.remoting.InvokerRegistry] decremented SocketClientInvoker[1b52a38, sslbisocket://OVSPC186:34457]'s count, current count 1
      09:09:56,406 ERROR [org.jboss.jms.client.container.ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[w2-iixo5xrf-1-dqio5xrf-qtzfw4-2227p4]: method getXAResource() did not go through, the interceptor is CLOSED
      





        • 1. Re: Bridge error because of network problems also influences
          Markus Lutum Novice

          Some further test:

          I also tried to kill instance A, so a local instance. Then also C is influenced once. After my 50s retrytime the bridge to C is back again.
          (no, C is not the problem. It also happes the other way round)

          After restarting instance A the connection from X to A is reestablished but then it failed 2 time again with messages like the example above. Between the reconnect and disconnect it always took around 3 seconds:

          09:44:41,421 INFO [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Succeeded in reconnecting to servers
          09:44:44,437 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Detected failure on connection
          javax.jms.JMSException: Failure on underlying remoting connection
           at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:102)
           at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:641)
          09:44:44,484 ERROR [ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[c7-xv1z6xrf-1-k6dr6xrf-d1wvvl-2227p4]: method getXAResource() did not go through, the interceptor is CLOSED
          09:44:44,484 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
          09:44:44,484 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:82d:49af8f92:ea received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
          09:44:44,484 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XAER_NOTA
          09:44:44,484 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_54] - Top-level abort of action -5601fdfe:82d:49af8f92:ea received TwoPhaseOutcome.FINISH_ERROR from <ClassName:RecordType.JTA_RECORD>
          09:44:44,484 WARN [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Will retry after a pause of 50000 ms
          09:45:34,609 INFO [Bridge] jboss.messaging:name=OutgoingBridge_AEOSA,service=Bridge Succeeded in reconnecting to servers
          


          • 2. Re: Bridge error because of network problems also influences
            Markus Lutum Novice


            I also noticed then that in this case above where the message bridge is reconnected no messages are send anymore.

            I debugged in the code because I first thought that the BatchTimeChecker was failing. But this works fine.
            I also see that the message list was empty.
            Then I created a new message on instance A and checked if the Bridge$SourceListener.onMessage() is called. BUT IT ISN'T!

            What in hell is the problem :-)....
            From outside it seems that the Bridge is working but the messages are not received by the Message Bridge!

            • 3. Re: Bridge error because of network problems also influences
              Tim Fox Master

              Did you give each node a unique serverpeerid?

              • 4. Re: Bridge error because of network problems also influences
                Markus Lutum Novice

                Hi Tim....

                AHHHHHHHH
                What a stupid beginner error!

                Someone else changed the configuration scripts which creates the deployment files and I have not checked it because it worked before.

                Ok now I can explain most of the errors. I have to retest.
                Results are postet to this thread.... sorry for time stealing....

                • 5. Re: Bridge error because of network problems also influences
                  Markus Lutum Novice

                  Hi Tim!

                  Sorry... forget my last mail!

                  My fault. One Server was startet 2 times or at least the old output was shown so I thought the serverpeers are the same.
                  BUT THEY DON'T .
                  4 Servers 4 ServerPeers.

                  Behaviour retested and still happens....
                  Have not tested this A SourceListener Issue yet.... But I definatly see the crahing connections on none related bridges like my first posts.


                  • 6. Re: Bridge error because of network problems also influences
                    Markus Lutum Novice

                    And the last issue that the messages are NOT delivered anymore after the queue has reconnected is also true.
                    Now this happens on C which were never stopped but lost connection while B has restarted.

                    • 7. Re: Bridge error because of network problems also influences
                      Markus Lutum Novice

                      another hint..
                      Maybe helps. I have no Idea what this means.

                      If i stop the bridge which seems to hang and start it again I got some strange messages in my logfile:

                      12:04:33,640 WARN [ClientConsumer] Timed out waiting for last delivery 4 got 1
                      12:04:33,843 WARN [LeasePinger] LeasePinger[SocketClientInvoker[6d7809, sslbisocket://OVSPC186:34457](4p7222-46h04s-frx8po6g-1-frx8uqso-3l)] tried to remove lease for client with session ID 4p7222-46h04s-frx8po6g-1-frx8vzo4-4t, but no such lease was found
                      12:04:33,890 INFO [BridgeService] Stopped bridge BridgeService
                      12:05:16,671 INFO [BridgeService] Started bridge BridgeService. Source: /queue/local_incomingSyncRequests Target: /queue/incomingSyncRequests
                      


                      Then the messages are transported again....

                      • 8. Re: Bridge error because of network problems also influences
                        Yong Hao Gao Master

                        Sorry mclu, I know you have A B C and X 4 nodes non-clustered,
                        A, C and X on one machine and B on another. I'm not clear how your bridges are deployed. You said:

                        "On X I have configured 2 Bridges to each other instance where one is sending data to the instance and the other one receives data from the instance. So I have 6 Bridges deployed on X.
                        Bridge QOS level set to 2 means XA. "

                        Did you mean A, C and X have 2 bridges deployed each and B has no bridge?

                        Can you give more details on how you messages flows over those bridges?

                        • 9. Re: Bridge error because of network problems also influences
                          Markus Lutum Novice

                          Hi Howard!

                          No sorry... not easy to explain :-)

                          All 6 Bridges are deployed on X
                          X is our so called root server which do the message processing and delegates the messages to the other nodes.

                          A, B and C are our nodes/instances which only uses local queues. Each node has an incoming and an outgoing queue.

                          X has 3 JMSProviderLoader configured. One for each node.
                          The

                          example:

                           <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoaderRemote,name=RemoteJMSProvider_AeosA">
                          <attribute name="ProviderName">RemoteJMSProvider_AeosA</attribute>
                          <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
                           <!-- The combined connection factory -->
                           <attribute name="FactoryRef">/XAConnectionFactory</attribute>
                           <!-- The queue connection factory -->
                           <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute>
                           <!-- The topic factory -->
                           <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute>
                           <attribute name="Properties">
                           java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
                           java.naming.factory.url.pkgs=org.jnp.interfaces
                           java.naming.provider.url=localhost:2099
                           </attribute>
                          </mbean>
                          


                          Because there are 3 Nodes I have 3 Bridges for the incoming queue and 3 Bridges for the outgoing queue on instance X.

                          On X there are also only 2 queues. The incoming bridges are sending all messages from "ABC incoming" to "X incoming".
                          The Outgoing bridges uses selectors to only fetch the node (ABC) related messages out of the outgoing queue of X.


                          In production we only have remote nodes. Currently 8 nodes and one root server X.


                          • 10. Re: Bridge error because of network problems also influences
                            Yong Hao Gao Master

                            ok thanks. Now I understand the model of your app. So X acts as a central message hub, it collects all messages from ABC and selectively distribute the messages out to ABC's outgoing queues.

                            I just got this jira
                            https://jira.jboss.org/jira/browse/JBMESSAGING-1543

                            I think your issue is similar to that one.

                            • 12. Re: Bridge error because of network problems also influences
                              Markus Lutum Novice

                              Hi Howard.

                              Yes... I thing this is related to the message not bridges issue... But whats about the main issue, that other bridges are influenced by problems of another??

                              • 13. Re: Bridge error because of network problems also influences
                                Markus Lutum Novice

                                Does https://jira.jboss.org/jira/browse/JBMESSAGING-1456 is maybe an explanation why the bridges/connections are influencing each other??

                                • 14. Re: Bridge error because of network problems also influences
                                  Yong Hao Gao Master

                                  I don't think this is related to JBMESSAGING-1456. This is likely a bridge issue.

                                  1 2 Previous Next