Hi, We are trying to do an Appian upgrade from 7.7 to 16.1, we have followe

Hi,
We are trying to do an Appian upgrade from 7.7 to 16.1, we have followed all of the procedures in the manual, and we even did some extra steps mentioned here and there on other forums for general jboss issues, but nothing is working. We get the following error block which i'll paste here to allow this post to help others who face the same thing in the future. Attached are all of the configuration files and server.log, your help is highly appreciated.

15:31:41,432 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "suite.ear")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\\"suite.ear\\".\\"jms-transient-topic-handler.jar\\".component.JmsTransientTopicHandlerBean.CREATE is missing [jboss.ra.hornetq-ra]",
"jboss.naming.context.java.comp.suite.jms-transient-topic-...

ConfigurationFiles16.1.rar

OriginalPostID-201548

OriginalPostID-201548

  Discussion posts and replies are publicly visible

  • ...handler.JmsTransientTopicHandlerBean.env.jms.TransientTopic is missing [jboss.naming.context.java.jms.AppianTransientTopic]",
    "jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]",
    "jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]",
    "jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]",
    "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.jms-process-inte...
  • ...gration-handler.JmsProcessIntegrationHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]",
    "jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]",
    "jboss.deployment.subunit.\\"suite.ear\\".\\"email-handler.jar\\".INSTALL is missing [jboss.deployment.subunit.\\"suite.ear\\".\\"jms-process-integration-handler.jar\\".deploymentCompleteService]",
    "jboss.deployment.unit.\\"suite.ear\\".deploymentCompleteService is missing [jboss.deployment.subunit.\\"suite.ear\\".\\"unattended-request-handler.jar\\".deploymentCompleteService, jboss.deployment.subunit.\\"suite.ear\\".\\"jms-process-integration-handler.jar\\".deploymentCompleteService, jboss.deployment.subunit.\\"suite.ear\\".\\"email-handler.jar\\".deploymentCompleteService, jboss.deploym...
  • ... ent.subunit.\\"suite.ear\\".\\"web.war\\".deploymentCompleteService]",
    "jboss.naming.context.java.comp.suite.jms-transient-topic-handler.JmsTransientTopicHandlerBean.env.jms.InternalConnectionFactory is missing [jboss.naming.context.java.ClusteredConnectionFactory]",
    "jboss.deployment.subunit.\\"suite.ear\\".\\"unattended-request-handler.jar\\".INSTALL is missing [jboss.deployment.subunit.\\"suite.ear\\".\\"web.war\\".deploymentCompleteService]",
    "jboss.deployment.subunit.\\"suite.ear\\".\\"jms-process-integration-handler.jar\\".INSTALL is missing [jboss.deployment.subunit.\\"suite.ear\\".\\"unattended-request-handler.jar\\".deploymentCompleteService]"
  • Can you uncomment the <security-domain name="messaging"> section and test?
  • Nothing changes, i still get the exact same error block above.
  • ¿Please could you tell if this problem was solved an how? Thanks.

    I have a similar error with version 16.3 and 17.1 on a clean installation on localhost development environment.
  • Not really. We abandoned that upgrade. But i would suggest manually starting the search server before starting jboss as we noticed that this does sometimes work. Make sure u rename the .failed deployment files to .dodeploy after each new attempt of starting jboss. Good luck