Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- Subject: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- From: Farrukh Ijaz <email@hidden>
- Date: Fri, 23 Apr 2010 00:17:06 +0300
Hi WOGurus,
1. We've few applications based on same database structure. What happens, one of the application after approximately 500 hits gets down. What can be the reason for that? (I know the question is too broad but would appreciate for any clues).
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?
3. I've read in the documentation that we can have multiple editing context but all of them by default share 1 database context. What I understand from this is if we configure pooling setting in the properties file it won't have any affect since there is only one channel for database. Is that right? If yes, how can we enable them to utilize connection pooling without creating multiple database contexts per session.
Farrukh _______________________________________________
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