MQSeries.net :: View topic

fatherjack · Posted: Fri Jun 18, 2010 3:06 am Post subject:

I can sort of understand why I'm seeing what I am seeing but am not sure if it's strictly what you'd want to happen. Here's the scenario:

I have a collector node with two input terminals called MQ and FILE. Each has a quantity setting of 1. The collection expiry is set to 300 seconds.

A message arrives on MQ and is safely stashed away on SYSTEM.BROKER.EDA.COLLECTIONS queue.

I then (accidentally) redeployed the flow.

After 300 seconds has lapsed nothing has come out of the expire terminal of the collector node. I guess because the redeploy stopped and started the flow and it has lost track of the fact there was a half complete collection.

If another message arrives at MQ this one eventually (after 300 secs) goes down the expire route in the flow as expected. My first message is still stuck in SYSTEM.BROKER.EDA.COLLECTIONS queue.

If a message arrives at the FILE terminal a collection is successfully propagated to the Out terminal of the collector node. I guess because the collector rules are satisfied i.e. one message from MQ and one from FILE.

But really the collection which includes the now very old message from MQ should have expired by now. Or should it? I dunno. Any thoughts?
_________________
Never let the facts get in the way of a good theory.