Same here regarding access. I have PersistTimeout in the HTTP server at 5 seconds, with MaxPersistRequest at 10. I'll have to dig and see if I can see the documentation that I used to come up with those numbers. I use persistent connections mostly to reduce the work used for SSL handshakes. What kind of values I have in WebSphere I can't recall, I'll have to check that out, too. Which version of WAS are you running? As Mr. Gray said, are you using the plugin, or are users coming straight in? What's the frequency of hits for a user? Any static content? How many hits per view? SSL or not?
Persistent connections can kill you or save you. It depends on your application. Also, you may get a better response if you post this on the WebSphere list or the WebSphere Forum or MVS-OE. Aaron On Thu, 29 Jun 2006 13:52:56 -0400, Gray, Larry - Larry A <[EMAIL PROTECTED]> wrote: > >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
