Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.2.CR1, 7.1.2.GA
Affects Version/s: None
Component/s: ActiveMQ
Labels:
- downstream_dependency
- test_included

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.z.GA
Git Pull Request:
https://github.com/rh-messaging/jboss-activemq-artemis/pull/228

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

This is upstream issue for https://bugzilla.redhat.com/show_bug.cgi?id=1431406, related to HornetQ. It is suspected the same problem exists in Artemis.

Description of HornetQ bug:

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.

clones

JBEAP-13419 Artemis JMS bridge does not remove vendor specific properties from message headers

Closed

is cloned by

JBEAP-13421 (7.0.z) Artemis JMS bridge does not remove vendor specific properties from message headers

Closed

is incorporated by

JBEAP-14132 (7.1.z) Upgrade ActiveMQ Artemis to 1.5.5-010

Closed

is caused by: ARTEMIS-1227 Loading...

Assignee:: Dmitrii Tikhomirov

Reporter:: Tomas Hofman

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2017/10/09 3:45 AM

Updated:: 2021/10/24 6:55 AM

Resolved:: 2018/03/13 10:08 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates