- 
Need Help on Odd Domino HTTP Issue / XPages
Category http wtf
Big Kudo Points and and a level up to anyone who can help point me in the right direction on this one ...
I'm putting together a well-endowed server, it's running SuSE Linux, and domino 8.5.1 ... Whenever I go to open a database via http I get a 12 (to 20) second delay before the http service responds. The http thread logs show this:
*** Start Request Step: Session 28, Thread cbf34b70, Clock 218710
*** Raw Request Step: Session 28, Thread cbf34b70, Clock 218710
*** Pre Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Post Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Get Group List Step: Session 28, Thread cbf34b70, Clock 218710
*** Authorized Server Access Step: Session 28, Thread cbf34b70, Clock 218710
*** Translate Step: Session 28, Thread cbf34b70, Clock 218710
*** Post Translate Step: Session 28, Thread cbf34b70, Clock 218710
*** Authorized Step: Session 28, Thread cbf34b70, Clock 218710
*** Process Request for User Jeremy Hodge: Session 28, Thread cbf34b70, Clock 218710
*** Calling Url Cache Process Request: Session 28, Thread cbf34b70, Clock 218710
*** Calling Inotes Process Request: Session 28, Thread cbf34b70, Clock 218710
*** Post write Buffer, bytes [176]: Session 28, Thread cbf34b70, Clock 230824
The delay happens at the bolded lines above, "*** Calling Inotes Process Request"... the clock time is in milliseconds, and you can see the 12 second delay between the clock time on that line and the Post write Buffer ... Its within this line that it actually executes everything to render the response (which happens to be an XPages application) ... but the majority of the wait happens before the Before Page Load of the XPage executes. Once the process hits that point, it's off to the races and the actual XPage rendering only takes milliseconds.
Does anybody know how to get a more detailed log to trace out where this may be happening?
Nathan pointed out a post that showed a similar issue found in the R7 days, but there was no response to the question then .... hoping someone can help ... or at least maybe know how to get deeper logs so I can get an inkling of the delay. I've got this happening on 6 partitions across three servers in a cluster, one of which I have torn apart three ways from Sunday trying to find a causal link.
HELLLLLP
Thanks
Big Kudo Points and and a level up to anyone who can help point me in the right direction on this one ...
I'm putting together a well-endowed server, it's running SuSE Linux, and domino 8.5.1 ... Whenever I go to open a database via http I get a 12 (to 20) second delay before the http service responds. The http thread logs show this:
*** Start Request Step: Session 28, Thread cbf34b70, Clock 218710
*** Raw Request Step: Session 28, Thread cbf34b70, Clock 218710
*** Pre Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Post Authenticate Step: Session 28, Thread cbf34b70, Clock 218710
*** Get Group List Step: Session 28, Thread cbf34b70, Clock 218710
*** Authorized Server Access Step: Session 28, Thread cbf34b70, Clock 218710
*** Translate Step: Session 28, Thread cbf34b70, Clock 218710
*** Post Translate Step: Session 28, Thread cbf34b70, Clock 218710
*** Authorized Step: Session 28, Thread cbf34b70, Clock 218710
*** Process Request for User Jeremy Hodge: Session 28, Thread cbf34b70, Clock 218710
*** Calling Url Cache Process Request: Session 28, Thread cbf34b70, Clock 218710
*** Calling Inotes Process Request: Session 28, Thread cbf34b70, Clock 218710
*** Post write Buffer, bytes [176]: Session 28, Thread cbf34b70, Clock 230824
The delay happens at the bolded lines above, "*** Calling Inotes Process Request"... the clock time is in milliseconds, and you can see the 12 second delay between the clock time on that line and the Post write Buffer ... Its within this line that it actually executes everything to render the response (which happens to be an XPages application) ... but the majority of the wait happens before the Before Page Load of the XPage executes. Once the process hits that point, it's off to the races and the actual XPage rendering only takes milliseconds.
Does anybody know how to get a more detailed log to trace out where this may be happening?
Nathan pointed out a post that showed a similar issue found in the R7 days, but there was no response to the question then .... hoping someone can help ... or at least maybe know how to get deeper logs so I can get an inkling of the delay. I've got this happening on 6 partitions across three servers in a cluster, one of which I have torn apart three ways from Sunday trying to find a causal link.
HELLLLLP
Thanks
| Permalink | 
Comments
Posted by best songs of 2012 ideeas At 05:53:51 AM On 11/07/2011 | - Website - |
Posted by 2012 haircuts At 07:49:35 AM On 10/26/2011 | - Website - |
Posted by teddy bear hamsters for sale At 03:07:24 AM On 10/05/2011 | - Website - |
Posted by best lawn mowers 2012 At 09:52:13 AM On 10/04/2011 | - Website - |
Posted by birendranath At 09:20:15 PM On 02/25/2011 | - Website - |
Posted by Jeremy Hodge At 04:30:32 PM On 08/25/2010 | - Website - |
2. Make sure your INI setting has HTTPQueueMethod=2 in it. This *should* be the default in 8.5.1, but you can read more about it here: { Link }
3. Are you running a Fix Pack? 8.5.1 pre-FP1 had some serious delay/caching problems with user group caching which may be affecting things. I can personally vouch for 8.5.1FP3 being darn fast on adequate hardware.
4. Run "show stat domino.*" on the console and look for threads.active.peak. If it's equal to the maximum number of HTTP thread specified in your server doc in your NAB, then you've got threads queueing and need to up that number in the NAB. Try like 20% higher. If things get slow keep going up.
Hope this helps. If none if this fixes things I'd open a ticket with IBM support.
Posted by Erik Brooks At 09:07:10 PM On 08/22/2010 | - Website - |