[jboss-jira] [JBoss JIRA] (WFLY-10214) WFLYMSGAMQ0030: Failed to find SocketBinding for connector: http-connector

[Jeff Mesnil (JIRA)]

Jeff Mesnil created WFLY-10214:
----------------------------------

             Summary: WFLYMSGAMQ0030: Failed to find SocketBinding for connector: http-connector
                 Key: WFLY-10214
                 URL: https://issues.jboss.org/browse/WFLY-10214
             Project: WildFly
          Issue Type: Bug
          Components: Application Client, JMS
    Affects Versions: 12.0.0.Final
            Reporter: Jeff Mesnil
            Assignee: Stuart Douglas


When an appclient is configured with the messaging-activemq subsystem:

{code}
 <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
            <server name="default" >
		<http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor" />
		<in-vm-connector name="in-vm" server-id="1"/>
                <!-- no acceptors are defined -->
		
		<connection-factory name="RemoteConnectionFactory" connectors="http-connector" entries="RemoteConnectionFactory java:/ConnectionFactory java:jboss/DefaultJMSConnectionFactory" consumer-window-size="0" thread-pool-max-size="10"/>
            </server>
        </subsystem>
{code}


There are intermittent errors during server start up:

{code}
\u001b[0m\u001b[31m09:27:42,858 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.messaging-activemq.default: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default: WFLYMSGAMQ0033: Failed to start service
        at org.wildfly.extension.messaging.activemq.ActiveMQServerService.start(ActiveMQServerService.java:359)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) [jboss-msc-1.3.2.Final.jar:1.3.2.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) [jboss-msc-1.3.2.Final.jar:1.3.2.Final]
        at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) [jboss-msc-1.3.2.Final.jar:1.3.2.Final]
        at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
        at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
        at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0030: Failed to find SocketBinding for connector: http-connector
        at org.wildfly.extension.messaging.activemq.ActiveMQServerService.start(ActiveMQServerService.java:216)
        ... 8 more
{code}

If there are no acceptors, the connectors resource have only *optional* dependencies to the socket -binding (or outbound-socket-binding) service.
It happens that from time to time, the messaging-activemq subsystem performs its runtime before the socket binding service is started.

The dependency to the socket binding must be required for connectors resources (though for historical reasons, it can depend on either a socket-binding or an outbound-socket-binding)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)