| Author |
Message
|
| bin_moh |
 Posted: Thu Mar 10, 2011 9:50 pm Post subject: 2009,2035 MQ Errors |
 |
|
Newbie
Joined: 10 Mar 2011
Posts: 8
|
Hi,
I'm trying to connect to a qmgr which is on AIX from a Windows client.
I'm able to telnet to the port of the qmgr from the client. but once I try to connec thru the java program used to send and resieve messages from the qmgr; its throwing errors such as:
MQJE001: An MQException occurred: Completion Code 2, Reason 2035
MQJE036: Queue manager rejected connection attempt
MQJE001: Completion Code 2, Reason 2035
Reason Code2035
Press any key to continue . . .
MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
MQJE001: Completion Code 2, Reason 2009
Reason Code2009
Press any key to continue . . .
The qmgr on the AIX box is running well along with its listener. (MQ 5.3)
checked for the reson codes in google; but still not able to connect............ |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Mar 10, 2011 11:08 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
So you checked for the reason codes, presumably in the order in which you go them, did not correct their cause, and you are surprised that you still cannot connect? The problem is obvious and easily resolvable with reference to the manuals.
And that version of WMQ is way out of support even for a sand-box environment.
_________________
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 |
|
|
| bruce2359 |
| Posted: Fri Mar 11, 2011 6:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Go to google, type reason code 2035 in search text box, click Search.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| santnmq |
| Posted: Mon Mar 14, 2011 1:46 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
| provide the required authorization to the user id which you are using to run this code. this will resolve your 2035 problem. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Mar 14, 2011 2:38 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| santnmq wrote: |
| provide the required authorization to the user id which you are using to run this code. this will resolve your 2035 problem. |
Shock, horror, you gave away the answer without letting the OP work out such as simple problem for themselves, even after exerk and bruce gave hints ! 
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 14, 2011 2:58 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gbaddeley wrote: |
| santnmq wrote: |
| provide the required authorization to the user id which you are using to run this code. this will resolve your 2035 problem. |
Shock, horror, you gave away the answer without letting the OP work out such as simple problem for themselves, even after exerk and bruce gave hints ! |
He/she also waited three days.
Granted, two of those were over a weekend. |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Tue Mar 15, 2011 3:16 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
the windows client which uses this particular program does have the reuired mqm group permissions. the also if says:
"Use of MQ Trigger Monitor not authorised" |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Mar 15, 2011 3:51 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| itsme_001 wrote: |
| the windows client which uses this particular program does have the reuired mqm group permissions. |
Wrong! Think again about what you have just said, and the consequences of 'fixing' the problem if you focus on it being mqm permissions.
_________________
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 |
|
|
| itsme_001 |
| Posted: Tue Mar 15, 2011 4:40 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
| Sorry I didn't get you!!!!!!!!!!!!!!! |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Mar 15, 2011 4:48 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| itsme_001 wrote: |
| Sorry I didn't get you!!!!!!!!!!!!!!! |
Then I'll rephrase the question and break it down into easily understandable parts:
1. For the Windows client to have the necessary mqm permissions on the AIX server, what must be done on the AIX server?*
2. What consequence is there for queue manager security when a userid within the mqm group is used for any queue manager operation?
*Consider the differences between userid name lengths on those platforms.
_________________
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 |
|
|
| bin_moh |
| Posted: Wed Mar 16, 2011 1:18 am Post subject: |
|
|
Newbie
Joined: 10 Mar 2011
Posts: 8
|
In the windows box the default user has been given required mqm group permissions. the problem pertains to the client box on windows; not on the AIX server.
C:\Documents and Settings\Administrator>runmqtmc -m QM -q MQ.INIQ
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
Use of WebSphere MQ trigger monitor not authorized.
WebSphere MQ trigger monitor ended.
Here's the error msg |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 16, 2011 1:30 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Interesting... itsme_001 posted this:
| Quote: |
| the windows client which uses this particular program does have the reuired mqm group permissions. the also if says: "Use of MQ Trigger Monitor not authorised" |
And bin_moh just posted this:
| Quote: |
| Use of WebSphere MQ trigger monitor not authorized. |
Are you two the same person, or work together?
Try checking the Event Viewer logs.
_________________
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 |
|
|
| bin_moh |
| Posted: Wed Mar 16, 2011 2:24 am Post subject: |
|
|
Newbie
Joined: 10 Mar 2011
Posts: 8
|
| There is nothing available in eventvwr logs pertaining to Websphere MQ. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 16, 2011 2:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bin_moh wrote: |
| There is nothing available in eventvwr logs pertaining to Websphere MQ. |
And what about the user?
_________________
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 |
|
|
| bin_moh |
| Posted: Wed Mar 16, 2011 2:46 am Post subject: |
|
|
Newbie
Joined: 10 Mar 2011
Posts: 8
|
| exerk wrote: |
And what about the user? |
The user is an Administrator user. Its already added to the <mqm> group |
|
| Back to top |
|
|
|
|
