[ https://issues.apache.org/activemq/browse/AMQ-995?page=all ]
james strachan resolved AMQ-995.
--------------------------------
Fix Version/s: 4.1
Resolution: Fixed
Patch applied Rob - thanks again! :)
> An unhandled exception in the TcpTransports' reader thread should close the
> connection (and inform the app)
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMQ-995
> URL: https://issues.apache.org/activemq/browse/AMQ-995
> Project: ActiveMQ
> Issue Type: Bug
> Components: NMS (C# client)
> Affects Versions: 4.0.2
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: james strachan
> Fix For: 4.1
>
> Attachments: amq995-patch.txt, AtomicBoolean.cs
>
>
> If the reader thread throws an exception (e.g. IOException) then the socket
> should be closed to prevent further messages being sent to the broker. If an
> exception is thrown during the marshalling of a message then there's no way
> for the stream to be set to the beginning of the next message, so all
> communication with the broker should cease at that point. Similarly, if the
> broker is killed, an IOException will probably be detected in the read thread
> first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
