| Author |
Message
|
| dextermbmq |
 Posted: Thu Jul 31, 2014 10:37 am Post subject: HBINT for SVRCONN Channel |
 |
|
Voyager
Joined: 26 Jul 2014
Posts: 77
|
Hi All,
We have a Client Application that runs 24X7. It uses CLNTCONN-SVRCONN channels to connect to a Queue Manager. Many a time we noticed that the application goes down with MQRC 2009 error (Connection Broken)
We confirmed the network and there seems no network issues between the queue manager server and the serer hosting Client Application.
I am not sure why the application is going down when there are no network issues.The Application is written in JAVA and we use TCP protocols.
We use DISCINT as 0 and HBINT as 300 in the channel definitions.
MQ CLIENT : v7.0.1.10
MQ SERVER : v7.5.0.1
Platform : MQ server bon AIX and MQ Client on WINDOWS
Any help would be greatly appreciated |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Thu Jul 31, 2014 11:04 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It might be worth looking in the error logs both on the server and the client. I can't remember where (or if) the JAVA client writes errors to a log file to be honest. Clearly the C client does. You may have to look for a linked exception. Either way, it should be possible to determine why MQ thought there was a comms. failure.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| dextermbmq |
| Posted: Thu Jul 31, 2014 11:21 am Post subject: |
|
|
Voyager
Joined: 26 Jul 2014
Posts: 77
|
Hi Paul,
We have not configured the logging for MQ client , however the error log of QMGR shows : TCP-IP Connection error.(Error connecting to XXX.XXX.XX.XX)TCP IP connection error. But our network team says there are no network related issues. There are multiple processes within this application and only a single goes down with this error which proves that its not a network error else all the processes should go down with MQRC2009
While googling I found a link where :
it says that malfunctioned Heartbeats can cause this error :
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IZ52693
My question is if i put HBINT as 0 in my channel definition , what adverse impact can it create(if it all) |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Thu Jul 31, 2014 12:03 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
If you suspect the JAVA Heartbeat code is causing this problem would it not be better just to install the fixpack?
I can't speak for the Java client but certainly for the C client, when using SHARECNV, the heartbeat is of less importance since we can use TCP KEEPALIVE to detect remote failures. Havingg said that some firewalls like regular traffic to flow to keep the socket active so heartbeats are still useful for that.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| tczielke |
| Posted: Thu Jul 31, 2014 12:51 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
| Quote: |
| But our network team says there are no network related issues. |
I have heard that before. And it wasn't true. Sometimes you have to speak their language and run tcp traces to show them that their truly is a network issue. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Aug 01, 2014 6:27 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
|
| Back to top |
|
|
| dextermbmq |
| Posted: Sun Aug 03, 2014 10:36 pm Post subject: |
|
|
Voyager
Joined: 26 Jul 2014
Posts: 77
|
Hi Joseph,
Thanks a lot for the link.
While going through the link I could see that setting DefRecon to YES in mqclient.ini is an option to enable the auto reconnect at application level without touching the code. However, the table 1 lists out that If the Client application is in JAVA Program access to reconnection options is not supported and my application is in JAVA. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 04, 2014 4:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dextermbmq wrote: |
Hi Joseph,
Thanks a lot for the link.
While going through the link I could see that setting DefRecon to YES in mqclient.ini is an option to enable the auto reconnect at application level without touching the code. However, the table 1 lists out that If the Client application is in JAVA Program access to reconnection options is not supported and my application is in JAVA. |
Quite unprecise here. Are we talking about Java base or JMS? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Aug 04, 2014 6:51 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Well, if this is Java using the MQI API, then you are on the hook for reconnect logic unless you are using a connection factory that does that for you.
If you are only PUTting/GETting msgs, then it is far better to use JMS (for this and more reasons).
Connections get broken in networking and reconnect logic is just a part of the game.
If you really cannot change the code, you could connect to a local Qmgr (in bindings mode) and allow those channels to do the reconnect logic to other Qmgrs. |
|
| Back to top |
|
|
|
|
