Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- Subject: Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- From: Chuck Hill <email@hidden>
- Date: Mon, 26 Apr 2010 13:08:07 -0700
On Apr 26, 2010, at 10:36 AM, Guido Neitzer wrote:
On 26. Apr, 2010, at 09:55 , Chuck Hill wrote:
It might. It should indicate if requests start taking longer to
process. You could also enable WO logging (see WO's apache.conf)
to see what the woadaptor has to say.
It won't say all too much as far as I recall. Mark can add some
info here, I guess.
It will indicate if the woadaptor is marking the instance as
dead. If this happens without a corresponding slowdown in the app,
it would indicate some other problem (wotaskd "stuck"?).
I might be mixing up something now, but if I recall the explanation
correctly, there was a bug with the adaptor logging that prevented
it from logging properly after the initial messages as long as you
didn't do some permission magic. Or so (getting old, bad
memory) ... ;-)
Oh, that is what you meant. I recall Mark saying... something about
that. Getting old sucks.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden