[jboss-jira] [JBoss JIRA] (JGRP-1958) RequestCorrelator "channel is not connected" error during shutdown

Dennis Reed (JIRA) issues at jboss.org
Tue Sep 1 17:09:05 EDT 2015


Dennis Reed created JGRP-1958:
---------------------------------

             Summary: RequestCorrelator "channel is not connected" error during shutdown
                 Key: JGRP-1958
                 URL: https://issues.jboss.org/browse/JGRP-1958
             Project: JGroups
          Issue Type: Bug
    Affects Versions: 3.2.12
            Reporter: Dennis Reed
            Assignee: Bela Ban
            Priority: Minor


Error logged during shutdown of a channel due to RequestCorrelator failing to send a reply:

ERROR [org.jgroups.protocols.UNICAST2] (OOB-17,shared=tcp) couldn't deliver OOB message [dst: server1/web, src: server2/web (4 headers), size=62 bytes, flags=OOB|DONT_BUNDLE|RSVP]: java.lang.IllegalStateException: channel is not connected
        at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:617) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1]
        at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:544) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1]
        at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1]
        at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1]
        at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1]
        [incoming JGroups message]

It appears to just be a timing issue between shutdown of the channel and RequestCorrelator processing the message, which triggers a response message.
It would be good to either avoid triggering the exception in the first place, or suppress the error log during shutdown.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list