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

[Miroslav Novak (JIRA)]

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

Miroslav Novak commented on WFLY-5394:
--------------------------------------

Ok, I'll use remote-acceptor instead. I agree that using class names in configuration is not best way to configure acceptor and should be used just in cases when normal netty acceptor cannot be configured.

I've attached config where I did some tries and removed messaging socket binding. It was attached by accident. Socket binding must be configured.

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