Bug 900392 (JBPAPP6-1408)
| Summary: | Singleton Service could fail with "IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results" | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Radoslav Husar <rhusar> |
| Component: | Clustering | Assignee: | Radoslav Husar <rhusar> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | atangrin, brian.stansberry, jkudrnac, msadhukh, rdickens, rhusar, rsvoboda, smcgowan, tomaz.cerar |
| Target Milestone: | ER1 | ||
| Target Release: | EAP 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1408 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The `SingletonService` sometimes failed with the following output in the log:
----
IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results
----
The error occurred in the `getValueRef` method and was triggered when a view change occurred because the old master node was stopping and the new one was still starting. To resolve this, `getValueRef` has been changed to retry if no results are returned. The `SingletonService` now performs as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-08 14:35:29 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: | 900317, 900553, 900611 | ||
|
Description
Radoslav Husar
2012-05-09 13:37:58 UTC
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. |