| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC 2035 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bravo |
 Posted: Thu Feb 26, 2009 11:34 pm Post subject: MQRC 2035 |
 |
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Hi All,
JMS application trying to communicate MQ 6 on AIX using client connection giving 2035. I have set the mcauser as (mdi).
I have enable QMGR event and got some messages in QMGR.EVENT queue. Read the messages using evmon,
Queue Manager event: CompCode(WARNING)
Reason = MQRC_NOT_AUTHORIZED
parameter count is 8
MQCA_Q_MGR_NAME INTQMGR
MQIACF_REASON_QUALIFIER 2 (X'2')
MQCA_Q_NAME MDI.ORDERS05.OUT
MQIACF_OPEN_OPTIONS 8208 (X'2010')
MQCACF_USER_IDENTIFIER mdi
MQIA_APPL_TYPE = MQAT_AIX
MQCACF_APPL_NAME WebSphere MQ Client for Java
MQCACF_OBJECT_Q_MGR_NAME DEVQMGR
We have 2 Qmgrs on the same box DEVQMGR on port 1414 and INTQMGR on port 1416. JMS appl was connected before to DEVQMGR and it was working fine. Now we want to connect to the new INTQMGR and we are getting 2035. I have set OAM same for both Queue Managers.
Please let me know what I'm missing.
_________________
Bravo |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Feb 28, 2009 3:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you have the same setmqaut scripts on both qmgrs, try running refresh security on the one that is not working. Make sure the users(mcauser) have the right group membership. Anything else will probably require a PMR. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Bravo |
| Posted: Mon Mar 02, 2009 9:28 am Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Thanks for your response fjb_saper.
I can see from the event message,
MQCA_Q_MGR_NAME INTQMGR is different than MQCACF_OBJECT_Q_MGR_NAME DEVQMGR .
INTQMGR is the new QM on port 1420 which I'm trying to connect.
DEVQMGR is old QM and client connection works fine on this.
Do you have any inputs why the old QM is showing in QM Event msg?.
_________________
Bravo |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Mar 03, 2009 12:58 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
I would run the commands
| Code: |
amqoamd -s -m INTQMGR
amqoamd -s -m INTQMGR |
and compare the output. You should also - as fjb_saper suggested - run the command
| Code: |
| refresh security(*) |
on both QMgrs.
You may enable or disable events on a QMgr. Default is "DISABLE", so if somebody changed the old QMgr and you created a new from scratch, you could see events on the old one, but not on the new one.
Some tools - e. g. Tivoli Monitoring - also switch on monitoring events.
_________________
Regards
Hubert |
|
| 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
|
|
|
|
