3 Replies Latest reply on Jan 13, 2016 3:23 AM by thomash

JBAS015018 and automatic addition of .undeploy files

jessholle Nov 20, 2014 9:15 AM

We are sometimes seeing:

2014-11-19 16:05:41,145 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015018: Deployment XXX.ear was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file /pathToEar/XXX.ear.undeployed is being added to record this fact.

where XXX.ear is an exploded ear directory. This was deployed via an explicit XXX.ear.dodeploy file -- auto-deploy-exploded is set to "false".

What does this message mean? Precisely how does the scanner believe that this ear "has been removed from the server deployment list by another management tool"? We're not aware of any use of any management tool whatsoever here.

I've found lots of questions about this by googling -- and have yet to find a single answer.

1. Re: JBAS015018 and automatic addition of .undeploy files

thomash Jan 5, 2016 9:48 AM (in response to jessholle)

Any update on this? I seem to have the same issue with wildfly 9.0.2. After a restart of the server, all packages (ear and war) have a .undeployed marker file.
Actions
2. Re: JBAS015018 and automatic addition of .undeploy files

jaikiran Jan 13, 2016 3:04 AM (in response to thomash)

Is there an application which you can attach to reproduce this?

I however, suspect it's more to do with your setup rather than the application. Can you provide more details about what operating system you are using, the Java vendor and version, how you deploy the application etc?
Actions

3. Re: JBAS015018 and automatic addition of .undeploy files

thomash Jan 13, 2016 3:23 AM (in response to jaikiran)

I notice this problem in an automated test-setup, where now and then, a wildfly-server (not the complete PC, just the 9.0.2 server) is restarted. This is part of the test.

It is a setup with multiple wildfly-servers, using a distributed cache (infinispan+ jgroups). The test checks basically if the cache is distributed correctly and the applications is up to date.

Most of the times everything is fine. But every 100-150 restarts (I don't have exact statistics), the application doesn't start. At that time, all packages (a couple of ear and war files) have a .undeployed marker.

The OS is windows 7.

The logs (of startup) contains the following:

jan:06,08:54:06,055 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment bms.war was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\bms.war.undeployed is being added to record this fact.
jan:06,08:54:06,055 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment com.x.bms.server.ear was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\com.x.bms.server.ear.undeployed is being added to record this fact.
jan:06,08:54:06,071 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment com.x.bms.server.test.ear was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\com.x.bms.server.test.ear.undeployed is being added to record this fact.
jan:06,08:54:06,071 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment com.x.compose.distributed.state.ear was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\com.x.compose.distributed.state.ear.undeployed is being added to record this fact.
jan:06,08:54:06,086 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment com.x.compose.sdk.war was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\com.x.compose.sdk.war.undeployed is being added to record this fact.
jan:06,08:54:06,086 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment com.x.webservice.installation.ear was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\com.x.webservice.installation.ear.undeployed is being added to record this fact.
jan:06,08:54:06,086 INFO  (:DeploymentScanner-threads - 2:) [org.jboss.as.server.deployment.scanner] WFLYDS0019: Deployment content.war was previously deployed by this scanner but has been removed from the server deployment list by another management tool. Marker file C:\ProgramData\x\x\JBoss7\standalone\deployments\content.war.undeployed is being added to record this fact.
jan:06,08:54:06,102 INFO  (:MSC service thread 1-3:) [org.jboss.as.connector.subsystems.datasources] WFLYJCA0010: Unbound data source [java:jboss/datasources/H2-bms-DS]
jan:06,08:54:06,133 INFO  (:ServerService Thread Pool -- 99:) [org.wildfly.extension.undertow] WFLYUT0022: Unregistered web context: /x-webservice
jan:06,08:54:06,149 INFO  (:ServerService Thread Pool -- 103:) [com.x.bms.blm.BLMLicenseService] Successfully stopped BLM service.
jan:06,08:54:06,149 INFO  (:ServerService Thread Pool -- 110:) [org.wildfly.extension.undertow] WFLYUT0022: Unregistered web context: /com.x.compose.sdk
jan:06,08:54:06,149 INFO  (:ServerService Thread Pool -- 103:) [org.wildfly.extension.undertow] WFLYUT0022: Unregistered web context: /bms
jan:06,08:54:06,164 INFO  (:ServerService Thread Pool -- 120:) [org.wildfly.extension.undertow] WFLYUT0022: Unregistered web context: /content

Go to original post