| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configmgr taking a lot of time to connect from toolkit |
« View previous topic :: View next topic » |
| Author |
Message
|
| bloomy |
 Posted: Wed Feb 11, 2009 11:23 am Post subject: Configmgr taking a lot of time to connect from toolkit |
 |
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
Hi,
We have a configmgr on AIX5.3, message broker 6.1.02
We had an issue with derby logs getting corrupted and had to recreate the configmgr, as we had no backup of the configmgr, we had to add the brokers using adopt broker from Configmgr proxy API.
After doing this we are seeing very late response from the configmgr, it takes more than 20 mins to connect to the configmgr from toolkit.
It is a known defect in fixpack2, for configmgr taking longer times, we have a fix for this along with the other fix for high CPU usage above our fixpack2.
IC58241 SUMMARY:
-----------------------------------------------------------------------------------------------
BROKER TOOLKIT TAKES A LONG TIME TO CONNECT TO CONFIGURATION MANAGER
And also we have
IC57886 SUMMARY:
-----------------------------------------------------------------------------------------------
CONFIGURATION MANAGER HAS HIGH CPU USAGE FOLLOWING A DEPLOY
But still have the problem. Any help would be greatly appreciated.
We have Configmgr and broker on a single server sharing the same Queue manager and a broker on a different server with its own Queue manger. That is two brokers and a configmgr. |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Feb 12, 2009 9:56 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
I have two suggestions:
1) Apply V6.1.0.3 on the runtime. This has specific fixes to increase the connect time from the toolkit.
2) Change the Timeout preferences in the Toolkit.
Window -> Preferences -> Broker Administration -> Configuration Manager Proxy and change the three numeric values at the top.
I suggest something like 100, 100, 0 instead of 3, 1000, 1000 ...but the best values will vary depending on your environment.
(A value of 1000 for the 'base time' property effectively means that, when connecting, the Toolkit is pausing for one second for every single object in your domain. So lowering this value, but increasing the maximum number of retries means that the information should be displayed a lot more quickly, particularly on larger domains.) |
|
| Back to top |
|
|
| bloomy |
| Posted: Thu Feb 12, 2009 11:30 am Post subject: Thanks for the reply mqmatt |
|
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
Thanks for both the suggestions.
| Quote: |
1) Apply V6.1.0.3 on the runtime. This has specific fixes to increase the connect time from the toolkit.
|
We have fixes that are known defects in fixpack 2, and which might lead to this problem. Anyways we are planning to roll out fixpack 3 in june 09.
| Quote: |
2) Change the Timeout preferences in the Toolkit.
|
I tried changing the settings you mentioned in my toolkit but of no use. i dont think this is a problem with toolkit, but with the configmgr itself, whenever we try to connect to the configmgr there are messages on SYSTEM.BROKER.CONFIG.QUEUE for almost 30 mins. I dont think it is a normal behaviour for it to take so long for messages to get processed.
Has anyone else come across same situation |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
