| Author |
Message
|
| mqjeff |
 Posted: Wed Feb 16, 2011 7:47 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Gil77 wrote: |
| exerk wrote: |
And the MDB ends, or continues running? |
The MDB should continue running. |
Whether it should or not, when it is not reading messages, DOES IT CONTINUE running? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 16, 2011 8:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| if we wait 30 minutes or longer; not make a request for 30 minutes, then an error will more likely occur (an error being where the message is ignored). if we start making requests within 30 minutes of each other, no errors will likely occur. When we restart the server, no errors will occur for a while |
So how long does the MDB run after it's processed the last message? What is setting this 30 minute timeout? Is it a deliberate timeout or something like the network closing a stale connection? Do you see any messages after 30 minutes consistent with the MDB being errored out?
Does the MDB successfully process all messages (even previously abandoned ones) after the server is restarted? What triggers the app server to start the MDB in the first place? Is the MDB actually driven by the arrival of a message or does it just come up with the app server?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 16, 2011 8:58 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| mqjeff wrote: |
Whether it should or not, when it is not reading messages, DOES IT CONTINUE running? |
Yes, as far as I can tell. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 16, 2011 9:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| mqjeff wrote: |
Whether it should or not, when it is not reading messages, DOES IT CONTINUE running? |
Yes, as far as I can tell. |
How far is that? Does it produce "inactive and waiting" messages in the log? Could it be made to do so? If it's still loaded into memory and in the task list, is it still connected to the queue manager? Is it hanging?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 16, 2011 9:30 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| Vitor wrote: |
So how long does the MDB run after it's processed the last message?
|
it continues running. It doesn't stop.
| Vitor wrote: |
What is setting this 30 minute timeout? Is it a deliberate timeout or something like the network closing a stale connection? Do you see any messages after 30 minutes consistent with the MDB being errored out?
|
That's an interesting question. I don't know what's causing this 30 minute interval. The 30 minutes seems pretty consistent though. Maybe it is some component timing out. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 16, 2011 9:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| Vitor wrote: |
So how long does the MDB run after it's processed the last message?
|
it continues running. It doesn't stop. |
Does it continue running or do you say that because it's designed to keep running? How do you absolutely, positively know it's still running and has not hung? How do you know it's responsive?
| Gil77 wrote: |
| The 30 minutes seems pretty consistent though. Maybe it is some component timing out. |
And you'd expect your MDB to be able to detect this and throw an error, or a log message, or the app server to notice, so again I ask what's in the logs 30 mins after the last message?
This is also the basis of my question (which you've not answered) as to how the MDB is started. If there's an error, it should be restarted by the same mechanism.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 16, 2011 9:52 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| Vitor wrote: |
Does it produce "inactive and waiting" messages in the log?
|
no
| Vitor wrote: |
Could it be made to do so?
|
Not sure. I would have to check.
| Vitor wrote: |
If it's still loaded into memory and in the task list, is it still connected to the queue manager? Is it hanging? |
not sure. how do I see this? manager console? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 16, 2011 9:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| not sure. how do I see this? manager console? |
If you don't know how to look, how can you be sure it's loaded, running and responsive?
Your problem is sounding more and more like a code issue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 16, 2011 2:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you have an exception listener set on the connection to report and log any errors on the connection?
If the connection gets broken your MDB will stop consuming. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gil77 |
| Posted: Thu Feb 17, 2011 5:50 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| Vitor wrote: |
If you don't know how to look, how can you be sure it's loaded, running and responsive? |
you're right. I am not absolutely sure. I should check. I just don't know how at the moment.
| Vitor wrote: |
Your problem is sounding more and more like a code issue. |
You could be right. But if it is, I haven't found the problem yet. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 17, 2011 5:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| I just don't know how at the moment. |
Is the WAS admin of no help?
| Gil77 wrote: |
| But if it is, I haven't found the problem yet. |
Ensure the code includes exception handling as my most worthy associate has indicated. It's imperative, especially when you're trouble shooting, that the application traps and reports all issues.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bsiggers |
| Posted: Thu Feb 17, 2011 9:27 am Post subject: |
|
|
Acolyte
Joined: 09 Dec 2010
Posts: 53
Location: Vancouver, BC
|
| What's the status of the TCP connections to the listeners on both sides? These should be able to be identified by hostname/portnumber on 'netstat -a' output on any unix/windows platform. Are you maybe getting stale connections because there's a firewall in the middle, or something like this? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 17, 2011 9:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bsiggers wrote: |
| Are you maybe getting stale connections because there's a firewall in the middle, or something like this? |
The OP didn't answer me when I asked that a few posts back....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 23, 2011 6:04 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| exerk wrote: |
| Gil77 wrote: |
| I don't have access to Queue Manager... |
Get access, or get someone who does have access to go through them on your behalf.
|
Okay, I got access to the Queue Manager Logs and it looks like it may be some type of firewall problem where the firewall is closing the connection between the App Server and the Queue:
DMQ7707: Connection to host 'Q4DDDD77 (10.176.80.192)' closed.
EXPLANATION:
An error occurred receiving data from 'Q4DDDD77 (10.176.80.192)' over TCP/IP.
The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator. |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 23, 2011 6:09 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| bsiggers wrote: |
| What's the status of the TCP connections to the listeners on both sides? These should be able to be identified by hostname/portnumber on 'netstat -a' output on any unix/windows platform. Are you maybe getting stale connections because there's a firewall in the middle, or something like this? |
Yes, it might very likely be a firewall problem. But this problem doesn't seem very easy to resolve.
Last edited by Gil77 on Wed Feb 23, 2011 6:13 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
