| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ4036 error MQSeries |
« View previous topic :: View next topic » |
| Author |
Message
|
| 4joey1 |
 Posted: Sun Apr 17, 2011 4:04 am Post subject: AMQ4036 error MQSeries |
 |
|
Newbie
Joined: 17 Apr 2011
Posts: 1
|
Hallo!I am totally new to MQSeries.I installed it Websphere 7 ON HP-UX Itanium as
I created a queue manager called Queue1 as below
crtmqm -q Queue1
Through MQSC commands,I created a local queue local.queue as below
define qlocal (local.queue) usage (xmitq)
I then created a listener and started it via commands below
define listener (listener1) trptype (tcp) control (Queue1) port (1414)
start listener (listener1)
Next,I created a server and receiver connection channel called test.channel as below
DEFINE CHANNEL(test.channel) CHLTYPE(CLNTCONN) TRPTYPE(TCP) CONNAME(10.1.0.9) QMNAME(Queue1)
DEFINE CHANNEL(test.channel) CHLTYPE(SVRCONN) TRPTYPE(TCP)
From have a Windows 7 machine,I have been trying to connect to the MQ Series in HP-UX via MQExplorer via the queue manager,channel name,IP address and port stated above but I get the error below
AMQ4036:The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object.
I had also tried creating a channel,queue manager from JMSAdmin by connecting to JMSAdmin as below
./JMSAdmin -v -cfg JMSAdmin.config
InitCtx> define xaqcf(local.queue) qmgr(Queue1) tran(client) host(localhost) port(1414)
But this had no effect.
How do I resolve this?
Thanks. |
|
| Back to top |
|
 |
| exerk |
| Posted: Sun Apr 17, 2011 4:40 am Post subject: Re: AMQ4036 error MQSeries |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| 4joey1 wrote: |
I created a queue manager called Queue1 as below
crtmqm -q Queue1 |
Best practice is not to use mixed-case names for queue managers and/or their objects - UPPER case is suggested for use everywhere as a standard. You should also review whether you do want a queue manager to be the default queue manager (-q switch).
| 4joey1 wrote: |
Through MQSC commands,I created a local queue local.queue as below
define qlocal (local.queue) usage (xmitq) |
The queue manager will wrap case to upper case unless you enclose the string inside quotes. And why did you make it an XMITQ, which has a special purpose?
| 4joey1 wrote: |
I then created a listener and started it via commands below
define listener (listener1) trptype (tcp) control (Queue1) port (1414)
start listener (listener1) |
It should be CONTROL(QMGR) not the name of the queue manager, and consider that using the globally known 'default' port is not necessarily a good thing.
| 4joey1 wrote: |
Next,I created a server and receiver connection channel called test.channel as below
DEFINE CHANNEL(test.channel) CHLTYPE(CLNTCONN) TRPTYPE(TCP) CONNAME(10.1.0.9) QMNAME(Queue1)
DEFINE CHANNEL(test.channel) CHLTYPE(SVRCONN) TRPTYPE(TCP) |
My remarks in regard to case hold here too.
| 4joey1 wrote: |
From have a Windows 7 machine,I have been trying to connect to the MQ Series in HP-UX via MQExplorer via the queue manager,channel name,IP address and port stated above but I get the error below
AMQ4036:The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object. |
Time to dig into the Security manual and understand why, and bear in mind that you will not be using the channels you created.
| 4joey1 wrote: |
I had also tried creating a channel,queue manager from JMSAdmin by connecting to JMSAdmin as below
./JMSAdmin -v -cfg JMSAdmin.config
InitCtx> define xaqcf(local.queue) qmgr(Queue1) tran(client) host(localhost) port(1414)
But this had no effect. |
Why? If it won't work one way why do you think it will work another? Especially as your HP-UX server will know what localhost is in regard to itself, but your Win7 box will have a different 'idea' of what localhost is.
| 4joey1 wrote: |
| How do I resolve this? |
Easy, RTFM. The Info Centre will provide all the answers you seek so go through it (it's searchable) but if still confused, then come back and post again. Also, you would do well to read the following post:
How To Ask Questions The Smart Way
Which also contains information of use to you, especially in regard to your current 'problem'.
The Quick Beginnings manual for your platform should be the first place to start...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Apr 17, 2011 9:56 am Post subject: Re: AMQ4036 error MQSeries |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| 4joey1 wrote: |
I had also tried creating a channel,queue manager from JMSAdmin by connecting to JMSAdmin as below
./JMSAdmin -v -cfg JMSAdmin.config
InitCtx> define xaqcf(local.queue) qmgr(Queue1) tran(client) host(localhost) port(1414)
But this had no effect.
How do I resolve this?
Thanks. |
First be advised that in order to create a JNDI entry that will be usable the relevant object needs to already exist in MQ.
Second you need to review the manual about creating entries using JMSAdmin. Looks to me like you are completely confusing things.
Regardless of the localhost problem you would need:
- 2 lines to define a qmgr and a queue, 1 for each one
- to define a qmgr (client connection) a minimum of host, port AND CHANNNEL
 hit the manuals  and have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SAFraser |
| Posted: Wed Apr 20, 2011 9:06 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
And once the other problems are resolved (as mentioned by my worthy associates), you'll find that the error message is valuable:
| Quote: |
| AMQ4036:The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object. |
The thing is... MQ has a learning curve. Sometimes management will dump a big MQ assignment on a newbie and expect it to be executed in a few days. It is just not practical!
The Intercommunication manual (see the Info Centre link at the top of this page) may be helpful. |
|
| 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
|
|
|
|
