| Author |
Message
|
| RaviKrG |
 Posted: Mon Jan 03, 2011 6:53 am Post subject: ConfigMgr Not Responding |
 |
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Hi, have 4 Brokers (3 on AIX and 1 on Sol) which is connected to one Config Mgr on Windows. Every Time we work on toolkit it says that the toolkit was able to connect to the qmgr but the configmgr did not respond. We did restart the config mgr many times but still this did not solve our problem. Just wondering if I have any other alternatives as this hampers our prod for the deployements. All are 6.1 Versions
Thanks |
|
| Back to top |
|
 |
| RaviKrG |
| Posted: Mon Jan 03, 2011 6:56 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
| Any activity I do I see tha the queue SYSTEM.BROKER.CONFIG.QUEUE increases and gets the message but no reply on the queue SYSTEM.BROKER.CONFIG.REPLY. and when I start the config mgr then the reply q has the messages but still the action is not perfomed as the toolkit event log does not say anything .. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Jan 03, 2011 7:11 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Also I see lot of differences in the toolkit. The flows are running but the toolkit shows as not running
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 03, 2011 7:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RaviKrG wrote: |
| Also I see lot of differences in the toolkit. The flows are running but the toolkit shows as not running |
Given that the Toolkit is getting it's information from the ConfigMgr (or not in this instance) that's not exactly surprising.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 03, 2011 7:19 am Post subject: Re: ConfigMgr Not Responding |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RaviKrG wrote: |
| We did restart the config mgr many times but still this did not solve our problem. |
So was this based on any plan or just the "if we restart it often enough the magic will come back"?
(Which isn't that unreasonable on Windows)
So what does the ConfigMgr log (not the event log that Toolkit shows) say when you try and start it? Anything in the event viewer? Have you attempted any diagnostic or problem resolution apart from systematic & repeated restart attempts?
| RaviKrG wrote: |
| Just wondering if I have any other alternatives as this hampers our prod for the deployements. |
If you're asking if there's any way to deploy to the brokers without using the ConfigMgr then no, there's no way to change the configuration of the brokers without using the software that manages the configuration. 
You could of course create a new ConfigMgr and have that do it, but without knowing why the current one has stopped working there's no guarantee that a) the new one will work or b) the new one will not stop working in the future.
You could repeat the process, but then you'll have a trail of unstartable ConfigMgrs....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Jan 03, 2011 8:10 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Thanks Vitor for the update. The config mgr was restarted just at the times when we are getting that its not responding  and we try to connect to the toolkit after 10 min and it works (sometimes it does not and take some more time) . I did try to look at the event viewer logs but there was nothing that really I could find related to the config mgr which could really give me a way. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 03, 2011 8:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RaviKrG wrote: |
| The config mgr was restarted just at the times when we are getting that its not responding and we try to connect to the toolkit after 10 min and it works (sometimes it does not and take some more time). |
So are you saying that after repeated restarts it suddenly starts responding? And/or that sometimes even if you don't restart it, it suddenly starts working? This implies that you either have the timeout set too low or (more likely) need to set it higher to cater for times of extreme system load.
You also need to see if the system is indeed under load at the times of unresponsiveness, and if so why?
| RaviKrG wrote: |
| I did try to look at the event viewer logs but there was nothing that really I could find related to the config mgr which could really give me a way. |
This reinforces the view that the ConfigMgr was running continuously but wasn't responding fast enough for the Toolkit. You should at least have seen messages in the Event Viewer corresponding to the starting & stopping of the ConfigMgr, and if there's nothing in that about the ConfigMgr crashing this implies it was running.
Which also explains why restarting it wasn't helping.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Jan 03, 2011 8:33 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Yep got something now at one place in the event viewer once ..
The WebSphere Message Brokers service detected that executable 'bipconfigmgr.exe' terminated, exit code 1.
An executable terminated unexpectedly.
The WebSphere Message Brokers service will restart the executable automatically unless the broker is currently shutting down. Determine the reason for the unexpected termination of this executable.
this was when we tried to stop the configmgr through the services then it was in stopping state for a very very long time and when we did not get anything then finally killed the configmgr process. and then when it was started then it suggests that
The WebSphere Message Brokers service has started at version '6103'; process ID 1720.
The WebSphere Message Brokers service executable has been started.
No user action required.
so I think there was no problem suring startup except during stopping where we had to kill the process which I never fill to do so
Now I think I am left with two options if I am not wrong.
1) Increase the time out
2) out of five brokers I can put as 3 broker to 1 config mgr and 2 brokers to the other config mgr..
ok .. then sure Vitor I will check both the things now and get back.. as this is really making us in lot of trouble.. will try to be back soon
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 03, 2011 8:40 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RaviKrG wrote: |
| The WebSphere Message Brokers service has started at version '6103'; process ID 1720. |
Considered applying some maintenance? Very unlikely to be a cause of this problem but still.....
| RaviKrG wrote: |
| so I think there was no problem suring startup except during stopping where we had to kill the process which I never fill to do so |
That sounds more like a broker process than a ConfigMgr one.
| RaviKrG wrote: |
| 1) Increase the time out |
Yes
| RaviKrG wrote: |
| 2) out of five brokers I can put as 3 broker to 1 config mgr and 2 brokers to the other config mgr.. |
Why would that help? 5 brokers in a topology is only fractionally more work than 3 & doesn't address the fundamental problem of why the ConfigMgr process is running slowly and/or failing to close cleanly.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 03, 2011 9:58 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vitor wrote: |
| RaviKrG wrote: |
| The WebSphere Message Brokers service has started at version '6103'; process ID 1720. |
Considered applying some maintenance? Very unlikely to be a cause of this problem but still.....
|
Actually it probably will help. There were a few posts here back when 6.1.0.3 was the latest version where a bunch of us were dealing with slow Config Managers. Deploys would take forever, or would time out.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 03, 2011 10:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| Vitor wrote: |
| RaviKrG wrote: |
| The WebSphere Message Brokers service has started at version '6103'; process ID 1720. |
Considered applying some maintenance? Very unlikely to be a cause of this problem but still.....
|
Actually it probably will help. There were a few posts here back when 6.1.0.3 was the latest version where a bunch of us were dealing with slow Config Managers. Deploys would take forever, or would time out. |
Well trout me pink! 
There you go then. Another convincing reason to always be at the latest maintenance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jan 04, 2011 7:19 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Indeed; a fair few deployment/administration performance improvements went into V6.1.0.4.
Even more went into V7  |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Wed Jan 05, 2011 10:59 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
| Thanks again for the reply. Since we are using clearcase together with toolkit 6103 and the toolkit was migrated to 6108 but after the upgrade we faced lot of issues while checking in/out the codes in cc. so finally we have removed the upgrade and are using 6103 as this is working fine with cc. also we have increased the time out value from the toolkit but this did not help. Even when we try to open the event log (of the toolkit) it does not open and gives an error that it was able to connect to qmgr but the config mgr did not respond and to increase the time out. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Thu Jan 06, 2011 1:58 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
| I made a clean start of the broker and config mgr. and have increased the time out vaue also .. I try to stop one message flow under an eg. I see the system.broker.config.queue getting one message. I did a browse and checked it is for stopping the message flow (only a hint). now I see the toolkit showing that waiting for a responce from the configuration manager. and I left this about 30 min but no help |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 06, 2011 5:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
So it comes to this: which problem would you sooner have?
- can't stop flows if you use 6.1.0.3
- can't check in/check out if you use 6.1.0.8
I know which I'd prefer, but I'm not you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
