[jboss-jira] [JBoss JIRA] (WFLY-5394) Netty acceptor is ignored in configuration and not opened

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13111743#comment-13111743 ] 

Jeff Mesnil commented on WFLY-5394:
-----------------------------------

This is not blocker. The right way to configure a Netty acceptor is to use a remote-acceptor.

We are moving away from having class names in our configuration. Unless there is a compelling reason to use a generic acceptor, we should be avoided.

Having look at the attached configuration, I don't see the definition of the messaging socket-binding? Was it omitted on purpose?

> Netty acceptor is ignored in configuration and not opened 
> ----------------------------------------------------------
>
>                 Key: WFLY-5394
>                 URL: https://issues.jboss.org/browse/WFLY-5394
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.CR1
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>            Priority: Minor
>
> If netty acceptor is configured then port is not opened:
> {code}
> <acceptor name="netty" factory-class="org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory" socket-binding="messaging"/>
> {code}
> after server is started. Setting higher priority because it's core functionality.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)