Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1431406

Summary:	[GSS](6.4.z) HornetQ JMS bridge does not remove vendor specific properties from message headers
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tyronne Wickramarathne <tywickra>
Component:	HornetQ	Assignee:	Yong Hao Gao <hgao>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Miroslav Novak <mnovak>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4.13	CC:	bmaxwell, cdewolf, csuconic, istudens, jbilek, msochure, msvehla, rstancel, thofman
Target Milestone:	CR1
Target Release:	EAP 6.4.18
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 18:28:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1463709, 1464499

Description Tyronne Wickramarathne 2017-03-12 08:28:39 UTC

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:

Comment 1 Yong Hao Gao 2017-03-17 03:09:42 UTC

The PR:

https://github.com/hornetq/hornetq/pull/2114

Comment 5 Clebert Suconic 2017-05-29 14:31:32 UTC

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.

Comment 6 Yong Hao Gao 2017-05-31 01:44:36 UTC

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

Comment 7 Yong Hao Gao 2017-06-12 01:47:46 UTC

Hi Clebert,

I think I got you wrong. I'll submit a PR to Artemis.
Sorry about that.

Howard

Comment 10 Tomas Hofman 2017-10-09 06:44:13 UTC

Adding to 6.4.18 payload, since it's already merged.

Comment 11 Tomas Hofman 2017-10-09 07:49:48 UTC

Upstream issue: https://issues.jboss.org/browse/JBEAP-13421

Comment 12 Jiří Bílek 2017-11-03 09:35:13 UTC

I am not able to reproduce the issue.

Regression tests are OK, function test passes.
Verified with EAP 6.4.18.CP.CR1

Comment 13 Petr Penicka 2017-12-06 18:28:59 UTC

Released on Nov 14 2017 as part of EAP 6.4.18.