You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Sergei Sokolov (JIRA)" <ji...@apache.org> on 2012/10/11 14:17:04 UTC

[jira] [Updated] (AMQNET-397) Connection timeout cannot be changed

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

Sergei Sokolov updated AMQNET-397:
----------------------------------

    Summary: Connection timeout cannot be changed  (was: Connection timeout can be changed)
    
> 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
>             Fix For: 1.5.6
>
>
> 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