| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error while logging In WMQI |
« View previous topic :: View next topic » |
| Author |
Message
|
| nik_iway |
 Posted: Thu Jul 21, 2005 4:41 am Post subject: Error while logging In WMQI |
 |
|
Centurion
Joined: 21 Jul 2005
Posts: 115
|
Hai everybody,
When i want to connect to my configuration manager i am getting the following error...
BIP1350E: The current operation has timed out.
One or more requests have been sent to the Configuration Manager to process the current operation, but no reply has been received for the last request sent.
Either your request has queued up behind a long-running request by another user, or the Configuration Manager has stopped. Check that it is up and running then retry the operation. Because the link to the Configuration Manager is via MQSeries, it is important to note that the original operation may have fully completed, or have partly completed, even though no reply was received in the allotted time. The results of the retried operation should indicate this, and will determine subsequent actions. For example, if a check-in operation timed out then the update may have occurred, but the object may still be locked. A subsequent check-in would then fail with a locked response. The action would then be to unlock the object.
Can anybody help me in this regard
Regards
raghav |
|
| Back to top |
|
 |
| hopsala |
| Posted: Thu Jul 21, 2005 7:52 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Either MQ error or CM (Configuration Manager) error.
The contact between you and the CM is via MQ. This means all normal MQ malfunctions apply here: You do not have proper authorities, listener is down, MQ is down, channel error etc..
Look at MQ error log(both general and per the ConfigManager QM) . If it looks ok, try seeing if any messages arrive to the CM admin queue, if you see them just standing there doing nothing it means the CM is not reading, which means it's probably down.
But naturally, first thing you should check is whether you put in the wrong connection parameters when loggin in to the control center (port, ip, qmname)... |
|
| Back to top |
|
|
| Pam |
| Posted: Thu Jul 21, 2005 9:23 pm Post subject: |
|
|
Novice
Joined: 10 Dec 2004
Posts: 11
|
I Agree with Hopsala.It is also worth checking whether the services DB2 - DB2-0 and DB2 License Server are running before invoking control center.
_________________
Pam
IBM Cert. MQ Series System Administrator
IBM Cert. WBI MB System Administrator |
|
| 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
|
|
|
|
