AccessViolation when my server prog close

[sparis]

Hi,

I use TOracleSession in my Multitier Remote Data Module program. When I close this prog, I obtain an AccessViolation at address 78463A33 in module 'ntdll.dll'. I have DOA 345 with Delphi 5 on Win2000 SP2.

NOTE: If I use at same time an ODAC TOraSession, no problemo, both close well.

 

[Marco Kalter]

Are all TOracleSession instances properly freed when the application terminates? Could there perhaps be some "lost" session instances?

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

 

[ThomyKay]

I've noticed the same problem with MIDAS AppServers since version DOA 3.4.5.

And the problem with OracleMonitor (InternalFinalize) is still not solved. But I really need the Monitor to debug (That's what it's good for, isn't it?).

I hate these endless 'trial and error' sessions finding the conditions when DOA finalization works!

 

[ThomyKay]

The problem only occurs when OracleMonitor is linked and when I start 2 MIDAS-Servers coming from different DLLs. When they are in the same DLL no exception occurs. DOA package is linked dynamically to both DLLs.

 

[sparis]

In my program, I use too a TDataBase object.
When I open the TOracleSession before the TDataBase, I have the AccessViolation but if I open the TDataBase before the TOracleSession, all is Ok !?!

Originally posted by sparis:
Hi,

I use TOracleSession in my Multitier Remote Data Module program. When I close this prog, I obtain an AccessViolation at address 78463A33 in module 'ntdll.dll'. I have DOA 345 with Delphi 5 on Win2000 SP2.

NOTE: If I use at same time an ODAC TOraSession, no problemo, both close well.