Bug 927615
| Summary: | Failed to recover cluster state after the current node became the coordinator: IllegalStateException | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ladislav Thon <lthon> | ||||||
| Component: | Clustering | Assignee: | Paul Ferraro <paul.ferraro> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitka Kozana <jkudrnac> | ||||||
| Severity: | high | Docs Contact: | Russell Dickenson <rdickens> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1.1 | CC: | dereed, istudens, jkudrnac, jswensso, mbabacek, mpark, myarboro, paul.ferraro, rhusar, rjanik, smumford | ||||||
| Target Milestone: | GA | Keywords: | Reopened | ||||||
| Target Release: | EAP 6.4.4 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-12-07 13:37:30 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ladislav Thon
2013-03-26 10:44:18 UTC
And also seen in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-netDown-repl-sync/7/console-perf19/ (only the first exception, the second doesn't seem to appear anywhere). Still seeing this with EAP 6.1.0.ER8. For example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-netDown-repl-sync/11/artifact/report/config/jboss-perf21/server.log https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-netDown-repl-async/11/artifact/report/config/jboss-perf21/server.log The error 02:31:14,431 ERROR [org.jboss.as.clustering] (Incoming-12,shared=tcp) JBAS010223: ViewAccepted failed: java.lang.IllegalStateException: JBAS010240: Address ec1de289-4782-a45c-cb61-d662009b71e7 not registered in transport layer was seen during 6.1.1.ER3 testing here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbremote-shutdown-dist-sync-tcpStack/17/artifact/report/config/jboss-perf20/server.log however without the first exception (Failed to recover cluster state after the current node became the coordinator: ...). Not seen in 6.1.1. Please retest against 6.3.0.GA. I was instructed to retest against 6.3.0.DR1. Haven't seen it there so I consider it verified. 6.3.0.DR2
I've got a lovely
{noformat}
ISPN000196: Failed to recover cluster state after the current node became the coordinator: java.lang.NullPointerException
{noformat}
with a dead-simple scenario, start, deploy, undeploy, shutdown. Two nodes, <distributable/> app.
I'm attaching the log.
Created attachment 871331 [details]
6.3.0.DR2_ISPN000196_NPE
Added the upstream counterpart. I'm sorry, the extend of my attention disorder can be hardly exaggerated. I accidentally swapped logs with the previous test run :-) Comment on attachment 871331 [details] 6.3.0.DR2_ISPN000196_NPE The [attachment 871331 [details]] is invalid. Ignore it. Paul, what version was this actually fixed in? Your comment (4) seem to suggest it's been fixed since 6.1.1. Does it need a release note for 6.3.0? If so, can you please supply an outline of the situation using the prompts in the Doc Text field above. Cheers This does not need a release note since it was fixed in a previous release cycle, even though it was only verified this cycle. Tristan Tarrant <ttarrant> updated the status of jira ISPN-3395 to Resolved The original issue in this BZ was fixed as part of ISPN-2935. Created attachment 1102190 [details]
ISPN000196: Failed to recover cluster state after the current node became the coordinator: java.lang.NullPointerException
I hit the issue again with JBoss EAP 6.4.4.GA during a simple mod_cluster failover scenario on 3 nodes. I believe that what mbabacek is seeing in comment 15 is in fact bug 1283465. @LaDiSlAv, hmm, yes, it appears to be the case. When will this bug be fixed in EAP 6.3.2 GA ? The issue is tracked by bug 1283465. |