Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1330

Deployment error after reboot [WFLYSRV0137]

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 3.0.0.Beta29
    • 1.0.2.Final
    • Management
    • None

    Description

      I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE).

      After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred.
      But if I restart the server now, I get following error message:
      10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
      10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

      I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot.
      The only way to fix the configuration is to manually remove the deployments from the standalone.xml.
      But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day.

      Attachments

        1. server.log
          21 kB
        2. server.log
          21 kB

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5715 Wildfly 9/10 removing deployments after a certain time

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2675 Simplify and fix ContentReference management

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-1348 Specify filesystem rights for deployment content

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1108 Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-3102 Implement the LocalClient close

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          links to

          Web Link StackOverflow Discussion

          Web Link StackOverflow Discussion

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              wildflyer_jira Tobi Tobias (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: