web services using session pooling

[jsarniak]

using session pooling and IIS

I have created an ISAPI dll to run on IIS using DELPHI 2005 (I am using DOA version 4.0.6.2). The ISAPI dll calls another DLL to do some work (mainly data base).

In the ISAPI dll, I am using connection pooling from the Global sessionPool. I am creating an TOracleSession (in the CallDll part of the web service) and assigning to it a connection from the pool.

The problem is that when you do not set the thread safe property of the OracleSession, access errors happen when more than one client is running at the same time. If you do set the thread safe property to true, a deadlock occurs when you try to run more than one client.

Any suggestions would be appreciated.

 

[Marco Kalter]

When do you call TOracleSession.Logon and LogOff (or set the Connected property)? The LogOn call will reserver a connection from the pool, and LogOff will release the connection into the pool again. Between LogOn and LogOff, access to the session should be restricted to one thread. Is this the case here?