Red Hat Bugzilla – Bug 900392
Singleton Service could fail with "IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results"
Last modified: 2014-06-28 08:32:40 EDT
Affects: Release Notes project_key: JBPAPP6 As seen on hudson runs and observed by Tom C. (thanks Tom) : http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK7/17/jdk=java17_default,label=Win2k8_x86/testReport/junit/org.jboss.as.test.clustering.cluster.singleton/SingletonTestCase%28UDP%29/testSingletonService/ {noformat} 07:34:17,664 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/singleton].[org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet]] (http--10.16.92.4-8080-1) Servlet.service() for servlet org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet threw exception: java.lang.IllegalStateException: java.lang.IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results. at org.jboss.as.clustering.singleton.SingletonService$RpcHandler.getValueRef(SingletonService.java:225) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.clustering.singleton.SingletonService.getValue(SingletonService.java:176) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.clustering.singleton.SingletonService.getValue(SingletonService.java:53) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1203) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet.doGet(MyServiceServlet.java:40) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67) at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.15.Final-redhat-1.jar:] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] Caused by: java.lang.IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results. at org.jboss.as.clustering.singleton.SingletonService$RpcHandler.getValueRef(SingletonService.java:221) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] ... 21 more {noformat} Test itself then fails with {noformat} Error Message Deployment with name deployment-1 could not be undeployed. Container container-1 must be still running. {noformat}
Link: Added: This issue Cloned from AS7-4751
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
Link: Added: This issue is incorporated by JBPAPP-7577
Labels: Added: eap6_need_triage
Link: Added: This issue is a dependency of JBPAPP-8860
Release Notes Docs Status: Added: Not Yet Documented
Link: Added: This issue is a dependency of JBPAPP-9290
Link: Removed: This issue is incorporated by JBPAPP-7577
Link: Added: This issue is a dependency of JBPAPP-9188
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: <para> An error like the following can be seen on Microsoft Windows: </para> <screen>IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results</screen> <para> This issue is under investigation and seems to be due to timing. The fix will be to make the <code>getValueRef</code> method retry if the new master has not yet been notified. Until this fix is in place, the workaround is to add a <code>Thread.sleep()</code> call to your code to delay the <code>getValueRef()</code> call. </para> Affects: Added: Release Notes
Labels: Removed: eap6_need_triage Added: eap601candidate
This was resolved in upstream master and 7.1 in late May; can this be resolved here?
Test is @Ignore-d again, due to AS7-5210.
Labels: Removed: eap601candidate Added: eap601-qe-triage
Not approved for EAP 6.0.1. If this should be reconsidered, please add the label: eap601-qe-triage
Labels: Removed: eap601-qe-triage
Writer: Added: mistysj
Release Notes Text: Removed: <para> An error like the following can be seen on Microsoft Windows: </para> <screen>IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results</screen> <para> This issue is under investigation and seems to be due to timing. The fix will be to make the <code>getValueRef</code> method retry if the new master has not yet been notified. Until this fix is in place, the workaround is to add a <code>Thread.sleep()</code> call to your code to delay the <code>getValueRef()</code> call. </para> Added: An error like the following can be seen on Microsoft Windows: IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results This issue is under investigation and seems to be due to timing. The fix will be to make the `getValueRef` method retry if the new master has not yet been notified. Until this fix is in place, the workaround is to add a `Thread.sleep()` call to your code to delay the `getValueRef()` call.
Release Notes Docs Status: Removed: Documented as Known Issue Writer: Removed: mistysj Release Notes Text: Removed: An error like the following can be seen on Microsoft Windows: IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results This issue is under investigation and seems to be due to timing. The fix will be to make the `getValueRef` method retry if the new master has not yet been notified. Until this fix is in place, the workaround is to add a `Thread.sleep()` call to your code to delay the `getValueRef()` call. Docs QE Status: Removed: NEW
This test passes on Windows currently with EAP 6.1.0.DR4 bits https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-61-as-testsuite-Win2k8R2_x86_64-OracleJDK6-gitrepo/21/testReport/org.jboss.as.test.clustering.cluster.singleton/SingletonTestCase%28SYNC-tcp%29/testSingletonService/ However his should be added to fixed issues for EAP 6.1.0 Docs
@rdickens, Continuing the IRC chat, the actual description and fix for the issue is here: https://issues.jboss.org/browse/AS7-4751?focusedCommentId=12693750&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12693750 I have rewritten the Doc Text with the updates. Also please note that this does not only influence Windows OS, but other OSes as well. It is just that the Windows OS exposed this issue. I have updated the fields and description of the Jira to reflect that.
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html