Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11145

multicastPrefix and anycastPrefix cannot be set

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 15.0.0.Beta1, 15.0.0.Final
    • 14.0.0.Final
    • JMS
    • None

    Description

      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"})

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2127 Message sent to JMSReplyTo from old client does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11143 Message sent to JMSReplyTo from old client does not find correct binding

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: