| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| KeepAlive question |
« View previous topic :: View next topic » |
| Author |
Message
|
| LouML |
 Posted: Thu Jun 19, 2008 5:28 am Post subject: KeepAlive question |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
We just moved an old Unix server to a new data center.
Before, other queue managers just used the actual hostname to communicate with this box (sender and clntconn channels). Because of network configuration changes, we are now using VIPs instead of the actual hostname. These VIPs have been set up with very low timeout values, which is causing apps connecting from other Queue Managers to disconnect when they weren't before.
Rant -
I know the real problem is the poorly coded apps which for some reason, start at 7:30 AM (and connect immediately) but do not do any work until well after 9:00 AM. Of course, now that the connection has timed out, the apps get errors because they are not coded to just reconnect and try again.
-End rant
We are not currently using KeepAlive and I know we need to start using it. The Network team has confirmed that Keep Alive is activated on the network and set for 2 hours.
My question is, does KeepAlive need to be set on:
A - This Queue Manager?
B - Any Queue Manager that wants to talk to this box?
C - Both?
| Code: |
bash-2.05$ echo "dis chl('CH.NEW1P.CLIENT')" | runmqsc QM.testapp.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.testapp.01.
1 : dis chl('CH.NEW1P.CLIENT')
AMQ8414: Display Channel details.
CHANNEL(CH.NEW1P.CLIENT) CHLTYPE(CLNTCONN)
TRPTYPE(TCP) DESCR( )
QMNAME(QM.NEW1P.01) MODENAME( )
TPNAME( ) SCYEXIT( )
MAXMSGL(4194304) SCYDATA( )
USERID( ) PASSWORD( )
CONNAME(new1p.vip.xxx.com(1414)) HBINT(300)
SSLCIPH( ) LOCLADDR( )
KAINT(AUTO) ALTDATE(1986-06-25)
ALTTIME(10.28.16) SSLPEER()
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis chl('CH.testapp.new1p')" | runmqsc QM.jefomsapp.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.testapp.01.
1 : dis chl('CH.testapp.new1p')
AMQ8414: Display Channel details.
CHANNEL(CH.testapp.new1p) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(QM.NEW1P.01) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(new1p.vip.xxxxx.com(1414)) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
SSLCIPH( ) BATCHHB(0)
LOCLADDR( ) KAINT(AUTO)
MCAUSER( ) ALTDATE(2007-10-04)
ALTTIME(08.47.36) SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ |
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu Jun 19, 2008 5:34 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Keep Alive works on the receiving QM.
I set mine to 15 minutes. On every MQ server. And tell every QM to use it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Jun 19, 2008 3:25 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
You've not mentioned what flavor of Unix..... we run on Solaris.
Part of the routine for building out a new MQ server for us is to set the OS keepalive to 15 minutes, then set KeepAlive=yes for each queue manager.
That's been enough for us to deal with the firewall shutdowns of the ports as well as the poorly coded applications. |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Jun 27, 2008 3:49 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| SAFraser wrote: |
You've not mentioned what flavor of Unix..... we run on Solaris.
Part of the routine for building out a new MQ server for us is to set the OS keepalive to 15 minutes, then set KeepAlive=yes for each queue manager.
That's been enough for us to deal with the firewall shutdowns of the ports as well as the poorly coded applications. |
It's Solaris.
For now we've set KeepAlive=Yes on the target box and we have not had the problem again. All future installs and upgrades will get the KeepAlive=Yes as well
Thanks all!
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| 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
|
|
|
|
