| Author |
Message
|
| Thomasb |
 Posted: Thu Sep 06, 2007 6:50 am Post subject: QM name not found |
 |
|
Novice
Joined: 07 Oct 2002
Posts: 15
Location: Sundsvall, Sweden
|
Have a QM uppgraded from ver 5.3 to 6.0 on Windows server 2003 . It has been working well for about 8 months after the upgrade.
Last week the machine was rebooted and after that I can't make client connections to my QM. There are two other QM:s on the same machine (created after the upgrade to version 6.0) and they work fine.
DSPMQ reports the QM is running
With RUNMQSC I can inspect all objects
AMQSPUT can connect
AMQSPUTC can't (2058)
So I guess there is something wrong with the listener (?). The listener is configured with port 1414.
Is this problem (and a way of handling with it) know to anyone of you?
Cheers
Thomas B |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Sep 06, 2007 6:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
The problem is well known. The problem is that you haven't performed any real diagnostics.
The way of handling it is to follow the guidelines in the documentation on how to troubleshoot WebSphere MQ.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 06, 2007 6:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If there was a listener problem I'd have expected a 2059. A 2058 indicates that the queue manager is not identified to the client at all, i.e not in the client table or similar.
Check that the table is where you expect & the environment variables have not been reset by the reboot.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 06, 2007 7:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A 2058 could also indicate that the wrong listener port was used - i.e. the wrong queue manager was connected to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 06, 2007 7:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| A 2058 could also indicate that the wrong listener port was used - i.e. the wrong queue manager was connected to. |
Doh! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Thu Sep 27, 2007 1:09 am Post subject: |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
try starting the queue manager using
| Quote: |
| strmqm -c <Qmgr Name> |
and then connect
_________________
Regards
Kiran |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Sep 27, 2007 5:34 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| kiran_raghunam wrote: |
try starting the queue manager using
| Quote: |
| strmqm -c <Qmgr Name> |
and then connect |
That can't help a 2058 problem. It might solve some other unrelated problem, but not a client's 2058.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
