[jboss-jira] [JBoss JIRA] (WFCORE-4979) WFLYSRV0137: No deployment content with hash

[Brian Stansberry (Jira)]

    [ https://issues.redhat.com/browse/WFCORE-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109806#comment-14109806 ] 

Brian Stansberry commented on WFCORE-4979:
------------------------------------------

The boot failure is expected given the state of the server installation (config referencing a file that is not in the content repo.) The question is how the server installation ended up in that state.  James can comment more if this is wrong but AIUI earlier he'd been using the wildlfy maven plugin. The server.log (and I assume the standalone_xml_history) in the attached zip provides a quasi-record of what he'd been doing.

> WFLYSRV0137: No deployment content with hash
> --------------------------------------------
>
>                 Key: WFCORE-4979
>                 URL: https://issues.redhat.com/browse/WFCORE-4979
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>            Reporter: James Perkins
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> I saw the following when attempting to start a server.
> {code}
> jperkins at localhost ~/servers/wildfly-19.1.0.Final $ ./bin/standalone.sh 
> =========================================================================
>   JBoss Bootstrap Environment
>   JBOSS_HOME: /home/jperkins/servers/wildfly-19.1.0.Final
>   JAVA: java
>   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=com.yourkit,org.jboss.byteman -Djava.awt.headless=true 
> =========================================================================
> 11:43:21,055 INFO  [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final-SNAPSHOT
> 11:43:21,410 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 11:43:21,421 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 11:43:21,545 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
> 11:43:22,184 INFO  [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.11.4.Final
> 11:43:22,703 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,774 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 37) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "simple-servlet.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 7e2e9824daa6775b04ed1eb5b012c7372f69c4a6 is available in the deployment content repository for deployment 'simple-servlet.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."
> 11:43:22,823 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 11:43:22,853 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 24ms
> {code}
> The deployment is there in the model, but doesn't appear to be in the file structure.
> {code}
> [standalone at embedded /] /deployment=simple-servlet.war:read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "content" => [{
>             "hash" => bytes {
>                 0x7e, 0x2e, 0x98, 0x24, 0xda, 0xa6, 0x77, 0x5b,
>                 0x04, 0xed, 0x1e, 0xb5, 0xb0, 0x12, 0xc7, 0x37,
>                 0x2f, 0x69, 0xc4, 0xa6
>             },
>             "archive" => undefined
>         }],
>         "enabled" => true,
>         "name" => "simple-servlet.war",
>         "owner" => undefined,
>         "persistent" => true,
>         "runtime-name" => "simple-servlet.war",
>         "subdeployment" => undefined,
>         "subsystem" => undefined
>     }
> }
> {code}
> I've zipped up the server in case it helps. https://www.dropbox.com/s/an9wj3n41vr0m30/failed-deployment-wildfly-19.1.0.Final.zip?dl=0



--
This message was sent by Atlassian Jira
(v7.13.8#713008)