Posted: Mon Sep 22, 2003 1:10 am Post subject: Slow CICS bridge when using same messageID
Partisan
Joined: 09 Aug 2001 Posts: 332
First let me give you an high level overview of workflow :
An application, which is a gatherer of data( Data Gatherer), receives a request from an app requesting data. The Data Gatherer then sends out request messages to the data providers, all the message id's that relate to this session have the same message id's so that the message id will be passed back in the Correl Id on the reply message. Reason for this was that the DPL Bridge requires that the Correl Id be set to NEW SESSION CORRELID and so we set the Message Id so it can be passed back in the Correl Id.
The problem is that this causes the DPL Bridge to process these messages in a single thread ( it does not spawn additional threads ) which is a bottle neck in the system. We have stress tested the DPL Bridge using unique message id's ( which is generated by the Queue Manager ) and the DPL Bridge spawns multiple threads and processes the messaged in sub milli-seconds. But this is not the case if the message id is not unique.
If the data gatherer sends out unique message id's then it must keep track of all the Message Ids it sends out and this could possibly be 50 messages.
Is there an alternative solution ?
Thanks _________________ If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
The CICS bridge does require unique message ids to work correctly.
If you dont want to use MQ generated message ids can you include a counter or time stamp in the message id that you generate. _________________ Bob Buxton
Ex-Websphere MQ Development
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum