In previous releases of JBoss EAP 6, users encountered issues with Clustered Grouping, whereing routing messages could be interrupted and give invalid answers.
In this release the communication between the nodes has been improved, as has the reaping process of groups to avoid this and other spurious messages that could happen across clustered grouping.
Description of problem:
The publisher is not able to send , getting following exception:
HornetQException[errorCode=100 message=HQ119016: queue jms.queue.skyboxOrderingQueue1d114bc5-b003-11e3-9692-45dbfcba4397 has been removed cannot deliver message, queues should not be removed when grouping is used]
[espressohiloservice H#90-r#85:0 E] 2014-05-08 14:05:11.0200 at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312)
[espressohiloservice H#90-r#85:0 E] 2014-05-08 14:05:11.0200 at org.hornetq.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:287)
[espressohiloservice H#90-r#85:0 E] 2014-05-08 14:05:11.0200 at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:142)
[espressohiloservice H#90-r#85:0 E] 2014-05-08 14:05:11.0200 at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:147)
[espressohiloservice H#90-r#85:0 E] 2014-05-08 14:05:11.0200 at com.apple.skybox.common.util.HornetClient.send(HornetClient.java:309)
Version-Release number of selected component (if applicable):
Server hornetQ version - 2.3.1 final
Applied patches - bz1025862
Client publisher hornetQ version - 2.2.16
Steps to Reproduce:
Andy Taylor has written a testcase which will be part of this fix.
I'm working on it as we speak... I think I will have this fixed by 26th of may after tests.
One-of back porting this into 6.1.0:
Verified in EAP 6.3.0.ER7.
Making public for inclusion in 6.3.0 Release Notes.