WildFly 8.1.0 shuts down when jbpm-console should be redeployed

[Dušan Chromý]

Hi,

we run jBPM 6.2.0 Final on WildFly 8.1.0 Final. We also deploy some custom BPM-workitems (WorkItemHandlers, Commands, ProcessEventListeners etc.) as a JAR file that we copy to the unzipped jbpm-console.war deployment.

Whenever we update the workitems.jar we do:

1. replace the file in jbpm-console.war/WEB-INF/lib
2. touch standalone/deployments/jbpm-console.war.dodeploy

This used to work relatively reliably until recently when we started to experience this unexpected behavior:

1. after performing the above steps the WildFly server stops responding and there is a message about shutdown going on ("Invocation cannot proceed as component is shutting down"). I am pasting excerpt from the log below.
   
2. there is a file created jbpm-console.war.failed with this contents: "{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"jbpm-console.war\")]"}}"
   
3. the server actually never shuts down, it has to be stopped manually
   
4. a file jbpm-console.war.skipdeploy has to be created (otherwise the server will fail to start with the same error as seen in the .failed file -step 2 above)
   
5. then the server can be started manually
   
6. then .dodeploy file can be created and now the jbpm-console.war deployment starts and finishes successfully

I wonder whether there is any explanation / tip / hint how to avoid the server shutdown and restart? Below is the log file, the .dodeploy file was created shortly before 15:14:53 but I am including previous messages for the context. Any help is appreciated.

15:05:13,328 WARN  [org.hornetq.core.server] (Thread-4 (HornetQ-scheduled-threads-185852185)) HQ222103: transaction with xid XidImpl (1753889037 bq:0.0.0.0.0.0.0.0.0.0.-1.-1.127.0.0.1.70.-27.-53.-21.86.-106.100.-18.0.0.1.17.0.0.0.3.0.0.0.0 formatID:13

1077 gtxid:0.0.0.0.0.0.0.0.0.0.-1.-1.127.0.0.1.70.-27.-53.-21.86.-106.100.-18.0.0.1.14.49 base64:AAAAAAAAAAAAAP__fwAAAUbly-tWlmTuAAA

BEQAAAAMAAAAAAAAAAAAAAAAAAP__fwAAAUbly-tWlmTuAAABDjEHAgIA timed out

15:05:13,401 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0

:ffff7f000001:46e5cbeb:569664ee:10e in state  CANCEL_INTERRUPTED

15:05:13,401 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012120: TransactionReaper::check worker Thread[Tr

ansaction Reaper Worker 4,5,main] not responding to interrupt when cancelling TX 0:ffff7f000001:46e5cbeb:569664ee:10e -- worker mark

ed as zombie and TX scheduled for mark-as-rollback

15:05:13,402 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012110: TransactionReaper::check successfuly marked TX 0:ffff7f000001:46e5cbeb:569664ee:10e as rollback only

15:14:53,022 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 85) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/KIE.AUDIT

15:14:53,022 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 85) JBAS011605: Unbound messaging object to jndi name java:/queue/KIE.AUDIT.ALL

15:14:53,023 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 84) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/KIE.SESSION

15:14:53,023 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 84) JBAS011605: Unbound messaging object to jndi name java:/queue/KIE.SESSION.ALL

15:14:53,023 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 86) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/KIE.RESPONSE

15:14:53,024 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 86) JBAS011605: Unbound messaging object to jndi name java:/queue/KIE.RESPONSE.ALL

15:14:53,024 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 87) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/KIE.TASK

15:14:53,034 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 87) JBAS011605: Unbound messaging object to jndi name java:/queue/KIE.TASK.ALL

15:15:03,034 WARN  [org.jboss.modcluster] (MSC service thread 1-2) MODCLUSTER000025: Failed to drain 2 remaining active sessions from default-host:/jbpm-console within 10.0 seconds

15:15:03,038 INFO  [org.jboss.modcluster] (MSC service thread 1-2) MODCLUSTER000021: All pending requests drained from default-host:/jbpm-console in 10.0 seconds

15:15:03,040 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /jbpm-console

15:15:03,101 INFO  [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."jbpm-console.war".CommandWebService

15:15:05,743 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 6) JBAS014134: EJB Invocation failed on component AvailableJobsExecutor for method public void org.jbpm.executor.impl.AvailableJobsExecutor.executeJob(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: JBAS014559: Invocation cannot proceed as component is shutting down

[Mauricio Salatino]

It might be the case that Wildfly is redeploying the app everytime that it detects a change in the app. 

So you might need to disable the auto deploy option (look in the docs about how to do that) .. That option is usually disabled for 

production use. 

HTH

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/c7166951-5998-479f-8495-6990fea8156b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

 - MyJourney @ http://salaboy.com

 - Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -