EAR file gets undeployed unexpectedly in wildfly-16

262 views
Skip to first unread message

Dora Tuttagunta

unread,
Jun 20, 2023, 1:22:35 PM6/20/23
to WildFly
Hi,

I am using Wildfly-16 and deploying an ear file. After start and running the server for an hour or so successfully,  the ear file is getting undeployed. Below is the log. Please suggest on what could be the reason and how can i fix this.

07:01:11,679 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 133) WFLYUT0022: Unregistered web context: '/mockservice' from server 'default-server'
07:01:12,151 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 177) WFLYUT0022: Unregistered web context: '/api' from server 'default-server'
07:01:12,151 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 175) WFLYUT0022: Unregistered web context: '/wu' from server 'default-server'
07:01:12,151 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 171) WFLYUT0022: Unregistered web context: '/cc' from server 'default-server'
07:01:12,259 INFO  [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."cc.ear"."cc.war"."com.qfund.wl.jaxwswebservices.leadservice.implementation.LeadServiceImplementation"
07:01:13,151 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: cc.war) in 1863ms
07:01:13,151 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: cc_stateless.jar) in 1863ms
07:01:13,151 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: wu.war) in 1863ms
07:01:13,151 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: api.war) in 1863ms
07:01:13,167 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: mockservice.war) in 1879ms
07:01:13,210 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment cc.ear (runtime-name: cc.ear) in 1922ms
07:01:13,241 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "cc.ear" (runtime-name: "cc.ear")
07:01:18,243 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found cc.ear in deployment directory. To trigger deployment create a file called cc.ear.dodeploy




Regards,
Dora.

Bartosz Baranowski

unread,
Jun 28, 2023, 7:51:02 AM6/28/23
to WildFly
WFLY is community project, so you will only get some sort of support for latest version. Id suggest updating to current release. If its reproducible, post tad more of log, possibly with more verbose level. As its hard to say, since all this log indicates is purge of allocated resources.

Fred Welland

unread,
Jun 29, 2023, 2:20:38 AM6/29/23
to WildFly
Maybe this is helpful.     Experienced unexplainable undeploys too,  using Bootable WF  2x variant.  

Deployment scanner is a transitive dep for a web layer needed during assembly; turns out that can be excluded.  

At any rate at runtime was using defaults; so BWF would unwind itself in /tmp.

Operationally our standard Linux image had a /tmp cleaner...so it dutifully cleaned causing  deploy scanner  to detect the removed deployment  and..well...

Few ways to resolve that; set install dir somewhere else...exclude deploy scanner (still probably dont want to use /tmp)..doing a hollow bwf and point to deployment (not in /tmp) ....

Hth

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/6fec39a0-2c0e-4fdf-ab9d-5fabf76eb4bbn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages