Description of problem: HornetQ JMS bridge does not remove vendor specific properties from message headers when handing over (forwarding) messages to a thirdparty JMS broker. This occurs on a JMS bridge that has been configured from a HornetQ cluster to a thirdparty JMS broker. The HornetQ assigns "_HQ_ROUTE_TOsf.my-cluster" header property to messages for routing within the cluster. However that header property does not get removed from messages by the JMS bridge. Version-Release number of selected component (if applicable): JBoss-EAP-6.4.13 HornetQ-2.3.25-SP16 How reproducible: Steps to Reproduce: 1. Please configure a HornetQ load balancing cluster 2. Please configure a JMS bridge on one node to a remote Weblogic server 3. The exception gets thrown if messages get routed within the HornetQ cluster Actual results: Expected results: Additional info:
The PR: https://github.com/hornetq/hornetq/pull/2114
The only issue really is that this is not fixed in Artemis. you fix it now, later customer updates... the issue will be in Artemis.
Hi Clebert, once you approved this fix, I'll port it to Artemis upstream immediately, I believe the issue is similar in Artemis. Is that ok? Howard
Hi Clebert, I think I got you wrong. I'll submit a PR to Artemis. Sorry about that. Howard
Adding to 6.4.18 payload, since it's already merged.
Upstream issue: https://issues.jboss.org/browse/JBEAP-13421
I am not able to reproduce the issue. Regression tests are OK, function test passes. Verified with EAP 6.4.18.CP.CR1
Released on Nov 14 2017 as part of EAP 6.4.18.