| Author |
Message
|
| raja8183 |
 Posted: Tue Nov 10, 2015 11:44 am Post subject: IBM MQ v7.5 Client HEARTBEAT and KEEPALIVE |
 |
|
Newbie
Joined: 10 Nov 2015
Posts: 1
|
Below is my configuration.
Client: IBM MQ v7.5 Resource Adaptor on JBoss 5.2 EAP
CCDT File configuration to write responses.
Server: IBM MQ v5.3
Client connects to the queues specified in the CCDT file to write responses to the MQ. But after >60 minutes the connections are killed by the firewall. Client is not aware of this, and when tries to reply the next time goes into a reconnection status. To avoid this both HEART BEAT and KEEP ALIVE are enabled on the SVRCONN channel. Below are my two questions:
1. The heart beats from the server, according to the MQ guys, are not being acknowledged back by the client. How do we resolve this? IS there an explicit configuration that needs to be set in the wmqjmsra-ds.xml file?
2. I do not see any keep alive traffic between the server and client. Have changed the keep alive setting to a numeric value on the MQ explorer. |
|
| Back to top |
|
 |
| zpat |
| Posted: Tue Nov 10, 2015 12:06 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Where did you get that time machine from?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 10, 2015 12:27 pm Post subject: Re: IBM MQ v7.5 Client HEARTBEAT and KEEPALIVE |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| raja8183 wrote: |
| Below is my configuration. |
And you expect all this to work when your v7.5 client is talking to a v5.3 server which
a) don't work the same way
b) handle these things differently
Guess what? Your massively ancient, massively out of support server can't handle the modern client.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vinodkumar.w |
| Posted: Tue Aug 02, 2016 9:02 pm Post subject: |
|
|
Newbie
Joined: 02 Aug 2016
Posts: 1
|
| I am also facing the same problem in my prod servers . Experts need your help. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 03, 2016 3:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| vinodkumar.w wrote: |
| I am also facing the same problem in my prod servers . Experts need your help. |
You're using a 7.5 client to talk to a v5.3 server?
If not, it's not the same problem.
What is the problem you are having?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 03, 2016 4:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinodkumar.w wrote: |
| I am also facing the same problem in my prod servers . |
If you are indeed facing the same problem (V5.3 server choking on a v7.5 client) then the comments above apply. Specifically:
| Vitor wrote: |
| Guess what? Your massively ancient, massively out of support server can't handle the modern client |
Or to put it another way, this is what you get for taking the risk of not updating your software. Sooner or later the risk blows up in your face.
If that's not your situation, why are you hijacking this thread and not starting your own? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Aug 03, 2016 4:34 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| Client connects to the queues specified in the CCDT file to write responses to the MQ. But after >60 minutes the connections are killed by the firewall. Client is not aware of this, and when tries to reply the next time goes into a reconnection status. To avoid this both HEART BEAT and KEEP ALIVE are enabled on the SVRCONN channel. |
IIRC, MQ client heatbeat was introduced in MQ v7.0. In MQ v5.3, the qmgr sits on a socket read indefinitely, waiting for the client to send something (eg. starting a MQI call). If nothing is sent, the system TCP KEEP ALIVE (or firewall) may close the connection.
With v7.5 Client and v5.3 Qmgr combination, the client protocol negotiates to the lowest common level, which is v5.3 
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 04, 2016 3:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Tell the firewall people to stop killing your channels.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
