Bug 924755
| Summary: | Failed to deliver OOB message: java.lang.IllegalStateException: channel is not connected | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ladislav Thon <lthon> |
| Component: | Clustering | Assignee: | Paul Ferraro <paul.ferraro> |
| Status: | CLOSED DEFERRED | QA Contact: | Jitka Kozana <jkudrnac> |
| Severity: | high | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | bmaxwell, cdewolf, jkudrnac, lcosti, mbabacek, myarboro, paul.ferraro, rhatlapa, rhusar |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | TBD EAP 7 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause: ??
Consequence:
Workaround (if any):
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-19 11:09:53 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: | |||
|
Description
Ladislav Thon
2013-03-22 12:55:54 UTC
Unfortunately this is an Infinispan issue https://issues.jboss.org/browse/ISPN-2960 Update from EAP 6.1.0.ER8 testing cycle: This issue was not seen during this cycle. This can mean that it was either fixed unintentionally (maybe as a by-product of the Infinispan upgrade to 5.2.6.Final) or this issue just became rarer. Either way, we decided not to close this issue. Still seeing this with EAP 6.1.1.ER7. For example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbservlet-undeploy-repl-sync/32/ ISPN-2752 is still unresolved. As expected based on comment #4, this issue is still with us in EAP 6.2.0.CR3: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-http-session-shutdown-dist-async/67/artifact/report/config/jboss-perf19/server.log Graceful shutdown is not support in the affected version of EAP 6. The described behavior is to be expected. The RFE to implement graceful shutdown is https://issues.jboss.org/browse/EAP6-7 Issues relating to HTTP can be avoided using mod_cluster and session draining prior to shutdown/undeploy. Can I safely believe that these exceptions in EAP 6.3 DR2 are actually of the same nature? Three nodes, clustered webapp, restarting nodes. Nothing rapid, no load, nothing extraordinary. standalone-ha profile.
{noformat}
INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-10) ISPN000082: Stopping the RpcDispatcher
ERROR [org.jgroups.protocols.pbcast.NAKACK] (OOB-14,shared=udp) failed to deliver OOB message [dst: <null>, src: jboss-eap-6.3-3/web (4 headers), size=45 bytes, flags=OOB|DONT_BUNDLE|RSVP, transient_flags=OOB_DELIVERED]: java.lang.IllegalStateException: channel is not connected
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:617)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:544)
at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391)
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600)
at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130)
at org.jgroups.JChannel.up(JChannel.java:707)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1025)
at org.jgroups.protocols.RSVP.up(RSVP.java:172)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:181)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:400)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:896)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:245)
at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:453)
at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:751)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:609)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
at org.jgroups.protocols.FD.up(FD.java:253)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288)
at org.jgroups.protocols.MERGE3.up(MERGE3.java:290)
at org.jgroups.protocols.Discovery.up(Discovery.java:359)
at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2607)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1260)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1822)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1795)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
{noformat}
The node shows such an exception quite often when it " ISPN000094: Received new cluster view" closely prior to shutdown (via CLI).
This bug pertains to clean shutdown which is not scheduled to be implemented in EAP 6.x - and is targeted to be addressed in 7.0. Setting resolution to WONTFIX. Dear Paul, could you create an EAP 7 RFE JIRA for this issue so as it won't slip through the cracks? Thanks. Jason Greene <jason.greene> updated the status of jira EAP7-86 to Resolved Radim Hatlapatka <rhatlapa> updated the status of jira EAP7-86 to Reopened Jason Greene <jason.greene> updated the status of jira EAP7-86 to Resolved Radim Hatlapatka <rhatlapa> updated the status of jira EAP7-86 to Reopened Jason Greene <jason.greene> updated the status of jira EAP7-86 to Resolved |