[#MB-706] Concurrent access to maxPageSize - via JMX and message dispatch can cause dispatch to think there is nothing in the store and stop dispatch

FUSE Message Broker

Concurrent access to maxPageSize - via JMX and message dispatch can cause dispatch to think there is nothing in the store and stop dispatch

Created: 26/Jul/10 03:48 PM Updated: 17/Aug/10 12:30 PM

Component/s:

broker

Affects Version/s:

5.3.0.6-fuse

Fix Version/s:

5.4.0-fuse-00-00

Issue Links:

Linked

This issue is linked to:

~~MB-668~~ Message Broker Stops Dispatching from Queues

Description

« Hide

trouble shooting http://fusesource.com/issues/browse/MB-668 causes the invocation of setMaxPageSize on a Destination from JMX that resulted in the broker dispatch loop getting into a state where it thinks there is nothing to dispatch. This needs to be resolved so that this situation cannot occur again.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Gary Tully added a comment - 26/Jul/10 03:50 PM

This issue will ensure the JMX contention with dispatch is removed

[ Permlink | « Hide ]

Gary Tully added a comment - 17/Aug/10 12:30 PM

There have been improvements (from other unrelated issues) to the logic in doPageIn Queue.java such that the negative toPageIn count will no longer occur in the event of a concurrent change to the max page size.