[jira] Resolved: (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.

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

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

Dejan Bosanac resolved AMQ-2088.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0

Fixed in SVN revision 742458. Thanks to Vedran Vrbanc for initial fix patch.

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