| Author |
Message
|
| manus |
 Posted: Mon Apr 02, 2012 12:08 am Post subject: Handles getting dropped on the Q.IPPROCS(0) |
 |
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
Hi all,
I am facing a very different issue,While i am able to put message on the Local Q,but the listener does not picks up the messages sometimes it does and sometimes the Q starts piling up,whenevr a put happens on the Q.When i monitored the logs,i observerd that after a certain amount of time,the parameter IPPROCS(1)-----> CHANGES TO IPPROCS(0),and when i further read,i got to know that IPPROCS(0) means that handles are getting dropped on the Queue due to which the messages are getting piled up on that Queue,instead the Listener reading each message.Can someone please bail me out of this situation. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 02, 2012 4:12 am Post subject: Re: Handles getting dropped on the Q.IPPROCS(0) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| manus wrote: |
| I am facing a very different issue[ |
Then why post on this by your own adminssion unrelated thread? 
| manus wrote: |
| Can someone please bail me out of this situation. |
Your listener code has a bug in it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Apr 02, 2012 4:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Does it go back for more, after getting and processing the first message?
What happens when the queue is empty (RC 2033) - does it terminate?
Does it use MQGET with MQGMO_WAIT ? |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 10:55 am Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
| Even while the Q is empty it terminates,If the listener had issues,it would never pick up a single message.It picks up the message when the IPPROCS(1),and stops picking the message when IPPROCS(0).i doubt if this is a listener issue.we are using default message listener container for jms. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 02, 2012 11:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
IPPROCS is a *reported* number. It's not a *causative* number.
I.e. it's not that the listener stops working BECAUSE IPPRROCS goes to 0.
It's that IPPROCS goes to zero BECAUSE the listener stopped working.
What, exactly, is the listener in question? You talk about a qlocal, so I'm guessing it's not the MQ channel listener. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2012 11:40 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| manus wrote: |
| It picks up the message when the IPPROCS(1),and stops picking the message when IPPROCS(0). |
Yes, because when it's working it has the queue connection open (IPPROCS(1)) and when it fails / stops the connection closes (IPPROCS(0).
| manus wrote: |
| i doubt if this is a listener issue.we are using default message listener container for jms. |
The container's probably fine. What you're put in the container has an issue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 11:54 am Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
yeah we are dropping the message on to the local Q.
But since we have different environments for diffenet phases of testing.the same listener does not have any issue in the earlier environment.
Can someone please suggest me what changes do i need to make to my listener code. |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 11:56 am Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
| or since we have the listener binded to the Q through the jndi binding,is it possible that the binding somehow is not properly done due to which the handles drop. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2012 12:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| manus wrote: |
| or since we have the listener binded to the Q through the jndi binding,is it possible that the binding somehow is not properly done due to which the handles drop. |
No. If the JNDI was done wrong you wouldn't be able to get any messages.
Also you need to understand this - the IPPROCS is not showing you the handles "dropping". It's showing if your application is actively connected to the queue and reading messages. All that the count going from 1 to 0 is showing is that your application is no longer reading the queue.
So, and this is the key bit, it's not that your application is failing to work because IPPROCS has dropped to 0. IPPORCS has dropped to 0 because your application has failed to work.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2012 12:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Armed with this knowledge (assuming you've absorbed this knowledge) your next step should be to determine why this listener isn't picking up messages; what excuse does it give? If it's not running, why isn't it running? If it's running, why is the queue showing closed for input? What's in the application logs? If you have JMS errors, what does the linked exception tell you about the problem?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 1:03 pm Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
Thanks for all ur help till now,now my question is the same listener is not functioning irregularly in the lower environment and also we dont have any jms errors in our logs.Thats why also we are confused.and howz this happening that listener is able to pick up mesage when we recycle the jvm,all the messahges that are stuck on the queue get flushed through to the listener and it processes it efficiently,and then at run time also it behaves properly till some time,but after that time again the some thing of piling starts happeninh....i am confused:( |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 02, 2012 3:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| manus wrote: |
| my question is the same listener is not functioning irregularly in the lower environment and also we dont have any jms errors in our logs.Thats why also we are confused.and howz this happening that listener is able to pick up mesage when we recycle the jvm,all the messahges that are stuck on the queue get flushed through to the listener and it processes it efficiently,and then at run time also it behaves properly till some time,but after that time again the some thing of piling starts happeninh....i am confused:( |
Is this piece of Java running inside WAS or similar? Possibly in a WAS or similar that's not configured the same as in lower environments? That is causing your app to hang / crash / fail?
If there's a problem with WMQ and nothing in the log there's a problem with your logging.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 4:17 pm Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
| Yes the app is running on WAS6.1.And all the configurations are done on the app server side. |
|
| Back to top |
|
|
| manus |
| Posted: Mon Apr 02, 2012 4:47 pm Post subject: |
|
|
Newbie
Joined: 01 Apr 2012
Posts: 8
|
Hi Grand Poobah,
As you said "All that the count going from 1 to 0 is showing is that your application is no longer reading the queue. "
The thing that basically binds the Litener app to the Q is the jndi binding and the spp server env settings.May be there is something missing there.
Also i feel if the listener pojo was probelematic,it would have never picked up any Messages at all from the Q...rite
Do you have any suggestions on this |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 02, 2012 8:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
O.K. we are talking JMS so your listener is an instance of MessageListener.
Did you also define an instance of ExceptionListener to be put on the connection?
Furthermore how did you define the handling of poison messages?
This could be entirely due to the environment. If for whatever reason the resource needed to process the message(s) is not available, and the poison message handling is set in the "right" manner, your message listener can stop delivering messages (would be the case with message affinity) until you have resolved the resource issue and restarted the MDB service...(at which point ops usually says its easier to bounce the jvm)...
Moving to more appropriate forum
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
