| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Exception Completion Code 2, Reason 2195+2009 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Keka |
 Posted: Sat Oct 20, 2007 8:11 am Post subject: |
 |
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
Just a quick question. Since you are using the application server, are you using a connection pool?? Is it possible that your connection pool has lost connections and your app is unaware of it is trying to use the stale connection object.
if indeed you are using the connection pool what is the purge policy on the connection pool??
if you are not using connection pool, I have seen where the connections to MQ are made in tandom to database. And everytime a database connection is retried a new connection is made to the MQ. Can you check in to this logic??
I know there is no solution suggested here but these detail help troubleshooting the issue better..
Hope that helps.
_________________
Keka |
|
| Back to top |
|
 |
| System9 |
| Posted: Mon Oct 22, 2007 12:25 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Hi,
I am not using conncetion pool. MQ is not in tandom with Database per my knowledge,because database connection establishes at application startup and it will remain till we stop the application.
Thanks
Srikanth |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Oct 22, 2007 4:37 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I agree with Peter. The disconnect after 2 hours is because the TCP connection has come to the end of its KeepAlive interval. You can change the interval using a variety of OS commands, different on every platform.
For Linux, the command is:
| Quote: |
Create/amend file /proc/sys/net/ipv4/tcp_keepalive_time. Insert the interval in seconds.
The parameter takes effect immediately. If the machine is rebooted the parameter is reset to the default value.
To make the change permanent, add a command like:
/#echo 60 >/proc/sys/net/ipv4/tcp_keepalive_time
to the file /etc/rc.d/rc.local script.
|
The 2195 from the Java client is written when the connection is broken, and is the equivalent of 2009 in the C client, so there is no FDC in the qmgr because the error is generated client side. I expect the qmgr side gets an AMQ9209 in the error log.
_________________
MQSeries.net helps those who help themselves..
Last edited by Nigelg on Mon Oct 22, 2007 10:31 pm; edited 1 time in total |
|
| Back to top |
|
|
| System9 |
| Posted: Mon Oct 22, 2007 9:13 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2007
Posts: 9
Location: UK
|
Thanks for the useful information.My only concern of changing this is it will effect other applications in the box.are we having a mechanisam like heartbeat or some thing like that.
Thanks
Srikanth |
|
| 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
|
|
|
|
