You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2012/06/08 22:02:23 UTC
[jira] [Commented] (QPID-4047) IoNetworkTransport doesn't use
timeout on socket connect
[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291941#comment-13291941 ]
Rob Godfrey commented on QPID-4047:
-----------------------------------
Seems like a reasonable enhancement. Ideally we should also make the timeout configurable (and possibly have different timeouts for the socket connection and the AMQP connection establishment) however I think we can leave this for another JIRA.
> IoNetworkTransport doesn't use timeout on socket connect
> --------------------------------------------------------
>
> Key: QPID-4047
> URL: https://issues.apache.org/jira/browse/QPID-4047
> Project: Qpid
> Issue Type: Bug
> Components: Java Common
> Reporter: Praveen Murugesan
> Assignee: Rob Godfrey
> Fix For: 0.17
>
> Attachments: addTimeOutOnSocketConnect.patch
>
>
> line 76 of org/apache/qpid/transport/network/io/IoNetworkTransport calls _socket.connect without supplying a timeout value. This is equivalent to an infinite timeout. Re-use the _timeout field within the same class that specifies a 60 second timeout for reads?
> I've attached a patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org