[jboss-jira] [JBoss JIRA] (WFLY-3784) JMX remoting-connector dependency error

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse resolved WFLY-3784.
------------------------------------
    Fix Version/s: 9.0.0.Beta1
       Resolution: Rejected


Jira is for the management and scheduling of bugs and features, for assistance with your configuration please use the community forums.

If you are unfamiliar with the best place for different tasks I recommend starting at http://wildfly.org/

> JMX remoting-connector dependency error
> ---------------------------------------
>
>                 Key: WFLY-3784
>                 URL: https://issues.jboss.org/browse/WFLY-3784
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.1.0.Final
>            Reporter: Rakesh Panati
>            Assignee: Darran Lofthouse
>             Fix For: 9.0.0.Beta1
>
>
> My WildFly 8.1 configuration contains the below subsystem profile.
> <server xmlns="urn:jboss:domain:2.1">
>     <extensions>
> ....
>         <extension module="org.jboss.as.remoting"/>
> ....
>     </extensions>
> ...........
>     <profile>
>         <subsystem xmlns="urn:jboss:domain:jmx:1.3">
>             <expose-resolved-model/>
>             <expose-expression-model/>
>             <remoting-connector/>
>         </subsystem>
>         <subsystem xmlns="urn:jboss:domain:remoting:2.0">
>             <endpoint worker="default"/>
>             <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
>         </subsystem>
>     </profile>
>     <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
>         <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:9993}"/>
>         <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
>         <socket-binding name="http" port="${jboss.http.port:8080}"/>
>         <socket-binding name="https" port="${jboss.https.port:8443}"/>
>         <socket-binding name="txn-recovery-environment" port="4712"/>
>         <socket-binding name="txn-status-manager" port="4713"/>
>         <outbound-socket-binding name="mail-smtp">
>             <remote-destination host="localhost" port="25"/>
>         </outbound-socket-binding>
>     </socket-binding-group>
> </server>
> During startup, the JMX addition fails with the below error
> 2014-08-27 14:34:06,301 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: 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]"]}
> 2014-08-27 14:34:06,329 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jboss.remoting.endpoint.management (missing) dependents: [service jboss.jmx.remoting-connector-ref] 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)