| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| sometimes messages are not read from Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Wed Feb 23, 2011 6:10 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| 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 |
After all, I suggested stale connections a few posts back! 
You have a few actions:
- as the message says, tell the system administrator or in this cases the network people.
- fit proper error trapping to the MDB so it reports every error without you needing to dig through the logs. This would (should) manifest in your MDB as a 2009/2019/2059 sort of error which would have pointed you directly at a network issue from the off, rather than this odd "sometimes it doesn't read a message" situation you initially reported.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| Gil77 |
| Posted: Wed Feb 23, 2011 6:33 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| Vitor wrote: |
You have a few actions:
- as the message says, tell the system administrator or in this cases the network people.
|
I have, last week. The network people don't seem able to resolve the problem.
They have tried the following :
- change the Session Pool value
- changed the Unused Timeout of the Connection Pool of the Connection Factory from 1800 seconds to 1200 seconds
but these changes haven't fixed the problem. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 23, 2011 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Gil77 wrote: |
I have, last week. The network people don't seem able to resolve the problem.
They have tried the following :
- change the Session Pool value
- changed the Unused Timeout of the Connection Pool of the Connection Factory from 1800 seconds to 1200 seconds
but these changes haven't fixed the problem. |
That's because YOU need to stop trying to have the problem fixed by one side or the other. Start by talking with the network people. This is not an US vs THEM problem, this is a WE need to fix it TOGETHER type of problem.!
The connection is only considered idle in the pool if it is unused.
If the connection is being used, but not active, the pool will not consider it being idle, and the firewall will cut if off as being idle.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gil77 |
| Posted: Wed Feb 23, 2011 7:50 am Post subject: |
|
|
Novice
Joined: 16 Feb 2011
Posts: 16
|
| fjb_saper wrote: |
That's because YOU need to stop trying to have the problem fixed by one side or the other. Start by talking with the network people. This is not an US vs THEM problem, this is a WE need to fix it TOGETHER type of problem.!
|
Thank you for the advice! You are right. The AppServer people are at a different site from the Queue Manager people and are actually part of a different company. The AppServer people are at a different site as I am and cannot be reached by telephone, only e-mail and skype. So these are obstacles but not insurmountable. I have tried to facilitate better communication between all parties. Hopefully, this will help resolve the problem.
| fjb_saper wrote: |
The connection is only considered idle in the pool if it is unused.
If the connection is being used, but not active, the pool will not consider it being idle, and the firewall will cut if off as being idle.
|
Yes, as long as requests are being made over the Queue to the AppServer, everything is fine. But if there are no requests for 30 minutes, then the firewall seems to close the connection. The next request that is made then is not read from the queue and this is where we are having the error. Requests that come after this request are successful if there is not a 30 min period of inactivity between them. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 23, 2011 8:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gil77 wrote: |
| But if there are no requests for 30 minutes, then the firewall seems to close the connection. |
Firewalls do that, especially if whoever configured them told them to do it!
This underlines the advice of my most worthy associate - this is not a them & us situation. The network people (assuming they are the ones configuring the firewalls) need to understand the requirements of your configuration. The app server people need to understand the network policies and work within them. Everybody needs to pull together.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Feb 23, 2011 10:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Make sure ClientIdle wasn't set on the QM server, as that could be killing idle but otherwise valid client connections just like a firewall. I don't know if the error in the QM Error Log would be exactly the same though.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
