Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <2109276083.1259169592973.JavaMail.jira@brutus>
Date: Wed, 25 Nov 2009 09:19:52 -0800 (PST)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2088) Change the InactivityMonitor to clear
 its flag as soon as a few bytes are received on a connection rather than
 only after an entire message has been assembled.
In-Reply-To: <136868851.1233155819783.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56111#action_56111 ] 

Hiram Chirino commented on AMQ-2088:
------------------------------------

I think a better approach would be for the wireformat to expose a counter which is incremented as data is read.

That way between inactivity check intervals the inactivity monitor can check to see if that value has changed since it's last check.

> Change the InactivityMonitor to clear its flag as soon as a few bytes are received on a connection rather than only after an entire message has been assembled.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2088
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2088
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.1.0
>            Reporter: Torsten Mielke
>            Assignee: Dejan Bosanac
>            Priority: Critical
>             Fix For: 5.3.0
>
>
> On slow connections with larger messages to be exchanged, the inactivity monitor might kick in, drop the network connection and re-establish it again. This prevents two brokers from exchanging larger messages on a slow connection as the transmission always gets interrupted.
> See the discussion of this on http://activemq.apache.org/slow-networks-drop-large-messages.html. 
> The problem is that the InactivityMonitor always waits for a complete message to be assembled on an active connection before clearing its internal flag.
> I propose to change the behavior of the InactivityMonitor so that it clears its flag already when a few bytes were received on a network connection rather than waiting for the entire message to be sent. This should work around the problem of connections being dropped and re-established periodically when receiving large messages.

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