| Author |
Message
|
| mqmike |
 Posted: Wed Mar 21, 2007 8:38 am Post subject: MQJE001: An MQException occurred: Reason 2058 |
 |
|
Acolyte
Joined: 09 Jul 2004
Posts: 63
|
MQ6.0.2 on AIX 5.3. Application is a 3rd party one that runs under WAS, it has its own MQ config file.
We have two QMs on the server but we get the above error when trying to connect to one of them and not the other using bindings. The QM name (and queue names) is (are) correct in both instances and the application is eaxctly the same.
Application runs under 'was' user id which is part of 'mqm'. Refresh security has been done. To get this working in the short term I've had to change the config to a svrconn channel with 'mqm' as the mcauser id. Without this it still fails in client mode with 2009 errors. Nothing in the MQ error logs or on the event qs.
Any ideas? |
|
| Back to top |
|
 |
| Toronto_MQ |
| Posted: Wed Mar 21, 2007 10:54 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Since it works with 'mqm' as the MCAUSER then chances are it's an authority issue, which I think you've already figured out.
If it is indeed an authority issue (are you sure you're not receiving a 2035 somewhere??), then turn on Authority Events at the queue manager level and try your test again, then have a look at the SYSTEM.ADMIN.QMGR.EVENT queue to see what's failing. You can either dissect the messages yourself, or I would reccommend using supportpac MS0P to do the work for you (assuming you can admin the qmgr from the explorer).
Then again, the header of this posting has 2058 in it. So I may be WAY off base.
Cheers
Steve |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 21, 2007 1:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Some clarification please:
Is the problem a 2058 (typical of a binding problem), a 2009 (typical of a client connection) or a security issue?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmike |
| Posted: Thu Mar 22, 2007 2:00 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2004
Posts: 63
|
2058 with bindings
2009 when using svrconn with no hard configured mcauser
no sign of 2035s and nothing in the event queues |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 22, 2007 2:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
A 2058 from a bindings connection typically means misspelt queue manager name (where misspelt includes wrong case of course!) 
Though I expect you've checked that already.
2009 can be caused by a wide variety of things (as a search through the forum will reveal). Is there any SSL involved here, which could be causing the client connection to be refused with the wrong credentials?
(Bit of a straw clutch there....)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmike |
| Posted: Thu Mar 22, 2007 2:29 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2004
Posts: 63
|
No SSL used.
To be honest I'm more concerned with the 2058. I guess the 2009 could have happened for a number of reasons.
Very odd. I've got a copy of the application's config file and the QM name is correct. |
|
| Back to top |
|
|
|
|
