Bug 1367793

Summary: [GSS](6.4.z) Singleton service is not correctly being set in 6.4 CP9 but does work in 6.4 CP8
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Shay Matasaro <smatasar>
Component: ClusteringAssignee: Panagiotis Sotiropoulos <psotirop>
Status: CLOSED CURRENTRELEASE QA Contact: Michal Vinkler <mvinkler>
Severity: high Docs Contact:
Priority: high    
Version: 6.4.9CC: bmaxwell, dereed, jbilek, jtruhlar, msochure, onagano, paul.ferraro, psotirop, wfink
Target Milestone: CR1   
Target Release: EAP 6.4.11   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:10:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1361648    
Attachments:
Description Flags
reproducer none

Description Shay Matasaro 2016-08-17 13:30:49 UTC 
EAP 6.4.9 (with and without BZ1358913) doesn't call ServiceLoader (META-INF/services/org.jboss.msc.service.ServiceActivator) when it is deployed in EAR/lib. It is called on EAP 6.4.8. The SingletonService (not a singleton EJB) is activated in the ServiceLoader so the SingletonService hasn't been activated from the first. It works as expected when deployed as an EJB (not in EAR/lib).

When the ServiceLoader is called, a message of "HATimerService will be installed!" is logged and the SingletonService will be activated.

$ fgrep -e HATimerService -e '[org.jboss.as.clustering.singleton]' domain/servers/server-one/log/server.log
12:14:52,373 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator] (MSC service thread 1-7) HATimerService will be installed!
12:14:56,251 INFO  [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service
12:14:56,251 INFO  [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010340: This node will now operate as the singleton provider of the jboss.quickstart.ha.singleton.timer service
12:14:56,268 INFO  [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerService] (MSC service thread 1-8) Start HASingleton timer service 'org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATim
erService'
12:14:56,873 INFO  [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service

Attaching a reproducer "jboss-ejb-in-ear.ear" which is based on "cluster-ha-singleton" and "ejb-in-ear" quickstarts projects. EJB calls from the SingletonService are disabled to avoid exceptions.
Comment 1 Shay Matasaro 2016-08-17 13:31:47 UTC 
Created attachment 1191636 [details]
reproducer
Comment 3 Shay Matasaro 2016-08-23 20:46:38 UTC 
Is there a viable workaround for this issue ?
Comment 7 JBoss JIRA Server 2016-08-26 07:54:09 UTC 
Panagiotis Sotiropoulos <psotirop> updated the status of jira WFCORE-1730 to Closed
Comment 8 JBoss JIRA Server 2016-08-26 08:02:19 UTC 
Panagiotis Sotiropoulos <psotirop> updated the status of jira JBEAP-5746 to Closed
Comment 9 JBoss JIRA Server 2016-08-26 08:04:03 UTC 
Panagiotis Sotiropoulos <psotirop> updated the status of jira JBEAP-5745 to Closed
Comment 10 Jiří Bílek 2016-10-04 16:01:19 UTC 
Verified with EAP 6.4.11.CP.CR1
Comment 11 Petr Penicka 2017-01-17 13:10:21 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.