]
Radoslav Husar closed WFLY-8706.
--------------------------------
Resolution: Rejected
Singleton deployments does not work in domain mode
--------------------------------------------------
Key: WFLY-8706
URL:
https://issues.jboss.org/browse/WFLY-8706
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Environment: Centos
Wildfly 10.1.0.Final (two instances and one domain controller)
Java 8
Reporter: Ariel Carrera
Assignee: Paul Ferraro
In a domain mode, when a deployment is a "singleton deployment" (with a
singleton- deployment.xml descriptor), it is working fine if the server nodes are started
sequently but fails if it is started from domain console.
When a deployments needs to be updated, a race condition happens and two instances of the
deployment are started.
From logs:
node1:
12:39:48,434 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool --
133) WFLYCLINF0002: Started default cache from server container
12:39:48,436 INFO [org.wildfly.clustering.server] (notification-thread--p84-t1)
WFLYCLSV0003: node1:one *elected as the singleton provider of the
jboss.deployment.unit."my-deployment.jar"*.FIRST_MODULE_USE service
12:39:48,440 INFO [org.wildfly.clustering.server] (notification-thread--p84-t1)
WFLYCLSV0001: This node will now operate as the singleton provider of the
jboss.deployment.unit."my-deployment.jar".FIRST_MODULE_USE service
node2:
12:39:48,370 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool --
122) WFLYCLINF0002: Started default cache from server container
12:39:48,372 INFO [org.wildfly.clustering.server] (notification-thread--p193-t1)
WFLYCLSV0003: node2:two *elected as the singleton provider of the
jboss.deployment.unit."my-deployment.jar"*.FIRST_MODULE_USE service
12:39:48,372 INFO [org.wildfly.clustering.server] (notification-thread--p193-t1)
WFLYCLSV0001: This node will now operate as the singleton provider of the
jboss.deployment.unit."my-deployment.jar".FIRST_MODULE_USE service