MQSeries.net :: View topic - Maximum concurrent events vs really processed events

fradev

Hi all, I am a newbie here.

I have encountered a strange behaviour of ICS running this scenario:
In a collaboration group where all objects have the same maximum number of concurrent events set (in particular set to '2'), the main object can choose (depending on processed record) to call a specific child object (each Coll Obj is called by a specific BO). The main Obj can choose between 3 different child Obj.

When the main Obj call one of these Child Coll bj (and it happens only with this specific Obj, not with the two others) this Child Coll takes the event and not process them and the only way to unlock situation is to delete events tables.

The other peculiarity is that such strange behaviour not happens in every case; I have processed more than 1000 records calling this specific child obj and I have not encountered any problems.

I have noticed , taking a look at the "flow status" window in the system manager, that when this collaboration is in this "locked" status even though the maximum concurrent event is set to 2 ICS has taken more events (I have not counted them, but I think is the maximum allowed by ICS) and all of them are in waiting to be processed, but nothing happens.

I hope someone could help me.

Thanks in advice!

fradev