Author |
Message
|
Bni |
Posted: Fri Dec 01, 2006 7:55 am Post subject: Got error message MQCONN Failed, reason code 2035 |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
MQ manager is running fine when we saw this error message. It is from an executable from application side triggered by MQ( run by mqm id). What this executable does is to access one of the queues( let's say queue A) and logged an error message from the log file. It has been running for years and we did not make any changes in MQ side and certainly there is are code changes for that executable. I can see that messages are piling up for queue A while we don't have any issues for the other queues. We recycled mq serveral times and we still saw the problem. After several hours, the problem suddenly went away. Any ideas what might be cause?
Appreciate your inputs.
Thanks |
|
Back to top |
|
 |
kevinf2349 |
Posted: Fri Dec 01, 2006 9:31 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
What changes were made to the security system? |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Dec 01, 2006 11:15 am Post subject: |
|
|
Guest
|
Reason Code 2035 us a secuity violation. So, the application did an MQCONNECT to make contact with the qmgr. That is where the violation occured.
So, look at who was signed on to run the program. Make sure that the userid is authorized to MQCONN in the domain security. |
|
Back to top |
|
 |
Bni |
Posted: Fri Dec 01, 2006 3:16 pm Post subject: The executable program |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
is triggered by MQ whenever there is a message in the queue, so the user id to run this program is always mqm( that has been the case from day 1). We don't know if there are any security changes made in the system. But certainly we did not make any changes and there are no code changes either. The weirdest thing is that this problem went away several hours later after it appeared. We never saw this issue in the past years! |
|
Back to top |
|
 |
kevinf2349 |
Posted: Fri Dec 01, 2006 7:20 pm Post subject: Re: The executable program |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Bni wrote: |
We don't know if there are any security changes made in the system. |
Check the logs. My guess is someone changed a security setting somewhere |
|
Back to top |
|
 |
Bni |
Posted: Mon Dec 04, 2006 9:50 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
Which log are you referring to? The system logs or for MQ error log? |
|
Back to top |
|
 |
kevinf2349 |
Posted: Mon Dec 04, 2006 10:15 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
The Event logs under the event viewer.
The MQ logs probably won't show anything, but if someone has been tinkering with security it should be in the event logs (unless it isn't a windows system of course, or they have deleted them). |
|
Back to top |
|
 |
killer |
Posted: Mon Dec 04, 2006 10:46 am Post subject: |
|
|
 Apprentice
Joined: 06 Jul 2006 Posts: 35
|
Without making change in Security it's not possible to get 2035 error,if it's running for years as u told.
Apllication had lost it's authority to make connection with Qmgr.So you get error 2035.
As suggestion ,please check the security setting once. |
|
Back to top |
|
 |
Bni |
Posted: Thu Dec 07, 2006 8:21 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
Appreciate all the answers and suggestions. Ask one final question, where is the security located? and where is the event log? We are using MQ5.0. The only log files I know is in /var/mqm/errors/log(where FDC files are located); and in /var/mqm/qmgrs/qmanager/errors/log. I am quite new to MQ. Thank you very much |
|
Back to top |
|
 |
Vitor |
Posted: Thu Dec 07, 2006 8:26 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Bni wrote: |
We are using MQ5.0. |
Upgrade. Soon. That's very old.
You view security via the command line interface.
Event log assumes you're running on Windows, while the path you've quoted implies Unix where the logs are where you claim. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Dec 07, 2006 8:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You should not be using MQ v5.0.
The minimum you should be using is MQ v5.3.
kevinf2349 was assuming you were using Windows when he said "event log". _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Bni |
Posted: Thu Dec 07, 2006 11:41 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
Thank you very much. We all know 5.0 is very old and it is very dangerous, but that is the way we are now. Appreciate all your help. |
|
Back to top |
|
 |
Bni |
Posted: Mon Jan 01, 2007 2:57 am Post subject: We just got this 2035 alert around 3:51AM US central today. |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
I really have no idea to troubleshoot this problem. As a support person, I certainly did not make any changes. There are no fdc report generated, and there are no obvious error messages related to this in MQ log files. Anybody can offer me more directions on this? Thanks |
|
Back to top |
|
 |
Bni |
Posted: Mon Jan 01, 2007 3:38 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2006 Posts: 29
|
Anybody can help me to issue a command on command line to check the MQ security setting in HP system? We are using MQ 5.0. Please help. Thanks |
|
Back to top |
|
 |
JosephGramig |
Posted: Mon Jan 01, 2007 5:14 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
Well, you need to consult with your SA (system administrator) and see if any HPUX patches have been applied.
If this is the case, you are now have an incompatible system. This might or might not be resolved by regressing the patches. You probably only have one choice and that is to upgrade.
Good luck! _________________ Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
Back to top |
|
 |
|