Re: Weird exception thrown

 
I sent this message to the list last week, but I did not receive it. Is it
that with the list relocated, the sender do not get its own messages? I am
trying to resend. If you guys got it twice, I apologize in advance.
 
Regards,
Eddie


  _____  

From: Eddie Lascu [mailto:[email protected]] 
Sent: Sunday, January 11, 2009 8:11 PM
To: '[email protected]'
Subject: Weird exception thrown


Hello,
 
I have an application that reads an XML file, parses it and saves its data
into an Oracle database. The save is actually an insert, if the record
doesn't exist or an update if the record exists. In order to figure out
which operation I have to perform, I execute a select, to check whether the
record is already in the database. I build the Select SQL statement, create
an Oracle Command object with it and then call its Execute Reader method.
This method returns an OracleDataReader object and for that, all I care to
check is to see whether it has any records. The OracleDataReader class has a
property called "HasRows" that will tell me just that.
I know what you are thinking: I should ask this question on a different
forum, like one Oracle hosts for their ODP.NET development, but bare with me
for a second.
After running for 2-3 days continuously, my application starts throwing this
weird exception where it says that "Memory could not be allocated". I
managed to trace the raise of the exception to the invocation of the
"HasRows" property for the OracleDataReader object. The problem is that,
looking at the documentation, that property is not raising any exceptions,
so what the heck is going on.
To keep things under control, I even tried to kick in the garbage collection
(GC.Collect()) myself, every now and then. Now the exception takes longer to
be triggered, but eventually it is triggered.
Can anyone give me some ideas as to what else to try and figure out what the
problem is? The XML files are not really big, averaging around 100 kB each.
When the exception is triggered, I look ion the task manager and Physical
Memory usage is nowhere near the top.
Any suggestion will be highly appreciated.
 
TIA,
Eddie 
 
PS: Further to my message, two more things that I observed: 
 
1. If I kill the process and then restart it, the exception is no longer
triggered for the 3-day interval;
2. If, while the exception is thrown, I force the garbage collection, that
still doesn't fix the problem, or at least not right away, but I didn't have
the patience to see if it gets resolved after a while.
 
 

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives