We have Remedy 7.1 installed on a windows environment using Oracle as the database. We are using the isapi filter to redirect requests to Tomcat 5.25. What we have been able to identify (I suspected for some time) is that when there is a higher volume of traffic, requests will get a timeout and fail. We were able to identify this by using web services as the request generating mechanism. My hypothesis is that when the isapi filter is "full" (unable to accept new requests) it denies requests and creates a "DOS" type situation. To resolve this in the past when this would happen with the mid tier is to direct traffic to the alternate host and let the primary host "catch up" for about 10 minutes and everything starts working again. Alternatively we tested going to the Tomcat server directly through port 8080 and found the success rate was 100% for properly formed requests. My question is, has anyone else experienced this behavior? If so have you identified any configuration/architecture changes to resolve it?
Thank you for any light you can shed, Jim Coryat Micron Technology Inc. ITIL v2 Practitioner Certified _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
