| Author |
Message
|
| mqmblife |
 Posted: Mon Sep 12, 2011 2:16 am Post subject: Unable to connect to Config Manager on Toolkit |
 |
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
Hi All,
I am using the Message Broker Version: 6.1.0.3. We faced a problem in connecting the configuration manager on toolkit last week, the error was "BIP0889E The MB Toolkit cannot connect to the configuration manager".
We solved this by restarting the brokers and configuration manager. It worked fine. But again now we are facing with same issue. Want to know if we can completely solve this problem. This would be a great help!!!
FYI...
Configuration Manager and Brokers are up and running....
There is no space issue....
Regards,
Venkat |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Sep 12, 2011 2:40 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What error is it reporting? The Toolkit connects as an MQ Java Client. There should be a WMQ Error associated with the problem.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqmblife |
| Posted: Mon Sep 12, 2011 3:07 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
| smdavies99 wrote: |
| What error is it reporting? The Toolkit connects as an MQ Java Client. There should be a WMQ Error associated with the problem. |
Below is the error associated with the problem,
BIP0889E The MB Toolkit cannot connect to the configuration manager.
Reason:
While the Message Broker Toolkit was able to connect the configuration manager's queue manager (XXXXXX), no response from the Configuration manager was received. This implies that the configuration manger is not running.
Ensure that the Configuration Manager is running and that it can be reached from the Message Brokers Toolkit.
If the Configuration Manager is simply running slowly, try increasing the time message brokers toolkit waits.
Regards,
Venkat |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Sep 12, 2011 3:38 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Is the listener on the target QM running?
If it is, is it running on the correct port?
If it is then do you have access to the QM at am MQ level?
If so, do you have access to the ConfigMgr (Broker ACL?)
Then if all fails, try restarting the ConfigMgr Only. Nothing else...
6.1.0.3 is pretty long in the tooth now. It might be worth thinking about upgrading to 6.1.0.9 or even to V7.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqmblife |
| Posted: Mon Sep 12, 2011 4:28 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
| smdavies99 wrote: |
Is the listener on the target QM running?
If it is, is it running on the correct port?
If it is then do you have access to the QM at am MQ level?
If so, do you have access to the ConfigMgr (Broker ACL?)
Then if all fails, try restarting the ConfigMgr Only. Nothing else...
6.1.0.3 is pretty long in the tooth now. It might be worth thinking about upgrading to 6.1.0.9 or even to V7. |
Everything is running and we have ACL entry also. We were able to connect to configuration manager by restarting it. We have done this previously also. Want to know if we have any other possibility.
Regards,
Venkat |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 12, 2011 4:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| Is the listener on the target QM running? |
If it's the same queue manager indicated here, we know it is. But perhaps it's a bit old and deaf for the Toolkit. Or is speaking Sandskrit? 
| smdavies99 wrote: |
| 6.1.0.3 is pretty long in the tooth now. It might be worth thinking about upgrading to 6.1.0.9 or even to V7. |
The site's using inetd listeners. Being 5 versions back isn't going to bother them. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 12, 2011 4:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqmblife wrote: |
| We were able to connect to configuration manager by restarting it. |
Did you restart the config manager, the config manager & it's queue manager or the box the queue manager is running on?
If the config manager's queue manager is using inetd listeners like the one in your other post, then the listener could be failing & preventing connection. That's a very, very old kind of listener & not all that great.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmblife |
| Posted: Mon Sep 12, 2011 4:58 am Post subject: |
|
|
Novice
Joined: 24 Aug 2011
Posts: 21
|
| Vitor wrote: |
| mqmblife wrote: |
| We were able to connect to configuration manager by restarting it. |
Did you restart the config manager, the config manager & it's queue manager or the box the queue manager is running on?
If the config manager's queue manager is using inetd listeners like the one in your other post, then the listener could be failing & preventing connection. That's a very, very old kind of listener & not all that great. |
Yes I have restarted the config manager not the box. Can you please let me know how to verify if the queue manager is using inetd listeners.
Regards,
Venkat |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 12, 2011 5:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqmblife wrote: |
| Can you please let me know how to verify if the queue manager is using inetd listeners. |
Same way you did on your previous thread. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
