I see the problem - there is no way to determine the end of dataset. The assumption is that the request for stats and the handling of the messages would be decoupled - so you could periodically query the stats - but then process the results asynchronously. Like you say, if the list of destinations is constantly changing, you don't know when the end of the stats generated finishes. We may need to add an additional null message so you can determine this - but it will need to be optional (default off). I'll look at adding this in.
cheers, Rob -- View this message in context: http://activemq.2283324.n4.nabble.com/how-to-detect-end-of-dataset-tp4658775p4658823.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
