Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1914

Application client container doesn't start

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Beta1
    • 8.0.0.Alpha4
    • Application Client
    • None

      Application client container fails to start with the following exception:

      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)
      

      when started using the following command:

      JBOSS_HOME/bin/appclient.sh /foo/bar/some.jar
      

              jaikiran Jaikiran Pai (Inactive)
              jaikiran Jaikiran Pai (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: