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

Exception on subscriber during failback on replication

XMLWordPrintable

    • Release Notes
    • Regression
    • should be fixed in 011 release
    • Documented as Known Issue
    • Hide

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git

      cd eap-tests-hornetq/scripts/

      git checkout refactoring_modules

      groovy -DEAP_VERSION=7.0.0.ER4 PrepareServers7.groovy

      export WORKSPACE=$PWD

      export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap

      export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap

      export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap

      export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

      export JOURNAL_DIRECTORY_A=$WORKSPACE/journal-A

      export JOURNAL_DIRECTORY_B=$WORKSPACE/journal-B

      cd ../jboss-hornetq-testsuite/

      mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackClientAckTopic -DfailIfNoTests=false -Deap=7x | tee log

      Show
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout refactoring_modules groovy -DEAP_VERSION=7.0.0.ER4 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap export JOURNAL_DIRECTORY_A=$WORKSPACE/journal-A export JOURNAL_DIRECTORY_B=$WORKSPACE/journal-B cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackClientAckTopic -DfailIfNoTests=false -Deap=7x | tee log
    • EAP 7.0.1

      In manually created colocated topolgy (using netty connectors) subscriber fails to consume messages after failback due to this exception:

      00:31:52,730 Thread-535 ERROR [org.jboss.qa.hornetq.apps.clients.SubscriberClientAck:207] Exception was thrown during receiving messages:
      java.lang.IndexOutOfBoundsException: readerIndex(22) + length(409600) exceeds writerIndex(3580): UnpooledHeapByteBuf(ridx: 22, widx: 3580, cap: 3580)
      at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1165)
      at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:675)
      at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:683)
      at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:511)
      at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:86)
      at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:68)
      at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37)
      at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112)
      at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.getMessage(ActiveMQMessageConsumer.java:204)
      at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:119)
      at org.jboss.qa.hornetq.apps.clients.SubscriberClientAck.receiveMessage(SubscriberClientAck.java:326)
      at org.jboss.qa.hornetq.apps.clients.SubscriberClientAck.run(SubscriberClientAck.java:169)
      Exception in thread "Thread-535" java.lang.RuntimeException: Fatal exception was thrown in subscriber. Subscriber for node: 127.0.0.1

      Note: we don't have 100% reproducer for this its just one of our tests which hit the issue.

      Customer impact: Receiver.receive() may throw IndexOutOfBoundsException which causes that standalone JMS client fails and stops to receive messages. This issue can be hit by client connected to live/backup with replicated journal after failover/failback.

              mtaylor1@redhat.com Martyn Taylor (Inactive)
              okalman@redhat.com Ondřej Kalman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: