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: Guido Neitzer <email@hidden>
- Date: Mon, 26 Apr 2010 08:49:44 -0700
On 22. Apr, 2010, at 14:17 , Farrukh Ijaz wrote:
> 2. Sometimes the logs show message with Runtime Exception "Statement running too long" what can be the reason. Does the back database backup running on the same database can cause this problem? If yes, how to fix that?
I'd start looking into this. Turn on SQL logging through Wonder (check the example properties in ERExtensions, it's all in there, copy those to your app, start it with SQL logging set to something that you get a stacktrace when a statement runs for too long - maybe a second or two).
Then go from there:
- Check whether it's database access that is causing the instance to get stuck
- If yes, optimize db access (indexes, better query, ...)
- Use Wonder's connection broker if you have to
If this is not the case, get some more thread dumps when the instance is definitely in that state. Set the number of worker threads to a reasonable number (like 4 or 8) and check whether it craps out earlier. If yes, get more thread dumps.
Take care,
Guido
_______________________________________________
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