Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6150

Cannot deploy ejb-multi-server QS

    XMLWordPrintable

Details

    Description

      After successful configuration and build, the QS cannot be deployed using deploy-domain.cli script. It ends with:

      The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): WFLYDC0022: Operation failed or was rolled back on all servers.

      Errors logged in server log:

      [Server:app-twoB] 09:43:23,441 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 59) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-two.ear" was rolled back with no failure message
[Server:app-main] 09:43:23,441 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 68) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-main.ear" was rolled back with no failure message
[Server:app-twoA] 09:43:23,439 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 59) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-two.ear" was rolled back with no failure message

      This worked fine in ER3. JBEAP-2831 blocked testing in ER4.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-3292 Cannot deploy ejb-multi-server QS

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          clones

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-3292 Cannot deploy ejb-multi-server QS

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

                pferraro@redhat.com Paul Ferraro
                sgilda_jira Sande Gilda (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: