[
https://issues.apache.org/activemq/browse/AMQ-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vedran Vrbanc resolved AMQ-2065.
--------------------------------
Resolution: Duplicate
This is a known issue. It is caused by a bug in the InactivityMonitor transport
class.
The cause and workaround is explained in more detail in AMQ-2088.
http://issues.apache.org/activemq/browse/AMQ-2088
> Inactivity monitor fires on slow transfer of large message
> ----------------------------------------------------------
>
> Key: AMQ-2065
> URL: https://issues.apache.org/activemq/browse/AMQ-2065
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.1.0, 5.2.0
> Reporter: Mike Atkin
>
> I have been investigating using ActiveMQ as a transport for shipping
> PostgreSQL log files as a method of offsite backup. PostgreSQL periodically
> produces 16meg files which I package up in a BytesMessage and place on a
> queue which is then emptied by an offsite machine. This works fine when
> testing locally over fast links, but when trying it over slow links the
> inactivity monitor throws an exception part way through the message transfer
> despite a network dump showing constant data traffic.
> I am guessing this is because the monitor does not recognise the transfer of
> the data as activity, only the command to retrieve it?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
