| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Limits for execution group |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ward |
 Posted: Mon Oct 03, 2005 7:20 am Post subject: Limits for execution group |
 |
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
Hi,
Does anyone know if there is a limit to how much one can deploy in a v5 execution group? I'm not looking for best practices etc just about physical limitations.
Reason of my question is the following. When I was deploying my message flows in an execution group it seemed that everything went fine up to the point where I tried to deploy the 7th message flow in the same execution group. At that point the execution group started abending and although the other message flows were still treating messages I could not deploy anything anymore until I did a remove all children of that execution group.
Some details about the environment:
AIX 5.2
WMBv5 CSD04
Some flows use HTTP input node
Anyone seen anything like this before ?
Cheers,
Ward. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Oct 03, 2005 7:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, first, there's a lot of discussion here.
Second, did you get core dumps when the EG abended? Were there errors written to the system log?
Does it work if you install any six of the set of seven flows? Or is there a deployment order dependancy?
Did you follow the instructions for ensuring that you are using the TCP/IP node to connect to DB2, not by using shared memory? (see You get DB2 error message SQL1224N when connecting to DB2)
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ward |
| Posted: Mon Oct 03, 2005 8:35 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
Thanks for your response...
here's some more details:
1) It's in the system log that I found the message flow was abending. Here's an extract, but we got the same few lines over and over again...
| Code: |
Sep 29 10:55:39 eaia3 MQSIv500[210110]: (BRMQI003A.IP_500)[1]BIP2201I: Execution Group started: process '210110'; thread '1';
additional information: brokerName 'BRMQI003A'; executionGroupUUID 'be5bbea0-0601-0000-0080-c37a70c9362d'; executionGroupLabel
'IP_500'; defaultExecutionGroup 'false'; queueManagerName 'MQI003A'; trusted 'false'; dataSourceName 'MQIBRA'; userId 'mqsi';
migrationNeeded 'false'; brokerUUID '729fbda0-0601-0000-0080-c37a70c9362d'; filePath '/usr/opt/mqsi'; workPath '/var/mqsi'. :
BRMQI003A.be5bbea0-0601-0000-0080-c37a70c9362d: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Sep 29 10:56:46 eaia3 MQSIv500[210110]: (BRMQI003A.be5bbea0-0601-0000-0080-c37a70c9362d)[6426]BIP2228E: Severe error: /build/S
500_P/src/CommonServices/Unix/ImbAbend.cpp 458 signal received Abend file: /var/mqsi/errors/BRMQI003A.be5bbea0-0601-0000-0080-
c37a70c9362d.210110.6426.abend action: abort
Sep 29 10:56:47 eaia3 MQSIv500[164696]: (BRMQI003A)[1800]BIP2060W: The broker has detected that the Execution Group IP_500, pr
ocess ID 210110, has shutdown. : BRMQI003A.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3869: ImbAdminAgent::startAn
dMonitorADataFlowEngine: :
Sep 29 10:56:47 eaia3 MQSIv500[210112]: (BRMQI003A.IP_500)[1]BIP2201I: Execution Group started: process '210112'; thread '1';
additional information: brokerName 'BRMQI003A'; executionGroupUUID 'be5bbea0-0601-0000-0080-c37a70c9362d'; executionGroupLabel
'IP_500'; defaultExecutionGroup 'false'; queueManagerName 'MQI003A'; trusted 'false'; dataSourceName 'MQIBRA'; userId 'mqsi';
migrationNeeded 'false'; brokerUUID '729fbda0-0601-0000-0080-c37a70c9362d'; filePath '/usr/opt/mqsi'; workPath '/var/mqsi'. :
BRMQI003A.be5bbea0-0601-0000-0080-c37a70c9362d: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Sep 29 10:57:55 eaia3 MQSIv500[210112]: (BRMQI003A.be5bbea0-0601-0000-0080-c37a70c9362d)[6426]BIP2228E: Severe error: /build/S
500_P/src/CommonServices/Unix/ImbAbend.cpp 458 signal received Abend file: /var/mqsi/errors/BRMQI003A.be5bbea0-0601-0000-0080-
c37a70c9362d.210112.6426.abend action: abort
|
2) Tried only a few combinations but it was every time number 7 out of the 8 flows I was trying to deploy that failed.
3) We are using Oracle 9 in this environment. so don't think there's any impact for us...
Cheers,
Ward |
|
| 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
|
|
|
|
