• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 10 subscribers
  • Views 5238 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Unable to start JBoss Engine in 17.3 with Hotfix B

xingc

When I start the jboss engine , the first Error I get is ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "com.mysql.jdbc")
]) - failure description: "JBAS010441: Failed to load module for driver [com.mysql.jdbc]"

  Discussion posts and replies are publicly visible

Parents
  • 0
    A Score Level 2
    The main issue here is the lines shown below:

    2:30:23,718 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "appian-mysql-ds.xml" (runtime-name: "appian-mysql-ds.xml")
    22:30:23,721 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "suite.ear" (runtime-name: "suite.ear")
    22:30:23,747 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
    JBAS014775: New missing/unsatisfied dependencies:
    service jboss.data-source.reference-factory.jdbc/AppianDS (missing) dependents: [service jboss.naming.context.java.jdbc.AppianDS]
    service jboss.deployment.subunit."suite.ear"."email-poller.rar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService]




    This means that appian-ds.xml in jboss-eap-6.4/standalone/deployments folder was not able to be deployed....there can be two reasons as to why this wasn't able to be deployed:

    1. appian-ds.xml.dodeploy must exist in that folder replacing any files such as appian-ds.xml.failed or appian-ds.xml.isdeploying or appian-ds.xml.deployed.

    2. Jboss wasn't able to communicate with jdbc/AppianDS.....make sure servername, username, password are correct and the jndi name listed here matches with standalone.xml under security-domains for the primary and secondary databases. Also it has to match with custom.properties with the listing under data sources section for jdbc/AppianPrimaryDS, jdbc/AppianBusinessDS if you called it like that....
Reply
  • 0
    A Score Level 2
    The main issue here is the lines shown below:

    2:30:23,718 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "appian-mysql-ds.xml" (runtime-name: "appian-mysql-ds.xml")
    22:30:23,721 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "suite.ear" (runtime-name: "suite.ear")
    22:30:23,747 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
    JBAS014775: New missing/unsatisfied dependencies:
    service jboss.data-source.reference-factory.jdbc/AppianDS (missing) dependents: [service jboss.naming.context.java.jdbc.AppianDS]
    service jboss.deployment.subunit."suite.ear"."email-poller.rar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService]




    This means that appian-ds.xml in jboss-eap-6.4/standalone/deployments folder was not able to be deployed....there can be two reasons as to why this wasn't able to be deployed:

    1. appian-ds.xml.dodeploy must exist in that folder replacing any files such as appian-ds.xml.failed or appian-ds.xml.isdeploying or appian-ds.xml.deployed.

    2. Jboss wasn't able to communicate with jdbc/AppianDS.....make sure servername, username, password are correct and the jndi name listed here matches with standalone.xml under security-domains for the primary and secondary databases. Also it has to match with custom.properties with the listing under data sources section for jdbc/AppianPrimaryDS, jdbc/AppianBusinessDS if you called it like that....
Children
No Data

© 2024 Appian. All rights reserved.