JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./suite

Dears,

OS: Windows Server 2016

Application Server:

JBoss (6.4.19)

Appian: 18.1 With Two HotFix-Updates (A and B)

I am able to run successfully the following:

- Appian Engine (all services)

- Data Server service

- Search Server service

- JBoss started as Standalone but failed with several exception messages.

 

"{
    \"JBAS014671: Failed services\" => {\"jboss.web.deployment.default-host./suite\" => \"org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./suite: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
    Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\"},
    \"JBAS014771: Services with missing/unavailable dependencies\" => [
        \"jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]\",
        \"jboss.deployment.subunit.\\\"suite.ear\\\".\\\"email-handler.jar\\\".INSTALL is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".deploymentCompleteService]\",
        \"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]\",
        \"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]\",
        \"jboss.deployment.unit.\\\"suite.ear\\\".deploymentCompleteService is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"email-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".deploymentCompleteService]\",
        \"jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]\",
        \"jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]\",
        \"jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".INSTALL is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService]\",
        \"jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]\"
    ]
}"

  Discussion posts and replies are publicly visible

Parents Reply
  • In case we need to use/enable LDAP using Appian Admin site

    1- Is it obligatory to have First Appian user (defined in password.properties file) the same exists in LDAP
    OR
    2- we can have the different unique user (which doesn't exist in LDAP) e.g. appAdmin/password etc.??

    If we will go with 2nd option then what will happened while configuring LDAP?
    Will we have to create another user with same username/password which exist in LDAP and then enable LDAP on Appian using that user??

    OR

    can we change the First user's username and password so that it matches exactly with the user exist in LDAP and then enable LDAP on Appian?

    Please respond
Children