| Author |
Message
|
| tegelert |
 Posted: Sun May 05, 2013 11:04 am Post subject: set MQNOREMPOOL=1 |
 |
|
Newbie
Joined: 03 May 2013
Posts: 9
|
Setting MQNOREMPOOL=1 fixes the issue.
This was supposed to be fixed in an earlier release, but appears not.
Thanks for the help. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun May 05, 2013 11:09 am Post subject: Re: set MQNOREMPOOL=1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tegelert wrote: |
Setting MQNOREMPOOL=1 fixes the issue.
This was supposed to be fixed in an earlier release, but appears not. |
You should raise a PMR. Either it was only fixed on Solaris, or it was fixed on all platforms and the fix doesn't work on Windows. In any event, this should be fed back to IBM.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Sun May 05, 2013 12:18 pm Post subject: Re: probe ID CO000001 |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| tegelert wrote: |
| But the probe IDs match. This looks very similar to what we see. The APAR says it's only been seen on Solaris, but that doesn't seem to be a strong enough statement to say it could absolutely never occur on Windows. Maybe we should upgrade anyway. |
Even if it is the same condition, the info on that page seems to say the code fix will only clean up the reporting, not avoid the original error.
The fix is in 7.0.1.10 which is due this quarter: http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006309
Besides the FDC, look in /var/mqm/errors/AMQERR01.LOG and the qmgr error log in /var/mqm/qmgrs/QMNAME/errors for anything else that might help. |
|
| Back to top |
|
|
| pandeg |
| Posted: Tue Oct 28, 2014 10:16 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| Hi , I was going through post and found that I am also facing the same exception. I am also using MQ 7.01.9 on Red Hat Linux. I get this exception when I increase the number of thread connection with MQ server beyond certain limit using JMS client application. Please let me know if the issue mentioned in this post was resolved , so that I can also try the same. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 28, 2014 10:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| pandeg wrote: |
| Hi , I was going through post and found that I am also facing the same exception. I am also using MQ 7.01.9 on Red Hat Linux. I get this exception when I increase the number of thread connection with MQ server beyond certain limit using JMS client application. Please let me know if the issue mentioned in this post was resolved , so that I can also try the same. |
Exactly and precisely what certain limit? Have you reached max channels? Or max active channels?
_________________
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 |
|
|
| Vitor |
| Posted: Tue Oct 28, 2014 11:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| pandeg wrote: |
| Hi , I was going through post and found that I am also facing the same exception. I am also using MQ 7.01.9 on Red Hat Linux. I get this exception when I increase the number of thread connection with MQ server beyond certain limit using JMS client application. Please let me know if the issue mentioned in this post was resolved , so that I can also try the same. |
Exactly and precisely what certain limit? Have you reached max channels? Or max active channels? |
He means the problem he was given the resolution to here. Apparently he doesn't like the solution given there, and hasn't noticed the resolution given in this this thread (or doesn't like this either, and hopes to get a better one by just asking again and again).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pandeg |
| Posted: Wed Oct 29, 2014 1:33 pm Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| Sorry for repeating the same question again and again. But , I checked those links and could not replace the latest MQ jar version with the ones I am currently using. I have mentioned it in details in the same post. Could you please help in updating the latest jar. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 29, 2014 1:38 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| pandeg wrote: |
| Sorry for repeating the same question again and again. But , I checked those links and could not replace the latest MQ jar version with the ones I am currently using. I have mentioned it in details in the same post. Could you please help in updating the latest jar. |
I suspect that not answering questions you were asked will yield similar results as repeating the same question again and again.
_________________
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 |
|
|
|
|
