[
https://issues.apache.org/activemq/browse/AMQNET-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-179.
---------------------------------
Resolution: Fixed
Resolved in trunk. Removed the try/catch logic from the TcpTransport's oneway
call and just propagate the exception up the stack. The Connection class
ensures that all exception thrown from a failed send are NMSException's so a
client that is using the TcpTransport only should add a try / catch around
producer.Send calls to catch the error and shutdown or manually reconnect.
As for the Failover transport issues those have I hope all been resolved by
other recent issue resolutions. Open a new issue if you have further trouble
with Failover.
> 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
> Affects Versions: 1.1.0
> Reporter: Igor Katkov
> Assignee: Timothy Bish
> 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.
