Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1895123468.1207674332746.JavaMail.jira@brutus>
Date: Tue, 8 Apr 2008 10:05:32 -0700 (PDT)
From: "Jim Gomes (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Closed: (AMQNET-81) FutureResponse transport correlater does
 not handle transport timeout correctly.
In-Reply-To: <1926999751.1207674092611.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Jim Gomes closed AMQNET-81.
---------------------------


> FutureResponse transport correlater does not handle transport timeout correctly.
> --------------------------------------------------------------------------------
>
>                 Key: AMQNET-81
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-81
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>    Affects Versions: 1.0
>         Environment: .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.0
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> While waiting for a response, there is a timeout value that can be set on the transport protocol.  However, the FutureResponse class will continue to loop and wait even after the timeout has expired.  The default timeout value is INFINITE (-1).  With a timeout value of infinite, there is no need to have a loop to re-enter the timewait period.  The timewait period should only be entered once.  When the timeout expires without a return response from the broker, then a null response should be returned to the client.

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