| Author |
Message
|
| Vitor |
 Posted: Fri Sep 19, 2014 5:33 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hughson wrote: |
| Vitor wrote: |
| being beaten with a rolled up newspaper is inspirational |
Everyone take note  |
So can I hope you'll be bringing a rolled up newspaper to MQTC, and will find a few quiet moments to inspire me????
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Sep 19, 2014 5:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| hughson wrote: |
| Vitor wrote: |
| being beaten with a rolled up newspaper is inspirational |
Everyone take note |
Look, what a man and his wife do in the privacy... |
This email thread has been forwarded. I look forward to watching from a safe distance (i.e. via CCTV from the next state) the next time you meet Holly.
| mqjeff wrote: |
| Our chief weapon is surpise! And a rolled up newspaper. |
I wasn't expecting that....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Sep 19, 2014 6:08 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| Vitor wrote: |
| hughson wrote: |
| Vitor wrote: |
| being beaten with a rolled up newspaper is inspirational |
Everyone take note |
So can I hope you'll be bringing a rolled up newspaper to MQTC, and will find a few quiet moments to inspire me???? |
I couldn't possibly comment
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| kishvardhan |
| Posted: Fri Sep 19, 2014 9:38 am Post subject: |
|
|
Newbie
Joined: 17 Sep 2014
Posts: 8
|
Hello All,
small clarification.
How application will interact with QMGR?
Is using svrconn channel?
Correct me if I'm wrong..!!
one more thing..
How to check count of process that connecting application?
for example: In MAXHANDLE in qmgr(2048)
how to check all those 2048 was consumed by which PIDs? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 19, 2014 9:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kishvardhan wrote: |
| How application will interact with QMGR? |
However it wants.
| kishvardhan wrote: |
| Is using svrconn channel? |
It might well be, it probably it but doesn't have to be
| kishvardhan wrote: |
| Correct me if I'm wrong..!! |
You're not wrong, but you shouldn't make the assumption that it's doing that. It's just most likely to be doing that.
| kishvardhan wrote: |
| How to check count of process that connecting application? |
See earlier in this post
| kishvardhan wrote: |
for example: In MAXHANDLE in qmgr(2048)
how to check all those 2048 was consumed by which PIDs? |
As I said above, that's not 2048 handles in the queue manager; that's 2048 handles per application. So if you have 10 applications running (over a SVRCONN or not) then potentially you could have 20,480 open handles in the queue manager. And very little memory left.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kishvardhan |
| Posted: Fri Sep 19, 2014 10:08 am Post subject: |
|
|
Newbie
Joined: 17 Sep 2014
Posts: 8
|
but then why getting error like 2017...
forget about recent upgrade.. Even I got confusion about that.
Actually our application talks to MQ via API.
API got this 2017 error. Why those error getting. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 19, 2014 10:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kishvardhan wrote: |
| API got this 2017 error. Why those error getting. |
The API not got this 2017 error. The API is returning a 2017 issued by the queue manager to the application when called by the application. The API is not running code, it's a set of librairies.
The API is returning this 2017 issued by the queue manager because the application in question has exceeded the number of open handles it's allowed to use as defined by the MAXHANDS attribute of the queue manager. Any application that's using that number of handles is most likely doing so because it's not closing unneeded handles.
No matter how many times you ask this, the answer will come back the same. No matter how many times you ask this, the answer will be it's an application problem that can't be fixed simply by changing the queue manager configuration. If you keep increasing MAXHANDS, the most likely scenario is it will be a longer period of time before you start seeing 2017 codes.
So go to the people who develop the application(s) that are getting 2017 errors and tell them the solution to their problem with 2017 errors is to fix their code so it doesn't result in 2017 errors.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Sep 19, 2014 11:14 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The problem could be completely unrelated to the MQ upgrade, and the app could really be unchanged. We had this once - some database errors started causing the app to go down an error path in its logic that was written poorly. It didn't close the queue even though the app went down an abnormal path. The next transaction that came thru caused a new MQOPEN to be issued. That got used until the next error. And there's another handle "leak". Repeat until the next MQOPEN call returns 2017.
Nothing changed in MQ or the app code, but all of the sudden 2017s. The problem was the app was coded wrong from DAY ONE. It took a couple of years to expose the cheesy path of code.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 19, 2014 12:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| Nothing changed in MQ or the app code, but all of the sudden 2017s. The problem was the app was coded wrong from DAY ONE. It took a couple of years to expose the cheesy path of code. |
Exactly the point I was making earlier after inspiration struck me across the nose; if the application (in my use case) had been using the ActiveX control then it could be failing post upgrade against a newer software level.
The important point (and you make it well) is that the app doesn't need to have changed recently to have a bug in it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 19, 2014 2:23 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
If it isn't hardware (that changed), and it isn't software, then the only thing left is data.
_________________
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 |
|
|
|
|
