| Author |
Message
|
| jpeela |
 Posted: Thu Mar 23, 2006 12:01 pm Post subject: problem with execution group |
 |
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi,
I am using MB6.0 on W2K system with mq5.3 and db2 8.1.
Recently my broker and execution groups stopped running.we rtyed much by changing the time outs and other settings,still no solution.we deleted config manager and configured with a new one,that did not work,using mqsideletebroker deleted broker and added a new that worked neither.So we uninstalled completely the brokr and reinstalled.
this time the broker was running but the execution group is not running,checked for the errrors in the event viewer and logs which gave a timed out error
( WBRK6_DEFAULT_BROKER ) Execution Group '' failed to return an internal configuration 'Start' message response within a 60 second time period.
and in the tool kit we are having this error.
BIP2087E: Broker WBRK6_DEFAULT_BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
and in the broker default queue manager the broker control queue and broker execution group que are having one message each.
Can some one suggest me some solution to this problem.
_________________
Jogi |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 23, 2006 12:07 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It would have been better to spend more time looking for errors in the original situation.
That said, let's try and solve the current situation. Did the broker complete it's startup properly? You should see messages in the Event Viewer - > Application that indicate that the broker started or failed to start. Hopefully it will say that it started.
What does the output of mqsilist show?
Is DB2 running properly?
Is MQ running properly?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 23, 2006 12:21 pm Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi jefflowery,
Ya mqsilist is showing this
C:\Program Files\IBM\MQSI\6.0>mqsilist
BIP8099I: DbInstMgr: DatabaseInstanceMgr6 -
BIP8099I: Broker: WBRK6_DEFAULT_BROKER - WBRK6_DEFAULT_QUEUE_MANAGER
BIP8099I: ConfigMgr: WBRK6_DEFAULT_CONFIGURATION_MANAGER - WBRK6_DEFAULT_QUEUE_MANAGER
BIP8071I: Successful command completion.
i checked the mq there is a warning in the default queuemanager.the channel initiator and the listener not running .i tried starting them but showing an error,
reason: MQRC_OBJECT_IN_USE
and a warning :Unexpected return code, '20', from command 'RUNMQCHI -qSYSTEM.CHANNEL.INITQ -mWBRK6_DEFAULT_QUEUE_MANAGER'.
Can I try change the initiation queue parameter.
Orelse can u suggest some solution to this.
_________________
Jogi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 23, 2006 12:36 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Stop the broker and config mgr.
Stop the queue manager.
Start only the queue manager.
Confirm that the listener and the channel initiator are running. If not, check the Event Viewer for errors from MQ.
Troubleshooting 101, day 1. One thing at a time!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 23, 2006 1:25 pm Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi,
Ya now the channel initiator as well as the listener are running.And now when i started my toolkit and connectting my config manager its again showing the execution group not running.
and again the ssame errors
BIP2066E: Broker WBRK6_DEFAULT_BROKER (UUID 3d4eee27-0a01-0000-0080-ecf365a66232) was unable to retrieve an internal configuration response message for execution group 'broker' within the 360 second Configuration Timeout.
and now the broker config reply queue's depth is 7 msgs.and control and execution group que's depth is one each.
_________________
Jogi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 23, 2006 1:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are the broker and the config mgr sharing a queue manager?
Also,
| jefflowrey wrote: |
| Did the broker complete it's startup properly? You should see messages in the Event Viewer - > Application that indicate that the broker started or failed to start. Hopefully it will say that it started. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jpeela |
| Posted: Thu Mar 23, 2006 1:37 pm Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
ya broker and configmgr started properly,they are sharing WBRK6_DEFAULT_QUEUE_MANAGER
[/quote]
_________________
Jogi |
|
| Back to top |
|
|
| ydsk |
| Posted: Thu Mar 23, 2006 2:40 pm Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
| Do you have v5 and v6 brokers on the same Windows machine ? Can you describe the configuration of v5 brokers/configmgrs if you have them on the same box ? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Mar 23, 2006 7:57 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi jpeela,
What user id are you using for all the startup/stop.
Is it the MB administrator. Did you try to stop/start with any other id before ?
Can you disconnect the brokers from configMgr in the toolkit and connect again...does it give any errors ?
Regards. |
|
| Back to top |
|
|
| jpeela |
| Posted: Fri Mar 24, 2006 6:47 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi evry one,
ydsk and elvs gn,
I have MB6.0 with mq 5.3 and db2 8.1 all on the same W2K machine.
I start stop with same username and password.
while disconnecting and connecting the cfgmgr there are no errors in the logs but warnings in the elerts that execution group not running.
jefflowery,
my cfgmgr and broker started properly.
the following is some info from the event viewer, could this help out.
( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) The Configuration Manager is available for use
( WBRK6_DEFAULT_BROKER. ) Execution Group started: process '1180'; thread '388'; additional information: brokerName ''WBRK6_DEFAULT_BROKER''; executionGroupUUID ''f559ee27-0a01-0000-0080-ecf365a66232''; executionGroupLabel ''''; defaultExecutionGroup 'false'; queueManagerName ''WBRK6
The execution Group has started using process '3000' and thread '2996' and will now start processing messages
( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) The WebSphere Message Brokers service has started at version '6000'; process ID 2548.
The WebSphere Message Brokers service executable has been started.
WebSphere MQ queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' started.
( WBRK6_DEFAULT_BROKER ) A problem was detected with WebSphere MQ while issuing 'MQCONN' for WebSphere MQ Queue Manager ''WBRK6_DEFAULT_QUEUE_MANAGER''. MQCC=2, MQRC=2059.
(MQRC_Q_MGR_NOT_AVAILABLE) but in the wizard the quemanager is running ,the channel inmitiator and listener are also running.
So cuold this info would be helpful for solving this problem.
_________________
Jogi |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 24, 2006 1:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I had a similar problem on Unix. The broker was running but would refuse any deploy and take a lot of time for the deploy....
The problem was running out of filespace in /var/mqsi... (a coredump was using up most of the space. Probably created because of a wrong parm in startup for the logs.)
So make sure the broker has enough filespace...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 25, 2006 6:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jpeela wrote: |
( WBRK6_DEFAULT_BROKER ) A problem was detected with WebSphere MQ while issuing 'MQCONN' for WebSphere MQ Queue Manager ''WBRK6_DEFAULT_QUEUE_MANAGER''. MQCC=2, MQRC=2059.
(MQRC_Q_MGR_NOT_AVAILABLE) but in the wizard the quemanager is running ,the channel inmitiator and listener are also running.
So cuold this info would be helpful for solving this problem. |
You bet! This tells you that for some reason, the broker was not able to connect to the queue manager! No wonder it can't process any messages!
Are there any other messages from the broker compoenent during it's startup?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jpeela |
| Posted: Tue Mar 28, 2006 8:00 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
jefflowery wrote,
| Quote: |
jpeela wrote:
( WBRK6_DEFAULT_BROKER ) A problem was detected with WebSphere MQ while issuing 'MQCONN' for WebSphere MQ Queue Manager ''WBRK6_DEFAULT_QUEUE_MANAGER''. MQCC=2, MQRC=2059.
(MQRC_Q_MGR_NOT_AVAILABLE) but in the wizard the quemanager is running ,the channel inmitiator and listener are also running.
So cuold this info would be helpful for solving this problem.
You bet! This tells you that for some reason, the broker was not able to connect to the queue manager! No wonder it can't process any messages!
Are there any other messages from the broker compoenent during it's startup? |
( WBRK6_DEFAULT_BROKER ) The WebSphere Message Brokers service has started at version '6000'; process ID 3072.
The WebSphere Message Brokers service executable has been started.
| Quote: |
WBRK6_DEFAULT_BROKER ) The broker was forced to stop an execution group process, process ID was '708'.
One reason for this is that the WebSphere Message Brokers executable bipbroker failed unexpectedly. |
(what could b the problem)
The execution Group has started using process '1520' and thread '3188' and will now start processing messages.
| Quote: |
| Publish/Subscribe subscriptions recovery started. (but ther r no such subscriptions in my broker) |
Execution Group '' failed to return an internal configuration 'Start' message response within a 60 second time period.
_________________
Jogi |
|
| Back to top |
|
|
| jpeela |
| Posted: Mon Apr 03, 2006 6:12 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi
evry one ,
thanx for ur support.we have created a new broker and again tried connecting the broker ,again the same problem ,execution grup not running.when I deployed a flow an error saying that already flow is deployed.even I create a new execution group ,still the same problem.any solution.
_________________
Jogi |
|
| Back to top |
|
|
| EAI Developer |
| Posted: Mon Apr 03, 2006 9:32 am Post subject: |
|
|
Centurion
Joined: 30 Nov 2005
Posts: 101
Location: US
|
Hi jpeela,
You can click an option called " Remove references to previously delete broker " in the configuration manager proxy Exerciser to ensure removal of old binding of prev broker.After that create a new broker.By the way u will get this option by right clicking the pubsub topology in the CMP exerciser after u connecting to Config Mgr.
Cheers,
Raj. |
|
| Back to top |
|
|
|
|
