Re: Recover from NullReferenceException in OracleClient.DBObjectPool...

Update, Update!

Ok, with the the OleDB provider we are actually able to recover from
the exception without leaking memory! However, sometimes the connection
will block indefinitely on the Open! From what I understand this is
because the MSDAORA uses the 7.x OCI interface which does not support a
timeout on the connection.

So, we have switched all code to the Oracle ODP.NET which uses 9.x OCI
which does support timeout. This code is in testing now... I will let
you know...

Any thoughts would be appreciated...

Thanks!


spam@xxxxxxxxxxxxxxxxxx wrote:
> Update!
>
> Once placing code into production environment and encountering the Null
> Reference Exception, this time we slightly modify the connect string to
> create a new pool and this worked perfectly!
>
> However, now the application starts leaking memory like crazy!! We
> started at 48MB and 3 hours after getting exception we where at 210MB!!
> Before restarting the app I attached and created a mini-dump and have
> started looking at this in WinDbg. One think I noticed right off the
> bat was that there where 186 Dead Threads!! Our application will use
> ~18 threads while everything is running fine. These threads are marked
> for Completion Port Pool and Thread Pool worker threads.
>
> We have now dumped the OracleClient code and modified for
> OleDBClient... this will go into prod tomorrow so I will update if I
> have any good news...
>
> We are getting killed by the customer over this... Any thoughts would
> be appreciated...

.

Relevant Pages