Clever Geek Handbook

Failed to deploy WildFly - "JBAS014771: Services with missing / unavailable dependencies"

I am new to web services. I have taken over some development projects from another developer. Everything worked fine until I created my own test project to see how everything fits together. When I go back from my testing project to my previous working project, the project compiles but does not run during deployment. I don't even know where to start looking.

I am using Eclipse Kepler and I am deploying WildFly server.

The logs display the following error message:

10:39:06,146 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "JEM-eap.ear")]) - failure description: {
    "JBAS014771: Services with missing/unavailable dependencies" => [
        "jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ui.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ui.war\".beanmanager]",
        "jboss.deployment.unit.\"JEM-eap.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"JEM-eap.ear\".beanmanager]"
    ],
    "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ejb.jar\".POST_MODULE",
            "jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ui.war\".INSTALL",
            "jboss.deployment.unit.\"JEM-eap.ear\".INSTALL",
            "jboss.persistenceunit.\"JEM-eap.ear/JEM-ejb.jar#JPA-ejb\".__FIRST_PHASE__"
        ],
        "Services that may be the cause:" => [
            "jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ui.war\".beanmanager",
            "jboss.deployment.unit.\"JEM-eap.ear\".beanmanager",
            "jboss.jdbc-driver.sqljdbc4_jar"
        ]
    }
}

10:39:06,146 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "JascoEnergy")
]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
    "jboss.driver-demander.java:/jdbc/JascoEnergy is missing [jboss.jdbc-driver.sqljdbc4_jar]",
    "jboss.data-source.java:/jdbc/JascoEnergy is missing [jboss.jdbc-driver.sqljdbc4_jar]"
]}
10:39:06,146 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "JascoEnergy")
]) - failure description: {
    "JBAS014771: Services with missing/unavailable dependencies" => [
        "jboss.driver-demander.java:/jdbc/JascoEnergy is missing [jboss.jdbc-driver.sqljdbc4_jar]",
        "jboss.data-source.java:/jdbc/JascoEnergy is missing [jboss.jdbc-driver.sqljdbc4_jar]"
    ],
    "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.data-source.reference-factory.JascoEnergy",
            "jboss.naming.context.java.jdbc.JascoEnergy"
        ],
        "Services that may be the cause:" => [
            "jboss.deployment.subunit.\"JEM-eap.ear\".\"JEM-ui.war\".beanmanager",
            "jboss.deployment.unit.\"JEM-eap.ear\".beanmanager",
            "jboss.jdbc-driver.sqljdbc4_jar"
        ]
    }
}
+3


source to share


1 answer


I solved my problem which is very similar to your problem.

The error log does indeed tell you where to look, it actually says your jdbc driver is missing. The sqljdbc4.jar file is missing from the WildFly server deployment folder. You need to add jar file to <your_wildfly_server_folder> --> standalone --> deployments

. After adding the missing jar file, the deployment works well for me.



I realized that (at least in my case) something went wrong with the garbage collector on the WildFly server on one of my deployment attempts. This will result in the required jar file (sqljdbc4.jar in your case) not being deployed to the server. Since this is a dependency for your own application, deploying the application will not work.

If you see the jar file present in the deployment folder and you still cannot deploy your application, you need to flip the jar file first. You can probably do this from the WildFly Admin Console, but I'm not sure exactly how. You can also do this by going to the deployment folder, find a file named exactly the same as your missing jar file, but with a .undeployed extension (in your case sqljdbc4.jar.undeployed) and just delete it. If all goes well, WildFly will automatically redeploy your jar file.

+4


source






More articles:


All Articles