NOTICE: All information in and attached to the e-mail(s) below may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Thank you.
I do not let browsers access my WAS servers directly. I require them to go through the webserver. I have the PersistTimeout for the webserver set at 3 seconds. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, June 29, 2006 11:00 AM To: [email protected] Subject: WAS Persistent Time-Out Value I'm currently tasked with investigating the persistent time-out value defined in WAS. At this point our time-out value is 60 seconds but what we're seeing is that 2/3's of the connections hit the 60 second time-out and then need to be potentially re-established. I'm looking for what others have this value set at and what the potential fallout, TCP/IP, WAS, is from raising this value. Any help or additional understanding would be greatly appreciated. TIA....... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
