MQSeries.net :: View topic - Database Input Node On Two Instances Creates Duplicate Msg

kiruthigeshwar

Hi All,
We have a flow which is triggered by an event table when records are inserted to an application table. The polling interval is 5mins. This flow in turn calls another MQ flow and waits for the response using MQ GET node. When the whole flow is done, it updates the application table with status of each request. the problem is we have two broker instances. As they lookup to the same table sometimes they pick the same record from even table and try to build the message which results in duplicate and the flows are processed in milliseconds difference. This results in error during database insert in the flow causing primary key violation. For which our flow already has logic to check whether it is a duplicate request, still they result in error.

Next we created a table in broker database, once a record is picked and message is built we log the unique values of the message and commit immediately in compute node level. The previous issue is resolved but, a few of the messages are processed by the internally called MQ flow but their status is not updated in the application table.

Does this have anything to do with Transaction Mode.

Please help.
_________________
Regards,
Kiruthigeshwar