| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Client connection to MQ Server fails after somo period |
« View previous topic :: View next topic » |
| Author |
Message
|
| rsinha |
 Posted: Sun Mar 15, 2009 11:55 am Post subject: MQ Client connection to MQ Server fails after somo period |
 |
|
Apprentice
Joined: 29 Aug 2003
Posts: 42
|
Hi,
We have recently installed MQ binaries and created queues and channels etc on a NetApp storage, that has been mounted on a Linux server. The Linux server has been placed in a highly secure environment and appropriate Firewall rules have been applied between the server and the mounted NetApp storage.
We then installed the client app on another Linux box which is outside the boundaries of the secure environment in which MQ server resides. We applied the FW rules for port 1420 so the Client app can initiate connection to MQ Server. This arrangement works fine except that if we send a message from the client app to MQ server after a period of 30 minutes of inactivity between client app and MQ server, it starts give this error.
"com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009"
This means connection to Queue Manager is broken. But at the same time everything is running fine on the MQ box, including the queue manager, the listeners etc. The ping and telnet from Client to MQ box is also working fine. Infact, on MQ box when I check the status of the transmit queue, I see the client is still connected to it.
display qstatus(transmit.q1) type(handle) all
So if the client is still connected to the queue manager, why do I get the '2009' error when i try to send a message from the client app? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Mar 15, 2009 12:00 pm Post subject: Re: MQ Client connection to MQ Server fails after somo perio |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rsinha wrote: |
| So if the client is still connected to the queue manager, why do I get the '2009' error when i try to send a message from the client app? |
Because something (firewall?) has timed out the connection after 30 minutes, and the queue manager hasn't noticed / cleaned up the connection yet?
There's been a lot of discussion on the forum regarding the admin of unused client conns you might find useful.
It's also best practice for a client to respond initially to a 2009/2019/2059 by simply attempting to reconnect.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 15, 2009 12:17 pm Post subject: Re: MQ Client connection to MQ Server fails after somo perio |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| rsinha wrote: |
| So if the client is still connected to the queue manager, why do I get the '2009' error when i try to send a message from the client app? |
Because something (firewall?) has timed out the connection after 30 minutes, and the queue manager hasn't noticed / cleaned up the connection yet?
There's been a lot of discussion on the forum regarding the admin of unused client conns you might find useful.
It's also best practice for a client to respond initially to a 2009/2019/2059 by simply attempting to reconnect. |
May be even better by attempting to first disconnect the broken connection and then reconnect. You could also try and change your default tcp timeout to the firewall timeout. This would help cleaning up the connection on the qmgr side...
On the other hand I sure hope your client connection is SSL encoded. Otherwise your qmgr is wide open.... Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
