Hi list,
we have a rather busy WO-service. Sometimes one of our multiple database
servers fails and CLOSE_WAIT shows its ugly head and kills the performance.
What I think the problem is:
- WebServer asks AppServer for data
- AppServer tries to connect to db
- more requests come in
- AppServer tries to connect to db
- more requests come in
- AppServer tries to connect to db
- more requests come in
...
Then after a while the WebServers close their side of the connection but the
app connection threads still wait in queue for the database. So the app never
acknowledges the close and we slowly die.
Is this what happens?
Can we do something against it?
A delegate method perhaps, to throw an error if we can not connect to the db?
(And of course retrying later to reconnect - after all the database will come
online again)
Any pointers are welcome,
atze
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
