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:02 UTC
[jira] [Created] (AMQNET-397) Connection timeout can be changed
Sergei Sokolov created AMQNET-397:
-------------------------------------
Summary: Connection timeout can 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
[jira] [Commented] (AMQNET-397) Connection timeout cannot be
changed
Posted by "Sergei Sokolov (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQNET-397) Connection timeout cannot be changed
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-397:
--------------------------------
Priority: Minor (was: Major)
Fix Version/s: (was: 1.5.6)
> 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
[jira] [Commented] (AMQNET-397) Connection timeout cannot be
changed
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474083#comment-13474083 ]
Timothy Bish commented on AMQNET-397:
-------------------------------------
Patch lacks unit tests
> 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
[jira] [Updated] (AMQNET-397) Connection timeout cannot be changed
Posted by "Sergei Sokolov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergei Sokolov updated AMQNET-397:
----------------------------------
Attachment: AMQNET-397.patch
> 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
>
> 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
[jira] [Updated] (AMQNET-397) Connection timeout cannot be changed
Posted by "Sergei Sokolov (JIRA)" <ji...@apache.org>.
[ 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