Thanks, Larry, Aaron. It's a fairly complex, at least to this simple mind, application.Desktop -> Citrix -> possible calls to one, two or all) AS/400, SQL Server, z/OS. We have at least 3 different locations where the Users come in from. We're currently running WAS V4 (3.5 lightweight mode) under z/OS 1.4. The Users are coming in via plugin, not sure of the hits per User, not sure about static content but I don't believe there is on our side, not sure about the hits per view, no SSL. When the application runs it runs very well. When there are problems I personally get frustrated due to the amount of trouble shooting capability we have. There are so many places where the app. can fall down. We're contracting right now to try to find the most obvious problems. We were told that some of the data showed timeouts at 60 seconds for quite a bit of the traffic on our end, z/OS. Since I'm a bit WAS challenged I've been looking for doc to view to get a better handle of what may be happening. Any pointers to doc would be appreciated. I've been to redbooks but there are so many I'm not sure which one will have the most useful information.
Can you point me to the WAS listserve? I guess I can go over there and get kicked around a bit. Thanks again for your help. Aaron Walker <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 06/30/2006 12:54 PM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: WAS Persistent Time-Out Value 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. > ---------------------------------------------------------------------- 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
