-
Bug
-
Resolution: Done
-
Major
-
14.0.0.Final
-
None
It's not possible to configure acceptor with multicastPrefix=jms.topic. and anycastPrefix=jms.queue.".
Problem is that those 2 parameters must be set to extraProps variable in TransportConfiguration:
https://github.com/apache/activemq-artemis/blob/a6b0b7e44291a76d6732c20b9efedf2a934fd189/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/TransportConfiguration.java#L128
however in messaging integration we don't call TransportConfiguration constructor with extreProps map:
https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f7252d5dd04/messaging-activemq/src/main/java/org/wildfly/extension/messaging/activemq/TransportConfigOperationHandlers.java#L258
Ideally this CLI command should configure acceptor with anycast/multicast prefixes:
/subsystem=messaging-activemq/server=default/acceptor=acceptor:add(socket-binding=http,factory-class=org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory,params={protocols="CORE",multicastPrefix="jms.topic",anycastPrefix="jms.queue"})
- is related to
-
ENTMQBR-2127 Message sent to JMSReplyTo from old client does not find correct binding
- Closed
-
WFLY-11143 Message sent to JMSReplyTo from old client does not find correct binding
- Closed