| Author |
Message
|
| viaimi00 |
 Posted: Tue Mar 08, 2005 5:27 pm Post subject: MQ client conecction drops by Firewall |
 |
|
Newbie
Joined: 08 Mar 2005
Posts: 2
|
We have MQSeries 5.3 Server installed on the iSeries (AS400) and the MQ Client installed on Window 2000. If the connection is idle for more than 1 hour, our firewall would terminate the connection. Is there any way we can keep the connection up even if there are no traffic between the Server and Client?
We have already configured the Keep Alive Interval to *AUTO on the channel and KeepAlive=Yes on qm.ini on the AS400. |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Tue Mar 08, 2005 6:12 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
KAINT only applies to z/OS.
I know I have remote Client Applications that always keep QLocals open for output using SVRCONN Channels on some of my MQManagers but I am not a WMQ Application Programmer so I really can't explain the mechanics of how.
Check the WMQ Intercommunications Guide.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 09, 2005 4:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Clients manual may also help.
A well written client should detect that the connection has closed, and reestablish it on it's own.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Mar 09, 2005 5:30 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Have the MQClient issue a Get With Wait. As the MQGET waits for the hour, it consumes the messages as soon as they arrive. If there are no messages, MQ sends Heartbeats over the connection (based on the channel properties) while your MQGET is waiting. This should provide the network traffic needed so the firewall thinks the connection is still live.
But you should hvae reconnect logic built in anyway, to detect dropped connections, whether that connection is dropped after 1 hour, or after 1 second, for whatever reason.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqmhr |
| Posted: Wed Mar 09, 2005 5:52 am Post subject: |
|
|
Centurion
Joined: 28 Dec 2004
Posts: 105
|
About the HeartBeat interval , the Intercommunication channel says
| Quote: |
This attribute is valid for sender, cluster-sender, server, receiver, cluster-receiver, and requester channels. Other than on z/OS and OS/400, it also applies to server-connection and client-connection channels. On these channels, heartbeats flow when a server MCA has issued an MQGET command with the WAIT option on behalf of a client application.
|
Does this mean that heartbeat flows will not be sent in a server connection channel to A/S 400? |
|
| Back to top |
|
|
| viaimi00 |
| Posted: Thu Mar 10, 2005 3:33 pm Post subject: |
|
|
Newbie
Joined: 08 Mar 2005
Posts: 2
|
Thanks guys. I am thinking more on the environment or channel setups on the clients. At the moment the clients can start up the connections automatically when they receive the next messages.
The problem is the performance or timeout issue. Sometimes the clients take too long to reply because they have to start the new connections.
There is a value KeepAlive=Yes or KeepAliveInterval but I am not too sure how it works or how to set them up on the on the clients |
|
| Back to top |
|
|
|
|
