You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/10/02 22:03:07 UTC

[jira] [Created] (AMQCPP-429) Response correlator can let a future into its mapping after its been closed causing a hang

Timothy Bish created AMQCPP-429:
-----------------------------------

             Summary: Response correlator can let a future into its mapping after its been closed causing a hang
                 Key: AMQCPP-429
                 URL: https://issues.apache.org/jira/browse/AMQCPP-429
             Project: ActiveMQ C++ Client
          Issue Type: Bug
          Components: Transports
    Affects Versions: 3.4.4, 3.5.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 3.5.0


There's a timing bug that could allow for a request to be put into the request map after the transport is closed meaning it would never be responded to and could lead to a hang. 

--
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] (AMQCPP-429) Response correlator can let a future into its mapping after its been closed causing a hang

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQCPP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-429:
--------------------------------

    Fix Version/s: 3.4.5
    
> Response correlator can let a future into its mapping after its been closed causing a hang
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-429
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-429
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.4.4, 3.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.4.5, 3.5.0
>
>
> There's a timing bug that could allow for a request to be put into the request map after the transport is closed meaning it would never be responded to and could lead to a hang. 

--
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] [Resolved] (AMQCPP-429) Response correlator can let a future into its mapping after its been closed causing a hang

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQCPP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-429.
---------------------------------

    Resolution: Fixed

Fixed now in trunk and 3.4.x
                
> Response correlator can let a future into its mapping after its been closed causing a hang
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-429
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-429
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.4.4, 3.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.4.5, 3.5.0
>
>
> There's a timing bug that could allow for a request to be put into the request map after the transport is closed meaning it would never be responded to and could lead to a hang. 

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