MQSeries.net :: View topic - Delay in completion of UPES activity instance.

vijaycr

We have some UPES activities each of them take some milliseconds to finish, less than a second most of the time. But we found that in the audittrail some of the event for eventcode 2032(Activity Implementation Complete) is logged about 5 seconds later. None of our activity implementations run this long.

To introspect, in a test system, we wrote a simple application that would post one message(a simple Helo World! message which is invalid) that persecond on to the EXEXMLIMPUTQ and monitored the fmcsys.log We found that error(FMC01100E Incorrect XML document) messsages are logged in batches of 5. So, I presume that the execution server 'polls' the EXEXMLINPUTQ every 5 seconds.

Is this the expected behaviour?
Has anyone else noticed this before ?.
Is there any way to increase/decrease this interval?.

Not that its a killer but thought it is a interesting discussion topic.