There is / was a bug in the Oracle Plugin that opened two connections
for every single connection you opened yourself to get the dreaded
JDBC info and never closed it this one even if you closed all your
connections. We had a similar cased in the PostgreSQL plugin.
So an application with excessive usage of new object store
coordinators could cause that. I'd turn on adaptor logging and check
for these things.
cug
On 12. Jun. 2009, at 14:06 , Mark Ritchie wrote:
On 12-Jun-09, at 2:01 PM, Vicky C. Miller wrote:
Good question. 9,000 connections to either other processes in
WebObjects
and to the Oracle database.
9,000 connections to the database does seem to be a tad excessive...
I'm still not sure what you mean by the "either other processes".
For the connections to the database, I'd turn on
EOAdaptorDebugEnabled and see when the connections to the database
is being opened. Off the top of my head, I can't think of a case
where too many connections to the database would be fixed by
changing WebObjects versions... However, did I mention that it's
been 7 days in a row for me! ;-)
M.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
dep...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/guido.neitzer%40gmail.com
This email sent to guido.neit...@gmail.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
