Wednesday, September 28, 2011

Collecting data for HTTP hang or performance issues on a Lotus Domino server

We're currently having problems with one of our old Domino servers. The HTTP task randomly hangs.

In the process of looking for help to track down the reason, I found this document from IBM.

Collecting data for HTTP hang or performance issues on a Lotus Domino server

1 comments:

nick wall said...

In our prod'n env, we still have http logs enabled (to file), as we are still tracking down a couple of random "slow downs". I know there are tools to read HTTP log files, but if you import into Excel...import as delimited, use "space" as the separator, it imports nicely, then just sort on column 11, response time, you can really quickly find requests that take a long time...either because some coding was rubbish (guilty), or\ and you can check logs to see what else was going on. In our case, a corrupt doc was causing replication to take ages, grinding everything to halt...HTTP threads saturated, app appears to have frozen to users, then clears up as threads complete. We are also using jsf beans, we weren't recycling some DOM objects properly, and over the course of time, memory ran out. If you get a memory dump, using the IBM HeapDump Analyzer, pointed us straight to where we were going wrong. We've been thru many many headaches with HTTP perf probs. Also, we were accessing Web Services on our Domino server, after many back and forths, we got a HotFix from IBM, but in the meantime we switched them all to RESTful style urls instead.