| Author |
Message
|
| dipscool |
 Posted: Mon Sep 18, 2006 5:50 pm Post subject: Message Flow deployment and Execution Group |
 |
|
Novice
Joined: 14 Aug 2006
Posts: 13
|
Hi Everyone
we have Message broker 5 (CSD5) installed on AIX and confhuration manager is on NT. we managed to install all the components successfully.When we are trying to deploy the message flow through Broker toolkit to the defualt execution group we are getting a timeout error
Couple of observations
1. when the broker is inot running if i run the command
mqsilist brokername
its giving execution group - o
there is no name associated with it.we have a similar environment setup in NT also there when we do mqsilist brokername it lists down the name of the execution group as default
2.When the broker is in running state the same command does not give me the name of the execution group but when we try to deploy to the execution group during that time it shows the name of the ex groupn if we do an mqsilist
please reply its urgent |
|
| Back to top |
|
 |
| meenakshi |
| Posted: Mon Sep 18, 2006 8:27 pm Post subject: |
|
|
Novice
Joined: 15 Jun 2005
Posts: 11
Location: India
|
Hi,
Are you able to see the execution group "default" in the toolkit ? If default is giving an error is it worthwhile to create another execution group just so that we can be sure there is no problem with the execution group.
Regarding the timeout problem, you could check if the channels between the queue managers are running. Also check that the user id with which you are trying to deploy is authorized to do so. You can also check the system logs to know the reason of failure.
I hope this helps you
_________________
Meenakshi Sharma
IBM Certified WMQ 5.3 Solution Developer |
|
| Back to top |
|
|
| jbanoop |
| Posted: Mon Sep 18, 2006 9:50 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
when the broker is stopped the mqsilist <brokername> should give you the list of execution groups in the format <name of exe grp>- 0.
AIX behaviour should be similar.
when it is started you should get in the format <name of exe grp>- <pid of the exe grp>.
This info I think is being pulled from the broker db. I am not sure. how ever try stopping the broker and then the broker database (db2stop if using db2) and restart the broker database and then the broker.
Regards,
Anoop |
|
| Back to top |
|
|
| dipscool |
| Posted: Mon Sep 18, 2006 10:23 pm Post subject: |
|
|
Novice
Joined: 14 Aug 2006
Posts: 13
|
Thanks for youor reply
I tried lot of options
1.First of all we cheked following
1.channel is up and running between Broker and Configuration manager.
2.Broker and Configuration manager is starting properly
3.We have stopped the broker ,broker database and then started again same problem
Broker (Running State)
when we do mqsilsit brokername during running state its not displaying the name of the execution group as default.Its displaying as follows
BIP8130I: Execution Group: - 52114
Broker(Running and Deploying state)
While deploying the flows to the broker itb displays
BIP8130I: Execution Group: default - 47448
BIP8130I: Execution Group: - 34222
after the deployment is unsuccessful it comes back to the first state
BROKER(Running state). Default exe group is not displayed.
Unbale to understand the problem
The error that is displayed in Configmanager event log is
"""""error configmanger event log START
( ConfigMgr ) Broker BRK5 (UUID a82fb9c0-0d01-0000-0080-f77d2c2debbf) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments
"""""error configmanger event log END
Request your help |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Sep 18, 2006 10:40 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi dipscool,
Is the problem that you can't see the execution groups ?
--Create one on your own and check using mqsilist.
OR
Is the problem that the deployment is timing out ?
--Check the MQ log files for the QM and see if they are full...
--Check the event viewer log...
--How huge is this flow that you are deploying...if it is huge, first deploy a small flow and verify if your broker and configMgr are working...
Regards. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Mon Sep 18, 2006 10:43 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
this has something to do with the default exe grp created when broker is created.
There has been a lot of discussion on this on the site and u shld try seraching using $SYS_mqsi .
eg:
http://www.mqseries.net/phpBB2/viewtopic.php?t=27298&highlight=sysmqsi
maybe u tried deleting the only execution grp on the broker .. you will find lots of possible solutions on the different posts.
Regards,
Anoop |
|
| Back to top |
|
|
|
|
