[
https://issues.apache.org/jira/browse/AMQNET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474086#comment-13474086
]
Sergei Sokolov commented on AMQNET-397:
---------------------------------------
Yeah, there is no unit test inside. It would be great if anyone could write a
unit test.
I use that patch in the production for about a year. Just updated to version
1.5.6 and had to apply my patch... So I decided to share it with the community.
But if it's not ok, then just forget about that.
> Connection timeout cannot be changed
> ------------------------------------
>
> Key: AMQNET-397
> URL: https://issues.apache.org/jira/browse/AMQNET-397
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.6
> Environment: Windows
> Reporter: Sergei Sokolov
> Assignee: Jim Gomes
> Priority: Minor
> Attachments: AMQNET-397.patch
>
>
> The problem with current socket connection is that you can't specify the
> timeout if broker is unavailable. It happens du to .NET implementation of
> sockets doesn't accept timeout as an argument.
> Simple workaround is implemented
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
