| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQSI DB2 DataFlow Engine Connections? |
« View previous topic :: View next topic » |
| Author |
Message
|
| smeunier |
 Posted: Tue Apr 27, 2004 6:12 am Post subject: WMQSI DB2 DataFlow Engine Connections? |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
After several encounters with DB2 failures and multiple DB2 configuration changes ( Increased maxappls, set EXTSHM, implemented loopback db), I think I now have a stable environment using WMQSI V2.1 and DB2 7.2
I have been monitoring the number of connections against the DB Instance. I have noticed that the connection rate seems to be increasing. There is one connection for the bipbroker and the rest are for DataFlowEngine process. My messageflows use no DB2 access directly, so the DB connection are purely against the MRM (I suspect). Is there a explaination on how the message flows uses the broker DB and when the DB resource should be freed? Do I need to do anything in the messageflow itself, to release DB connections? I'm ready to release to production, but fear I do not have a handle on the DB2 connection scenario's. |
|
| Back to top |
|
 |
| fschofer |
| Posted: Tue Apr 27, 2004 6:26 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
WMQI 2.1 Admin Guide:
| Quote: |
Broker database connections
The number of connections required by the broker to its database depend to some
extent on the actions of the message flows it is processing. The following
connections are required for each broker:
v Five by internal broker threads.
v One for each Publish/Subscribe neighbor, if the topology has been deployed.
v One for each message flow thread that contains a publication node.
v One for each message flow thread that parses MRM messages.
v A further number if you are using SCADA nodes with MQSeries Everyplace.
The exact number to add depends on whether thread pooling is being used
(determined by the Use Thread Pooling property of the SCADAInput node):
– If Use Thread Pooling is not selected (the default setting) add the number of
SCADA clients that will connect to the SCADAInput node.
– If Use Thread Pooling is selected, add the value in the Max Threads property of
the SCADAInput node. The default value is 500.
If you are using the same database for several brokers, you must take account of
all brokers in your calculations.
The connections for neighbors and publication nodes are only required if you are
using retained publications.
When you start a broker, it opens all connections that it requires to the broker
database for its own operation. When you stop the broker, it releases all current
database connection handles.
If you are using DB2 for your broker database, and you believe the connections
that the broker might require exceed the default allowance of forty, you must
increase the maxappls parameter to a new value based on your calculations.
Broker database |
|
|
| 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
|
|
|
|
