OT: oo4o and IIS

This is slightly off topic, sorry.

We're developing an application in asp with oracle at the back. It does connections with oo4o using a pool. All sql are in pl/sql packages. With little load it works great. When stress testing the app, after some time connections between web server and db stop responding generating an error on "CreateSql". This error happens as many times as there are initiated connections to Oracle. After that following pages breaks on GetDatabaseFromPool (even though there are room for more connections in the pool).

It seems that this behavior only happen with asp pages that calls stored procedures that passes many (5-10) ref cursors as parameters.

When this have occurred all pages that uses a db connection fails, but pages without connections executes fine. The db keeps responding as usual after the failure, e.g. it accepts connections from other applications.

There are no errors in alert.log nor listener.log

The tests uses 50 connections at the same time, the pool accepts 100.

During the tests dllhost.exe memory consumption fluctuates between 250-350MB, the (web)server uses in total less than 600MB (of 1GB).

Open cursors during test are a little less than 3000, more or less constant. There are between 90 and 110 (of 150) oracle processes in the db server.

To me it seems that the Oracle client software runs out of some resource, but I don't understand what.

Client is 10.1.0.3 on win 2000, DB is 10.1.0.3 on Linux.

Any ideas on how to debug this further greatly appreciated! Lex Received on Sat Jun 11 2005 - 17:43:53 CDT