| Author |
Message
|
| algowu |
 Posted: Fri Feb 10, 2006 9:52 pm Post subject: JMS can't connect to MQ queue manager |
 |
|
Newbie
Joined: 10 Feb 2006
Posts: 3
|
 I got this weird problem and hope somebody can help me:
we developped a software that using JMS to communicate with IBM MQ5.3 server using mqcontext.jar (on solaris). It has been working fine until we changed channel MCAUSER attribute from blank to a valid unix user MCAUSER(devuser).
The error code we got is 2035. If we switch MCAUSER back to blank or mqm, our software works fine again. If we add "devuser" to mqm group, it also works.
So, is it true that MCAUSER must belongs to mqm group in order for MQ to work with JMS?
Another weird problem is that we can't access alias queue from our jms application, even we use MCAUSER(mqm) in channel definition.
Peter |
|
| Back to top |
|
 |
| wschutz |
| Posted: Sat Feb 11, 2006 4:02 am Post subject: Re: JMS can't connect to MQ queue manager |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| algowu wrote: |
I got this weird problem and hope somebody can help me:
we developped a software that using JMS to communicate with IBM MQ5.3 server using mqcontext.jar (on solaris). It has been working fine until we changed channel MCAUSER attribute from blank to a valid unix user MCAUSER(devuser).
The error code we got is 2035. If we switch MCAUSER back to blank or mqm, our software works fine again. If we add "devuser" to mqm group, it also works.
So, is it true that MCAUSER must belongs to mqm group in order for MQ to work with JMS?
|
No, but devuser must be authorized via setmqaut to both connect to the qmgr and use the queue.
| algowu wrote: |
:
Another weird problem is that we can't access alias queue from our jms application, even we use MCAUSER(mqm) in channel definition.
Peter |
What's the error?
_________________
-wayne |
|
| Back to top |
|
|
| algowu |
| Posted: Sat Feb 11, 2006 9:48 pm Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 3
|
We granted all possible permissions for "devuser" to use qmgr and target queue, it still does not work. do we have to grant "devuser" permissiones to access all queues defined under the qmgr? we got the feeling that the error(2035) come from other queues which devuser does not have permission to access.
About the alias queue, we simly got messages says that the alias queue does not exists. |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Feb 11, 2006 11:28 pm Post subject: Re: JMS can't connect to MQ queue manager |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| wschutz wrote: |
| No, but devuser must be authorized via setmqaut to both connect to the qmgr and use the queue. |
I am kind of nervous to disagree with wschutz, because he couldn't be wrong. But I think the user must be from mqm group.
| Quote: |
| About the alias queue, we simly got messages says that the alias queue does not exists. |
Check the case
If it is clustered queue, issure the right cluster displaying commands to verify that the queue is really showing up. |
|
| Back to top |
|
|
| algowu |
| Posted: Sun Feb 12, 2006 8:16 am Post subject: Re: JMS can't connect to MQ queue manager |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 3
|
| vennela wrote: |
| wschutz wrote: |
| No, but devuser must be authorized via setmqaut to both connect to the qmgr and use the queue. |
I am kind of nervous to disagree with wschutz, because he couldn't be wrong. But I think the user must be from mqm group.
I got the same feeling, it seems that JMS (we are using mqcontext.jar from ibm) trying to find out entire list of queues served by the qmanager which is not possible if you are not part of mqm group.
Is there a document from ibm that confirm this?
| Quote: |
| About the alias queue, we simly got messages says that the alias queue does not exists. |
Check the case
If it is clustered queue, issure the right cluster displaying commands to verify that the queue is really showing up. |
|
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Feb 12, 2006 9:31 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You can see why you're getting 2035 by turning on authority events:
| Code: |
runmqsc QMGR
alter qmgr AUTHOREV(enabled) |
and then look at the event message generated in SYSTEM.ADMIN.QMGR.EVENT.
(I've used ms0k "evmon" to look at these messages in the past, but it doesn't seem to work well with MQ v6, it might still work ok with v5.3)
_________________
-wayne |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Feb 12, 2006 9:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| I am kind of nervous to disagree with wschutz, because he couldn't be wrong. But I think the user must be from mqm group. |
Why should that be? As far as MQ is concerned, its just another MQ client connection, isn't it?
_________________
-wayne |
|
| Back to top |
|
|
| wschutz |
| Posted: Sun Feb 12, 2006 1:14 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Actually, use the evmon from supportpac MO01, it seems to work properly for authorization messages (whereas ms0k seems to be broke here).
_________________
-wayne |
|
| Back to top |
|
|
|
|
