Note

Icon

This article only applies to older versions of ActiveMQ, i.e. 5.3 and 5.4.0. From 5.4.2 onwards this issue has been adressed in the bugs AMQ-2511 and AMQ-2088.

You may experience problems sending large messages using networks across slow links.

The symptoms are usually that the network connection will be dropped and continuously re-established.

This problem arises because the ActiveMQ message broker continuously checks for activity on a socket, and whilst building a large message in the TCP socket buffer, the inactivity monitor will time out - see Configuring Wire Formats and the TCP Transport Reference.
The inactivity monitor uses an activity flag that is only updated after a message is received (in case the connection is not idle).
The monitor then clears the activity flag, waits the timeout amount and peeks at the activity flag. If it's still cleared, then we assume the connection was inactive. When the connection is NOT in use, a keep alive message is sent. But in case the connection is in use because of a larger message being sent/received, no keep alive will be sent and the activity flag will not be updated. That can lead to inactivity timeouts.
Ideally the activity flag would get cleared every time a few bytes arrive from the network... but right now it is only cleared when an entire message is assembled.

You can either set the wireFormat.maxInactivityDuration property to a high value - or disable it (set it to zero) to work around this issue.

e.g. configure your network connection like this:

See also

ActiveMQ InactivityMonitor

© 2004-2011 The Apache Software Foundation.
Apache ActiveMQ, ActiveMQ, Apache, the Apache feather logo, and the Apache ActiveMQ project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram