[ https://issues.apache.org/activemq/browse/AMQNET-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Katkov updated AMQNET-179: ------------------------------- Attachment: patchfile.txt Patch to fix. > TcpTransport.cs consumes transport-related exceptions > ----------------------------------------------------- > > Key: AMQNET-179 > URL: https://issues.apache.org/activemq/browse/AMQNET-179 > Project: ActiveMQ .Net > Issue Type: Bug > Components: ActiveMQ Client > Affects Versions: 1.1.0 > Reporter: Igor Katkov > Assignee: Jim Gomes > Fix For: 1.2.0 > > Attachments: patchfile.txt > > > TcpTransport.cs consumes transport-related exceptions > Therefore there is no way to handle broken connections in the client > application. > To reproduce: > 1. Connect c# to a broker via tcp transport > 2. Send a few messages > 3. Restart the broker > 4. Bingo! Client application thinks connection is up, while it's in fact > broken for good. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.