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

ASF GitHub Bot commented on AMQCPP-643:
---------------------------------------

GitHub user RoddieKieley opened a pull request:

    https://github.com/apache/activemq-cpp/pull/17

    AMQCPP-643: Add an option to time out connection attempts when blocked in 
ensureConnectionInfoSent

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/RoddieKieley/activemq-cpp AMQCPP-643

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-cpp/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17
    
----
commit 69f8ea4c9bfff6aeb7f78d3e5e0477df2bc32edd
Author: Roddie Kieley <rkieley@...>
Date:   2018-12-11T16:37:01Z

    AMQCPP-643: Added connection.connectionResponseTimeout to CMS CPP client as 
per JMS client AMQ-6362.

commit fc5488a2836525a2dcf3e292b0d1b4bce4d5e62d
Author: Roddie Kieley <rkieley@...>
Date:   2018-12-12T19:38:38Z

    AMQCPP-643: Added connection.connectResponseTimeout option to 
ActiveMQConnectionFactoryTest::testURIOptionsProcessing.

----


> Add an option to time out connection attempts when blocked in 
> ensureConnectionInfoSent
> --------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-643
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-643
>             Project: ActiveMQ C++ Client
>          Issue Type: New Feature
>          Components: Transports
>    Affects Versions: 3.9.4
>         Environment: HP-UX
> Fedora 27 / gcc
>            Reporter: Roddie Kieley
>            Assignee: Timothy Bish
>            Priority: Major
>
> In some rare cases client side stack traces show that the client can be stuck 
> in ensureConnectionInfoSent waiting forever for a response from the broker.
> We will add an optional timeout to allow this operation to fail which 
> defaults to off via a default timeout of 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to