activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Moved: (AMQNET-14) An unhandled exception in the TcpTransports' reader thread should close the connection (and inform the app)
Date Tue, 27 Feb 2007 10:39:04 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

james strachan moved AMQ-995 to AMQNET-14:
------------------------------------------

        Fix Version/s:     (was: 4.1.0)
                       1.0
          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: 4.0.2)
                  Key: AMQNET-14  (was: AMQ-995)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> An unhandled exception in the TcpTransports' reader thread should close the connection
(and inform the app)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-14
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-14
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>         Environment: Windows
>            Reporter: Rob Lugt
>         Assigned To: james strachan
>             Fix For: 1.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message