| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Flow Additional Instances not being actioned |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rookwood |
 Posted: Fri Feb 04, 2011 7:36 am Post subject: Flow Additional Instances not being actioned |
 |
|
Novice
Joined: 26 Aug 2004
Posts: 13
|
Hi,
we have a relatively simple message flow, input node connected as follows:
Failure terminal to MQoutput node,
Catch terminal to Trace node then throw node
Out terminal to compute node
The compute node uses sybase stored procs to record message content for our technical logging
The flow is defined with 10 additional instances configured to "Use Pool Associated with Message Flow"
However when deployed it will not instanstiate additional threads even when input queue depth is 10,000+
I have replaced the above flow with a simple mqinput to mqoutput flow with additional instances as a test to exclude possible issues with the queue itself and this happily ramps up the full thread allocation.
Any suggestion s as to what might be throttling the thread creation of the flow.
running version 7.00.2
Cheers
G |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 04, 2011 8:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| The compute node uses sybase stored procs to record message content for our technical logging |
You think this might have something to do with it?
An alternate design might be to have the logging go to a queue and have a scalable app pick it up and insert it into the DB. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Feb 05, 2011 6:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| Quote: |
| The compute node uses sybase stored procs to record message content for our technical logging |
You think this might have something to do with it?
An alternate design might be to have the logging go to a queue and have a scalable app pick it up and insert it into the DB. |
Broker IS a scalable app. 
There's no particular reason a flow would not instantiate additional threads unless the deployed bar did not set additional instances. Check what runtime says.
If runtime says ten instances, but only one is running (and only one OPPROC on queue), then take a service trace and open a PMR. |
|
| 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
|
|
|
|
