You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2012/08/13 13:26:38 UTC

[jira] [Commented] (QPID-4051) [Java client] the 'connecttimeout' ConnectionURL option is no longer used

    [ https://issues.apache.org/jira/browse/QPID-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433070#comment-13433070 ] 

Keith Wall commented on QPID-4051:
----------------------------------

Hi Robbie,

No comments against the code/tests, but I thing we should add a sentence to the Programming in Apache Qpid docbook describing the behaviour of zero.  It should have words to the effect of "A timeout of zero is interpreted as an infinite timeout. The connection will then block until established or an error occurs."

http://qpid.apache.org/books/trunk/Programming-In-Apache-Qpid-Book/html/QpidJNDI.html#section-jms-connection-url


                
> [Java client] the 'connecttimeout' ConnectionURL option is no longer used
> -------------------------------------------------------------------------
>
>                 Key: QPID-4051
>                 URL: https://issues.apache.org/jira/browse/QPID-4051
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18
>            Reporter: Robbie Gemmell
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: 0.19
>
>
> The 'connecttimeout' ConnectionURL option is no longer used.
> It appears that the option was only ever used for the 0-8/0-9/0-9-1 client path, but its use there was broken with I/O updates made in 2009 (apparently here: http://svn.apache.org/viewvc/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/client/transport/SocketTransportConnection.java?r1=726140&r2=825362&pathrev=1143866&diff_format=h) before Qpid 0.6 went out and presumably it has been unused ever since.
> QPID-4047 introduced a fixed timeout on the socket connect call, but we should restore the 'connecttimeout' option to make it configurable again (possibly adding a system property in the process).

--
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