Right before the end of a JBoss startup, the following error is printed in the application server log:
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "jmx"), ("remoting-connector" => "jmx") ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.jmx.remoting-connector-ref is missing [jboss.remoting.endpoint.management]"]}
This is seen before the INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS015859: Deployed "appian-ds.xml" (runtime-name : "appian-ds.xml") line.
INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS015859: Deployed "appian-ds.xml" (runtime-name : "appian-ds.xml")
No management interfaces were configured in standalone.xml prior to starting JBoss. This is typically the result of making modifications to the out-of-the-box standalone.xml file. Making any modifications to any JBoss files that are not documented by Appian are unsupported by Appian.
<JBOSS_HOME>/standalone/configuration
<audit-log>
<management-interfaces> <native-interface security-realm="ManagementRealm"> <socket-binding native="management-native"/> </native-interface> <http-interface security-realm="ManagementRealm"> <socket-binding http="management-http"/> </http-interface> </management-interfaces>
<socket-binding-group>
<socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
This article applies to all versions of Appian using JBoss EAP as an application server.
Last Reviewed: February 2017