[
https://issues.jboss.org/browse/WFLY-6895?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-6895:
----------------------------------------
The linked PR is for the 10.x branch and it looks fine for that, so assuming it still
passes CI I'll merge it. There are no particular plans for another 10.x release
though.
For WF 11, WFCORE-1272 has fixed the problem.
TimerService problem(duplicated resource)
-----------------------------------------
Key: WFLY-6895
URL:
https://issues.jboss.org/browse/WFLY-6895
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Environment: Two standalone instances connected into a cluster.
*Master WildFly*
{code}
standalone.bat -c standalone-full-ha.xml -Djboss.node.name=master
{code}
*Slave WildFly*
{code}
standalone.bat -c standalone-full-ha.xml -Djboss.node.name=slave
-Djboss.socket.binding.port-offset=100
{code}
Both instances has the same singleton policy defined in singleton-full-ha.xml:
{code}
<singleton-policy name="scada-singleton"
cache-container="server">
<simple-election-policy>
<name-preferences>master</name-preferences>
</simple-election-policy>
</singleton-policy>
{code}
Reporter: Artur Kowalczyk
Assignee: Tomasz Adamski
Fix For: 10.2.0.Final, 11.0.0.Beta1
I found a problem with TimerService that occurs when your application is configured as a
singleton deployment.
*Test Case*
# Start master node, the app is also started - OK
# Start slave node, the app is deployed but bot stared - OK
# Stop master node, the app is started on slave - OK
# Start master node, there is a preference for node name so the app will be started again
on master and stopped in slave - OK
# Stop master node, the app should be started again on slave but an exception occur. -
ERROR
{code}
09:50:42,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001:
Failed to start service
jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."wildfly-ejb-in-ear.ear"."wildfly-ejb-in-ear-ejb.jar".INSTALL:
WFLYSRV0153: Failed to process phase INSTALL of subdeployment
"wildfly-ejb-in-ear-ejb.jar" of deployment "wildfly-ejb-in-ear.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0086:
Failed to install management resources for TimerEJB
at
org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:82)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
... 5 more
Caused by: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource timer-service
at
org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:290)
at
org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:169)
at
org.jboss.as.server.deployment.DeploymentResourceSupport.register(DeploymentResourceSupport.java:322)
at
org.jboss.as.server.deployment.DeploymentResourceSupport.registerDeploymentSubResource(DeploymentResourceSupport.java:219)
at
org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.installManagementResource(EjbManagementDeploymentUnitProcessor.java:119)
at
org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:79)
... 6 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)