| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Increasing instances leading to another problem ... |
« View previous topic :: View next topic » |
| Author |
Message
|
| pandug |
 Posted: Fri Feb 26, 2010 2:19 am Post subject: Increasing instances leading to another problem ... |
 |
|
Newbie
Joined: 18 Feb 2010
Posts: 4
|
Hi Friends,
I have 2 main message flows. 1st one builds 3 types of output messages START, NORMAL and DONE. Here, occurrence for START and DONE are single but NORMAL has multiple occurrences. (NORMAL means main message)
In the 2nd flow, I have compute node and 3 label nodes one with START, NORMAL and DONE. So based on the message from previous flow, the corresponding label in the 2nd flow gets processed.
The problem here is START and DONE messages are very small but NORMAL is very large and processing of the NORMAL messages takes a lot of time. (In corresponding label flow, we are using 3rd party tool 'Item field Content Master' to write the message to a file.)
When we had single instance it is working fine. But problem here is, it is taking lot of time to write all NORMAL messages to a file (no. of days and it keeps on increasing every month).
So, we thought of implementing multiple instances in the 2nd flow ...
When we have multiple instances.. 1st instance process the START message and other instances process the NORMAL messages initially. Since, NORMAL message is taking time to process the message mean while one of the instance is processing the DONE message when it reaches the end of the messages in a queue.
But our main frame job starts reading the file when it gets the DONE message. In this case by the time mainframe job starts ...still our flow is processing the NORMAL message and writing to a file.
Can any one help me to resolve the same? Thanks in advance. Your quick response will be highly appreciated.
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 26, 2010 4:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have your monitoring software monitor the input queue and generate a done message when it has been empty for more than the time it takes to process the longest NORMAL message. You first flow then can just strip the DONE message or move it to some "parking" queue. The monitoring software can then place a message to some queue to start a "GET" node to pick up the DONE message when the input queue has been empty for the time it takes to process the NORMAL message...
Alternatively switch to MQ on the MF. No more files to worry about...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 26, 2010 5:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Use aggregation or collection to assemble a list of responses from the NORMAL runs that will also hold off writing out the DONE message until all the NORMAL runs are, you know, DONE. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
