Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13950

[GSS](7.1.z) ARTEMIS-1639 - MDB does no longer receive messages after broker was restarted

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.3.CR1, 7.1.3.GA
    • 6.4.0.GA, 7.0.8.CR1
    • JMS
    • None
    • CR1
    • Workaround Exists
    • Hide

      Restart the EAP 7 server on which MDB is deployed. Once the server is restarted it as able to reconnect.

      Show
      Restart the EAP 7 server on which MDB is deployed. Once the server is restarted it as able to reconnect.
    • Hide

      1. Attached is the standalone configuration for each EAP.
      2. We have broker configured in EAP 6
      3. We have MDB configured in EAP 7.
      4. Using the code MessageConsumer.java we are able to consume message successfully.
      5. Restart EAP 6 the MDB on EAP 7 will not be able to reconnect.

      Show
      1. Attached is the standalone configuration for each EAP. 2. We have broker configured in EAP 6 3. We have MDB configured in EAP 7. 4. Using the code MessageConsumer.java we are able to consume message successfully. 5. Restart EAP 6 the MDB on EAP 7 will not be able to reconnect.
    • EAP 7.1.3

    Description

      The use case in which we use external context to lookup a destination in remote EAP 6 instances and try to send a message to it does not work. We can create a destination and then send a message but after restarting EAP 6 the EAP 7 RA never reconnects to the remote EAP 6 instance so the MDB can't consume any messages.

      I see those errors in EAP6 logs

      14:31:49,404 WARN [org.hornetq.core.client] (Old I/O server worker (parentId: 1281942433, [id: 0x4c68e3a1, /192.168.1.109:5445]), runningThread=Thread-30 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=1685594d-d8fe-11e7-bb77-93f7004eb4f4-1521177293-339693078)) HQ212037: Connection failure has been detected: java.lang.IllegalArgumentException: HQ119032: Invalid type: -4 [code=GENERIC_EXCEPTION]
      14:31:49,405 WARN [org.hornetq.core.client] (Old I/O server worker (parentId: 1281942433, [id: 0x4c68e3a1, /192.168.1.109:5445]), runningThread=Thread-21 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=1685594d-d8fe-11e7-bb77-93f7004eb4f4-1521177293-339693078)) HQ212037: Connection failure has been detected: java.lang.IllegalArgumentException: HQ119032: Invalid type: -4 [code=GENERIC_EXCEPTION]
      14:31:49,404 WARN [org.hornetq.core.server] (Old I/O server worker (parentId: 1281942433, [id: 0x4c68e3a1, /192.168.1.109:5445]), runningThread=Thread-23 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=1685594d-d8fe-11e7-bb77-93f7004eb4f4-1521177293-339693078)) Failed to decode buffer, disconnect immediately.: java.lang.IllegalStateException: java.lang.IllegalArgumentException: HQ119032: Invalid type: -4
      at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:582) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:589) [hornetq-server-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:72) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:281) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.socket.oio.OioWorker.process(OioWorker.java:71) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:73) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_144]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_144]
      at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_144]
      Caused by: java.lang.IllegalArgumentException: HQ119032: Invalid type: -4
      at org.hornetq.core.protocol.core.impl.PacketDecoder.decode(PacketDecoder.java:434) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.hornetq.core.protocol.ServerPacketDecoder.decode(ServerPacketDecoder.java:180) [hornetq-server-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:536) [hornetq-core-client-2.3.25.SP22-redhat-1-bz-1519198.jar:]
      ... 22 more

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-14387 [GSS](7.1.z) Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          ARTEMIS-1639 Loading...

          Activity

            People

              thofman Tomas Hofman
              raisaurabh Saurabh Rai (Inactive)
              Peter Mackay Peter Mackay
              Peter Mackay Peter Mackay
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: