[JBoss JIRA] (WFWIP-67) [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-67?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak commented on WFWIP-67:
-------------------------------------
[~clebert.suconic] I've updated steps to rerproduce. There is used EAP 7.1.0.GA as old server and then latest WF/Artemis 2.x build from you [1] for new server.
Note that there is no Artemis cluster between old and new servers. It's common LODH scenario. Two old JMS servers in cluster. Then 2 new servers in connecting by remote JCA to old JMS cluster. JMS servers are sequentially killed and started again.
IndexOutOfBoundsException is thrown from receiver which consumes messages from OutQueue at the end of the test. It receives malformed message thus IndexOutOfBoundsException.
[1] https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
> [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-67
> URL: https://issues.jboss.org/browse/WFWIP-67
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
>
> *Scenario:*
> Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
> MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
> Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
> # Client sends messages to InQueue on node A
> # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
> # During processing of messages nodes A and C are killed
> # Client reads messages from OutQueue on node B.
> *Issue*
> At the end of the test, client is not able to read message
> {code}
> java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
> at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
> 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:224)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-67) [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-67?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-67:
--------------------------------
Steps to Reproduce:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=http://download.eng.brq.redhat.com/devel/candidates/JBEAP/to_be_deleted/JBEAP-7.1.0/jboss-eap-7.1.0.zip 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
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ResourceAdapterCompatibilityTestCase#oldJmsNewMdbWithStaticConnectorKill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log
{code}
was:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=http://download.eng.brq.redhat.com/devel/candidates/JBEAP/to_be_deleted/JBEAP-7.1.0/jboss-eap-7.1.0.zip 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
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ResourceAdapterCompatibilityTestCase#OldJmsNewMdbWithStaticConnectorKill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log
{code}
> [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-67
> URL: https://issues.jboss.org/browse/WFWIP-67
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
>
> *Scenario:*
> Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
> MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
> Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
> # Client sends messages to InQueue on node A
> # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
> # During processing of messages nodes A and C are killed
> # Client reads messages from OutQueue on node B.
> *Issue*
> At the end of the test, client is not able to read message
> {code}
> java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
> at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
> 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:224)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-67) [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-67?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-67:
--------------------------------
Steps to Reproduce:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=http://download.eng.brq.redhat.com/devel/candidates/JBEAP/to_be_deleted/JBEAP-7.1.0/jboss-eap-7.1.0.zip 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
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ResourceAdapterCompatibilityTestCase#OldJmsNewMdbWithStaticConnectorKill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log
{code}
was:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-JMS/view/early-testing/view/tooling/job/early-testing-messaging-prepare/545/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-JMS/view/early-testing/view/tooling/job/early-testing-messaging-prepare/546/artifact/jboss-eap.zip 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
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ResourceAdapterCompatibilityTestCase#OldJmsNewMdbWithStaticConnectorKill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log
{code}
> [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-67
> URL: https://issues.jboss.org/browse/WFWIP-67
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
>
> *Scenario:*
> Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
> MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
> Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
> # Client sends messages to InQueue on node A
> # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
> # During processing of messages nodes A and C are killed
> # Client reads messages from OutQueue on node B.
> *Issue*
> At the end of the test, client is not able to read message
> {code}
> java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
> at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
> 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:224)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10630) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10630?page=com.atlassian.jira.plugin... ]
Stuart Douglas commented on WFLY-10630:
---------------------------------------
This appears to be a clustering issue. Clustering is making two instances of the session manager, which means that they are not sharing listeners (just the backing cache).
> HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-10630
> URL: https://issues.jboss.org/browse/WFLY-10630
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final, 13.0.0.Final
> Environment: Windows 10, Java 1.8.0_131
> Reproducible with both WildFly-10.0.0.Final and Wildfly-13.0.0.Final
> Reporter: Bernhard Kabelka
> Assignee: Bartosz Baranowski
> Attachments: LoginForm.png, roles.properties, sessionlistener-test.ear, standalone.xml, users.properties
>
>
> For sessions shared across different WARs in a single EAR, the notification of HttpSessionListener works differently in WildFly 10.0.0.Final (and Wildfly 13.0.0.Final) than it it used to work in WildFly 8.2.0.Final:
> I have an EAR containing two WARs with enabled session sharing across the WARs. Basically, one WAR contains the web UI, and the other WAR contains the REST interfaces for AJAX calls made by the UI. The user authenticates against the UI-WAR. On logout, a REST method in the AJAX-WAR is triggered which calls HttpSession.invalidate() on the user session.
> In WildFly 8.2.0.Final, a HttpSessionListener in the UI-WAR gets notified immediately about session creation and destruction.
> In WildFly 13.0.0.Final, however, a HttpSessionListener in either WAR only gets one of the two notifications:
> * In the UI-WAR, I get a notification about the created session immediately when the login form is loaded. However, I do not receive any notification about the session destruction (unless it times out).
> * In the AJAX-WAR, I do not get any notification about the session creation at all, but I immediately receive a notification about the session destruction.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-92) SNI - circular dependency causes server to crash
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFWIP-92?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas resolved WFWIP-92.
---------------------------------
Resolution: Done
> SNI - circular dependency causes server to crash
> ------------------------------------------------
>
> Key: WFWIP-92
> URL: https://issues.jboss.org/browse/WFWIP-92
> Project: WildFly WIP
> Issue Type: Bug
> Environment: Wildfly build with undertow and wildfly-core modules build from following sources:
> * https://github.com/stuartwdouglas/undertow/tree/sni
> * https://github.com/stuartwdouglas/wildfly-core/tree/sni
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Labels: SNI
>
> When I try to utilize recently added {{server-ssl-sni-context}} and put its reference again in the {{sni-mapping}}, after a server reload the server completely crash and one has to restore configuration manually:
> {code:title=command example}
> /subsystem=elytron/server-ssl-sni-context=srvSniSslCtx/sni-mapping=server:add(ssl-context=srvSniSslCtx)
> {code}
> {code:title=server.log output}
> 22:58:51,998 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 44) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-sni-context" => "srvSniSslCtx")
> ]): org.jboss.msc.service.CircularDependencyException: Container jboss-as has a circular dependency: [service org.wildfly.security.ssl-context.srvSniSslCtx]
> at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:803)
> at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:784)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:761)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2056)
> at org.jboss.msc.service.ObsoleteServiceBuilderImpl.install(ObsoleteServiceBuilderImpl.java:293)
> at org.jboss.as.controller.OperationContextImpl.installService(OperationContextImpl.java:2034)
> at org.jboss.as.controller.OperationContextImpl.access$600(OperationContextImpl.java:132)
> at org.jboss.as.controller.OperationContextImpl$2$1.installService(OperationContextImpl.java:761)
> at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:2165)
> at org.jboss.msc.service.DelegatingServiceBuilder.install(DelegatingServiceBuilder.java:104)
> at org.wildfly.extension.elytron.TrivialAddHandler.performRuntime(TrivialAddHandler.java:72)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
> I understand that such configuration does not make sense, although it would be nice if we could detect this problem ahead to avoid server crush. Is it possible?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-67) [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Clebert Suconic (JIRA)
[ https://issues.jboss.org/browse/WFWIP-67?page=com.atlassian.jira.plugin.s... ]
Clebert Suconic commented on WFWIP-67:
--------------------------------------
Is this about mixing versions in clustering?
I don't think that should be allowed. Clustering should require versions aligned. (if that's the case.. which it seems )
> [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-67
> URL: https://issues.jboss.org/browse/WFWIP-67
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
>
> *Scenario:*
> Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
> MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
> Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
> # Client sends messages to InQueue on node A
> # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
> # During processing of messages nodes A and C are killed
> # Client reads messages from OutQueue on node B.
> *Issue*
> At the end of the test, client is not able to read message
> {code}
> java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
> at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
> 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:224)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months