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

Bug 1348931

Summary:	[GSS](6.4.z) When message expires while being moved on the cluster bridge does not follow the address setting configuration.
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	shailendra kumar singh <shsingh>
Component:	HornetQ	Assignee:	Miroslav Sochurek <msochure>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	bmaxwell, csuconic, jtruhlar, msochure, msvehla, pmackay, tom.ross
Target Milestone:	CR1
Target Release:	EAP 6.4.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 13:08:47 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:	1348328, 1361648

Description shailendra kumar singh 2016-06-22 10:46:16 UTC

Description of problem:
When message expires while being moved on the cluster bridge does not follow the address setting configuration.


Messages which got expired in the temporary queue of cluster, are moved to the default expiry queue instead of expiry-address configured in the subsystem. 

Sample message:-
~~~~
ClientMessage[messageID=10445, durable=true, address=jms.queue.ExpiryQueue,userID=be530d61-3484-11e6-b189-c300b888c027,properties=TypedProperties[_HQ_ORIG_ADDRESS=jms.queue.test,_HQ_ORIG_QUEUE=sf.my-cluster.199f4d38-347f-11e6-95bb-895615949f9b,_HQ_ORIG_MESSAGE_ID=10427,__HQ_CID=aeaf9a6a-3484-11e6-b189-c300b888c027,_HQ_ACTUAL_EXPIRY=1466165541586]]
~~~~


_HQ_ORIG_QUEUE is a temporary queue and _HQ_ORIG_ADDRESS has the actual queue name.


Additional info:
It seems that during expiry, broker is considering _HQ_ORIG_QUEUE and ignoring _HQ_ORIG_ADDRESS due to which expired messages are found in different queue and not as per the address-settings defined in the configuration files.

Comment 8 Vlado Pakan 2016-08-18 13:56:56 UTC

PR: https://github.com/hornetq/hornetq/pull/2100
No upstream PR since HornetQ was replaced with Artemis on upstream

Comment 9 Clebert Suconic 2016-09-14 22:06:00 UTC

Actually.. it's wrong.. this needs to go upstream on Artemis.

Comment 13 Peter Mackay 2016-10-06 09:53:36 UTC

Verified with EAP 6.4.11.CP.CR1

Comment 15 Petr Penicka 2017-01-17 13:08:47 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.