Failed to deploy in Domain mode, the only error is 'JBAS015871: Deploy of deployment "x.ear" was rolled back with no failure message'

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 7.x
    • 6.x

Issue

  • In EAP 6 Domain mode(one master and three hosts), when deploying an .ear to hosts, the only error printed in Domain's console is

    JBAS015871: Deploy of deployment "x.ear" was rolled back with no failure message
    

    But it can be deployed in Standalone mode.

  • We are tying to deploy the application on our production environment (which is to go live) but it is failing with out any clue, only JBAS015871 is printed out in the server.log. Same deployment can succeed in some other hosts belonging to another profile.

In EAP 7 domain mode:

ERROR [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0021: Deploy of deployment "x.ear" was rolled back with the following failure message: undefined

Resolution

  • In Domain mode, only start one server which belong to the problematic server-group and deploy .ear to it to find if it works or not.
  • Do the same action to the rest servers one by one, you will find the root cause in each server's log.
  • When you resolved all of the errors in each server, you will successfully deploy the .ear in Damion mode.

Root Cause

In this case, it is caused by missing configured database driver on hosts.
As customer's domain is using module jdbc driver, but he didn't install the driver on other hosts.
When staring hosts, they will throw below errors:

JBAS014612: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "sqlserverdriver")
]) - failure description: "JBAS010441: Failed to load module for driver [com.sqlserverdatabase.sqlserver]"
...
New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.sqlserverdriver (missing) dependents: [service jboss.data-source.java:

And when deploying in Domain, if one server failed to deploy package for some reasons, th whole deployment will be rollback.

So this issue caused a chain reaction.

Diagnostic Steps

  • Try to deploy the problematic .ear on standalone mode, if it works which means the .ear is a good one.
  • Starting domain, keep only one server which unable to deploy .ear running and shutdown other servers, and then deploy .ear on it.
  • You will find more useful error message on this server's log and find way to resolve its issues.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.