-
Documentation
-
Resolution: Done
-
Major
-
7.1.0.GA
-
Documentation (Ref Guide, User Guide, etc.)
-
-
In Red Hat JBoss EAP 7.1: CONFIGURING MESSAGING: 31.3. Using JBoss AMQ for Remote JMS Communication, the extra info needs to be documented to avoid ENTMQBR-962.
This is a comment from ENTMQBR-962
The EAP 7.1 resource adapter uses the 1.5.5 Artemis client. The client requires prefixing on an the address and expects the queue name to be the same as the address name.
try setting the non jms.queue. and jms.topic. addresses/queue name and enable the anycastPrefix and multicastPrefix paramters on the acceptor.
<acceptors> <acceptor name="netty-acceptor">tcp://localhost:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor> </acceptors>
- is cloned by
-
JBEAP-14344 [EO12] Using Same Address/Queue Name And Adding Prefix Setting Are Required To Use RA For AMQ
- Closed
- relates to
-
ENTMQBR-962 Message Lost in Clustered A-MQ7 Brokers When Message Is Sent From EAP Resource Adapter
- Closed