| Author |
Message
|
| protocol |
 Posted: Wed Jul 13, 2005 3:13 am Post subject: Unable to Deploy |
 |
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi,
I am unable to deploy flows anymore. They were all working fine yesterday.
The following is the error when i am getting in the Event Viewer:
"The broker was unable to put an internal configuration message to message queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE'.
The internal configuration message could not be sent because the message queue was not available.
Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the broker's configuration. "
"A problem was detected with WebSphere Business Integration while issuing MQPUT for WebSphere Business Integration queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE', WebSphere Business Integration queue manager 'QM1'. MQCC=2, MQRC=2024.
The operation on the specified queue or queue manager returned with the indicated WebSphere Business Integration completion and reason code. "
But the queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' is very much there.
The deploy takes a long time and when i try to cancel the deploy, the following is the msg i get :
"BIP1056I: Cancelling all outstanding deploy requests ...
BIP1015I: External exception.
An external exception was caught: 'Could not connect to MQ Queue Manager 'QM1' (reason code=2059)'"
The queue manager QM1 is very much there and running which i can see when i do a dspmq :
QMNAME(QM1) STATUS(Running)
I am using WBI MB v5.0.4 in Win 2000.
Any suggestions as to why this is occurring and the solution for the same ? |
|
| Back to top |
|
 |
| sjensen |
| Posted: Wed Jul 13, 2005 4:57 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
Well 2024 is 'Syncpoint Limit Reached' so the UOW could be to big.
Is this a delta or full deploy?
Cheers
Stefan |
|
| Back to top |
|
|
| Devasis.Sahu |
| Posted: Thu Jul 14, 2005 10:23 pm Post subject: Deploying |
|
|
Apprentice
Joined: 22 Feb 2003
Posts: 43
Location: India
|
Whats the heap size and time out settings for your Configmgr and broker ....Can u try increasing it and deploying the bar file again. See if that helps. Please refer to IBM documentation if u need further help for commands. But of course your MQ Q manager should be running 
Regds |
|
| Back to top |
|
|
| protocol |
| Posted: Fri Jul 15, 2005 12:49 am Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Thanks for your reply guys.
It is resolved now. As Stefan had pointed out , it was due to "'Syncpoint Limit Reached" error. I increased the Maximum Uncommitted Messages value of the Queue Manager and it is working fine now. |
|
| Back to top |
|
|
| ydsk |
| Posted: Tue Jul 19, 2005 8:08 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
How and where did you change the max uncommitted msgs in the qmgr ? Pls clarify.
Thanks. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Jul 19, 2005 8:11 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
runmqsc
alter qmgr maxumsgs(<big value>)
_________________
-wayne |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Tue Jul 19, 2005 10:14 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Delete the outstanding deployings from the config mgr database in the cbroker table, and increase the channel size to max if your config mgr and broker are two diff boxes, and dont put lot of msg flows in the same execution gruop.
It may solve the problem.
Thanks,
Chandra. |
|
| Back to top |
|
|
| ydsk |
| Posted: Tue Jul 19, 2005 11:49 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Even the xmit queues between the broker/configmgrs should be set to maxlength of a msg apart from channels.
Thanks. |
|
| Back to top |
|
|
|
|
