Core bridge in JBoss EAP between queue (ANYCAST) and topic (MULTICAST) does not work

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.4
  • Red Hat AMQ Broker (AMQ)
    • 7.8

Issue

Messages get lost when routing messages between a queue in EAP and a topic in an external AMQ broker

Resolution

Upgrade to a version that contains the fix for This content is not included.JBEAP-22538

The workaround:
To workaround this issue it is possible to add an additional queue to the broker that can be bridged to EAP and then create a divert to divert any messages arriving on the queue to the topic (MULTICAST), for example:

<diverts>
	<divert name="queue-to-topic">
		<address>targetQueue</address>
		<forwarding-address>targetTopic</forwarding-address>
		<routing-type>STRIP</routing-type>
		<exclusive>true</exclusive>
	</divert>
</diverts>

Root Cause

When routing messages over core bridge between ANYCAST and MULTICAST destinations it is necessary to configure the bridge with routing-type as STRIP otherwise the broker will not route a message from an ANYCAST to a MULTICAST destination. Currently EAP does not offer an option of setting routing-type on a CORE bridge. This is a defect This content is not included.JBEAP-22538

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.