| Author |
Message
|
| klabran |
 Posted: Fri Feb 17, 2006 3:14 pm Post subject: WBIM deploy timeout loop??? |
 |
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
I have been attempting to deploy a flow but it never deploys. It eventually times out.
I have had this happen before and was able to correct by stopping the broker and config mgr service then delete the message in the system broker deploy queue and restart the services....
It's not working now. I can't deploy anything because of this. I have even set the system deploy queue to non-persistent and reboot the server to no avail. I am guessing there is an entry in the DB2 DB but I don't know where that upon reboot is resending the message???
I have also cancelled the deploy in the toolkit but this doesn't help either.
Any ideas?
Thanks,
Kevin |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Sat Feb 18, 2006 3:03 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Any errors in the system log or toolkit's event log editor? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 18, 2006 7:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I've seen this in V6.
Easy remedy:
1) Cancel deployment
2) Disconnect broker topology
3) Reconnect broker topology
4) Redeploy
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| klabran |
| Posted: Tue Feb 21, 2006 1:15 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
mqmatt - When I try to deploy I am getting:
BIP2066E: Broker WBRK_BROKER was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
I am using MQ 5.3 and WBIM 5 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 21, 2006 6:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Is there a default path between your broker's qmgr and the config qmgr? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| klabran |
| Posted: Wed Feb 22, 2006 8:12 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
default path???? The qmgr is on the same server as the brkr and config mgr.
Forgive me for my ignorance on this one....
I will say that the deploy to this broker has worked in the past..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 22, 2006 8:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is the broker using the same qmgr as the configmgr?
Is the broker using the same service user as the configmgr?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| klabran |
| Posted: Wed Feb 22, 2006 8:42 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Feb 22, 2006 9:34 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
OK - look at the depths of the following queues:
a) SYSTEM.BROKER.ADMIN.QUEUE
b) SYSTEM.BROKER.ADMIN.REPLY
c) SYSTEM.BROKER.EXECUTIONGROUP.QUEUE
A message on (a) means that the broker isn't running; on (b) means that the Config Manager isn't running; on (c) suggests a problem with the execution group.
From what you say, it looks like (c) may be the culprit. I'd suggest trying to deploy to a new execution group, although you might need to cancel deployment first.
To work out why this problem happened, check the event log for clues.
-Matt |
|
| Back to top |
|
|
| dilse |
| Posted: Wed Feb 22, 2006 9:47 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
| Also do you see any errors in the event viewer? Let us know. |
|
| Back to top |
|
|
| klabran |
| Posted: Wed Feb 22, 2006 11:21 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
dilse - the event viewer is giving
BIP2066E: Broker WBRK_BROKER was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
mq_matt - the ExecutionGroup.Queue is the one with the depths. In times past I have been able to stop the cfg and brkr services and empty this queue then restart the services and continue on.
This is not working now. I have even set the persistence of this queue to non-persistent, cancelled deployment, rebooted server and the queue will after the reboot have a message in it??????
How is this happening???? I am wondering if there is a record in the DB2 DB that is not getting cleared and thus when the brkr and cfg services restart they put this message back on the queue....?
I have also emptied the queue myself and then resubmitted my deploy (with and without a cancel deployment) and the deploy eventually times out.....???
Kevin |
|
| Back to top |
|
|
| klabran |
| Posted: Wed Feb 22, 2006 4:04 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
to continue.....
I created a new exe group and it has the same issue.
Right now I am getting messages on system.broker.admin.queue and system.broker.executiongroup.queue and system.broker.config.reply depending on what I do.....
It seems the only way out of this one is to restore my DB2 DB.... 
I or the other programmer have no idea what happened to bring this about. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 22, 2006 4:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you get any error messages in the toolkit?
Could it be that there is an error and the code is not deployable?
Any dependencies not satisfied?
Can you remove the old version and add it back again (the old version) (only if not production) ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Feb 23, 2006 1:43 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
What version/fixpack level are you running?
In addition to what fjb_saper says, check that you're up-to-date on fixpacks and that the CM and broker are on the same fixpack level.
In parallel, I'd also suggest that you raise a PMR so my colleagues can do some further investigation. Please include all the information you've provided here.
-Matt |
|
| Back to top |
|
|
| klabran |
| Posted: Thu Feb 23, 2006 6:54 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
fjb_saper - I only get a timeout in the toolkit and event viewer....
BIP2066E: Broker WBRK_BROKER was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
There is not an error in the code for a few reasons...
We have been working and deploying the same bar file successfully to this server before the issue started. To eliminate an issue with the fiel I tried to deploy a known bar file that is on both a development and production server without any changes recently. It has given me the same results.
mqmatt - good question... It looks like WBIM is at FP4 but my DB and MQ are at initial install levels..... I'll put this server at the same level as my other servers and report back if this helps.
Kevin |
|
| Back to top |
|
|
|
|
