4 Replies Latest reply on Nov 27, 2015 8:21 AM by Andrew Marlow

    WFLYCTL0184: Why does this error give no info on why the missing dependencies are missing?

    Andrew Marlow Newbie

      I have been grappling with the wildfly error WFLYCTL0184 for several days now. I am using wildfly 9.0.2.final on linux redhat enterprise 5. I am running it standalone with a couple of proprietary wars (hence I cannot disclose info about them or my precise config). I am getting this error in standalone/log/server.log:

       

      12:37:30,177 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

          ("subsystem" => "remoting"),

          ("connector" => "remoting-connector")

      ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.remoting-connector is missing [jboss.binding.remoting]"]}

       

      It is the only error message I get. Other than that the server.log is completely clean. The boot.log is empty. Not a lot of clues to go on, I know.

      The provider URL I use is http-remoting://localhost:8180. Note that since switching from JBoss to wildfly I do everything through the http port. No more using 4777. I use 8180 instead of 8080 because the old JBoss setup is still running on the machine and that uses port 8080.

      I have looked at every jar under modules/system/layers/base/org/jboss and cannot find any class with remoting in the path that starts with jboss.

      I was able to find META-INF/maven/org.jboss.remoting/jboss-remoting in modules/system/layers/base/org/jboss/remoting/main/jboss-remoting-4.0.9.Final.jar. This the closest I could get. There is no class there though, just a pom and property file.

      I really want to see a future version of wildfly in which this particular error report is preceded by information that says WHY it failed to find the dependencies. If only there was some way to crank of the verbosity level so you could where it was searching and which component or thing initiaised the search. Or maybe someone can make some suggestions as to what the cause of this error might be.

       

      Regards,

       

      Andrew Marlow