3 Replies Latest reply on Aug 21, 2013 7:17 AM by Aleksandar Kostadinov

    problem with appclient

    Aleksandar Kostadinov Novice



      I tried running appclient on wildfly from master branch. But I hit these error messages:

      16:23:40,742 INFO  [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016328: CORBA Naming Service started
      16:23:40,744 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
          ("subsystem" => "naming"),
          ("service" => "remote-naming")
      ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.remote is missing [jboss.remoting.endpoint.subsystem]"]}
      16:23:40,779 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
      JBAS014775:    New missing/unsatisfied dependencies:
            service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote] 
      16:23:40,782 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started (with errors) in 1471ms - Started 99 of 103 services (1 services failed or missing dependencies, 9 services are lazy, passive or on-demand)
      16:23:40,798 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "hello-0.0.1-SNAPSHOT.jar" (runtime-name: "hello-0.0.1-SNAPSHOT.jar")


      I'm starting app by first starting wildfly default standalone profile and then:

      bin/appclient.sh /path/hello-0.0.1-SNAPSHOT.jar


      The app is just what I got from maven appclient archetype project. I can attach if necessary.