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

Generic acceptor/connector is ignoring its socket-binding

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 10.0.0.CR2
    • 10.0.0.CR1
    • JMS
    • None

    Description

      If netty acceptor is configured then port is not opened:

      <acceptor name="netty" factory-class="org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory" socket-binding="messaging"/>

      after server is started. Setting higher priority because it's core functionality.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1137 Netty acceptor is ignored in configuration and not opened

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5970 Plain JMS clients don't fallback

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: