Oracle sessions hanging after commit/rollback

[Syspec]

We are currently using DOA version 3.4.6.4 with an Intraweb (v5.0.61) ISAPI dll to implement an online application.

At first everything seems to work fine, at the (Intraweb) session timeout all the objects are freed and the oracle session (using OracleSession object) is discarded.

Then, when someone uses the application to update the database, causing a commit (or rollback on error), all subsequent oracle connections, made by any new online user, hang and are not discarded at the (Intraweb) session timeout. This also seems to keep the (Intraweb) session from closing properly and this also stays open indefinitely.

The only way to get rid of these connections seems to be unloading the ISAPI dll from ISS, which is not really an option in a production environment.

I don't know if this is related to the recent "unsafe destructors" post where the destructor does not completely remove the DOA connection.(?)

Please can you suggest anything, a workaround, to resolve this situation.

(We've tested with Oracle Cliente 8.1.6, 8.1.7 and 9.2.0 with the same results)

 

[Marco Kalter]

The "unsafe destructors" topic merely applies to exceptions raised within a destructor. I do not see how this would apply here.

I'm not clear what is happening in your ISAPI DLL when your oracle session hangs though. Where is it hanging? What is happening?

------------------
Marco Kalter
Allround Automations

 

[Syspec]

Apologies for not replying sooner. This problem appears to have been resolve by installing the newer release of Intraweb.

Thank you for your attention to this problem.

Christopher.