| Author |
Message
|
| andy840920 |
 Posted: Thu May 10, 2007 3:04 am Post subject: why sometimes MQCONNX ended with 2059 |
 |
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| QMgr name and Queue name all are correct. Why sometimes MQCONNX ended with 2059? my application are multi-processes concurrency. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 10, 2007 3:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Search the forum for 2059. It is one of the most common reason codes, for reasons which may have nothing to do with your code or indeed your configuration and has been the subject of much, much discussion.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy840920 |
| Posted: Thu May 10, 2007 3:16 am Post subject: |
|
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| Vitor wrote: |
| Search the forum for 2059. It is one of the most common reason codes, for reasons which may have nothing to do with your code or indeed your configuration and has been the subject of much, much discussion. |
thanks..
i search 2059 but can't get the answer, i think the reason relate with my application(much concurrency process). and my queue created by "def ql(PH2WEB) maxdepth(10000) defpsist(yes) replace" script. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 10, 2007 3:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It's not a queue error (as you will have determined from your reading) - it's a connection error at the queue manager level.
What your code could be doing is running out of connections, though I would have expected a different code for that. Be sure that your application has control over the number of concurrent connections it has open, and closes them when it's finished with them. Make sure the max connections is set high enough for normal use of your application.
Or use some kind of application server solution with connection pooling.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy840920 |
| Posted: Thu May 10, 2007 6:48 am Post subject: |
|
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| you said set MAXACTIVECHANNELS argument in qm.ini. but my application is not operate by channels, it's a local queue. so, set this argument yet? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 10, 2007 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| andy840920 wrote: |
| you said set MAXACTIVECHANNELS argument in qm.ini. but my application is not operate by channels, it's a local queue. so, set this argument yet? |
If you're getting a 2059 & using MQCONNX, you're using a client connection, which is established over a channel. Granted if the queue is hosted by a queue manager on the same box as your application there's not much network in the channel, but it is a channel.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 10, 2007 1:33 pm Post subject: |
|
|
Guest
|
|
| Back to top |
|
|
|
|
