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 2010/07/09 16:34:52 UTC

[jira] Updated: (AMQNET-260) Static Timeout property in FutureResponse

     [ https://issues.apache.org/activemq/browse/AMQNET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQNET-260:
--------------------------------

        Fix Version/s: 1.4.0
    Affects Version/s: 1.3.0
                       1.2.0

> Static Timeout property in FutureResponse
> -----------------------------------------
>
>                 Key: AMQNET-260
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-260
>             Project: ActiveMQ .Net
>          Issue Type: Sub-task
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.4.0
>
>
> The FutureResponse class uses a static property to set the Timeout for a response.   This can lead to issues if the client sets the timeout more than once if the timeout change from infinite to some bounded time span then previous Requests could timeout unexpectedly.  The value should be non-static.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.