| Author |
Message
|
| harsha8127 |
 Posted: Sun Apr 24, 2016 9:57 pm Post subject: MQOPEN ended with reson code 000002017 |
 |
|
Acolyte
Joined: 25 Nov 2013
Posts: 72
|
Hi Docs,
I am using WebSphere MQ ver 6.0.2.12 in AS400 server with ver V6R1. we are using MQ between BIZTALK and LIFEASIA for receipt creation and online transaction. Last weekend due to some reasons the connection between MQ and target application has been broken.
After two day when we saw this the input queue has depth 450 (requests for transactions and receipt). And when we made a connection back after processing two messages the connection is getting broken again. And we are getting the error "MQOPEN ended with reson code 000002017" .
I have studies many docs ''IY85202: 2017 MQRC_HANDLE_NOT_AVAILABLE is reported in WMQ at service levels 6.0.1.0 and 6.0.1.1" but did not get any info or i did not understood anything from them.
Did anyone came across this type of problem if so please help.  |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Apr 25, 2016 3:55 am Post subject: Re: MQOPEN ended with reson code 000002017 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| harsha8127 wrote: |
| MQ ver 6.0.2.12 in AS400 server with ver V6R1. |
Upgrade or get a new job.
Otherwise, are you using threads?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| harsha8127 |
| Posted: Tue Apr 26, 2016 10:15 pm Post subject: Re: MQOPEN ended with reson code 000002017 |
|
|
Acolyte
Joined: 25 Nov 2013
Posts: 72
|
| mqjeff wrote: |
Upgrade or get a new job.
Otherwise, are you using threads? |
Very thanks for your suggestion, as a software engineer/ MQ admin i also know that we need a up gradation. But i am not the chair person to decide for up gradation. Our client is not ready for up gradation now.
And at the same time we want to resolve the issue.
If anyone has come across these type of issue please help me |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Apr 26, 2016 10:33 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Have you done some of the basic detective work ? What are the IPPROCS and OPPROCS for the various queues used by the application? Are they reasonable ? What is the value of MAXHANDS of your Queue Manager ?
If you have run out of handles for a task then it suggests that either
- The application has a bug where by it is not closing handles (either because it forgets about them or is caching)
- The system has been configured to be too restrictive and that this application is not allowed as many as it needs
Unfortunately MQ V6 is pretty old. I can't remember when the command was introduced but you probably want to issue 'DIS CONN(*) TYPE(HANDLE)' and see whether your application is behaving itself.
Hope this helps,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed Apr 27, 2016 5:09 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
This approach is not for everyone (it is technical), but I would prefer using an MQ API trace to debug an issue like you reported. There is also the MH06 supportpac that has a mqtrcfrmt tool that *might* be able to help format things like the MQ data structures (e.g. MD, OD, etc.) in a v6 AS400 trace with its "-o unix" option. I have never seen an AS400 trace, but the fact that the traces use dspmqtrc to format them makes me think that it might be following the "unix" style of tracing.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
