Java Broker does not attempt to process any outstanding frames when Mina
reports an exception
---------------------------------------------------------------------------------------------
Key: QPID-2138
URL: https://issues.apache.org/jira/browse/QPID-2138
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: M4, M3, M2.1, 0.5
Reporter: Martin Ritchie
Attachments:
TEST-org.apache.qpid.server.failover.MessageDisappearWithIOExceptionTest.test.out
When an exception is caught in Mina it is notified via exceptionCaught().
When an IOException is fired the Java broker simply logs the event and carries
on.
The MessageDisappearWithIOExceptionTest highlights this problem as frequently
an ack is sent to the broker just before failover is initiated. The Java client
closes the connection which prevents the ack being received on the broker as
the IOException occurs first.
As there is no sign in the logs of the Ack being received it suggests that Mina
stops sending messages for the IOSession after the exception occurs. It doesn't
seem write that we have flushed our socket then closed it and the broker does
not receive the data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
