Darn I am kind of out of geotools time for the day .. is there a good 
time when you are on IRC? I assume it is earlier in the day given your 
location.

Running your current set up (with the problem) with a profiler should 
give us the answer we need (ie what new statement is responsible for 
using up the most memory).

OracleDataStore is good a streaming the data from the ResultSet into 
Features and not using memory as it goes. WFSDataStore has a lot of 
overhead parsing that may be causing trouble.

My fear is the memory leak is going to be somewhere in the XML parsing 
code; do you have access to a profiler? Even an evaulation copy of 
JProbe would do the trick (although someone will answer with the latest 
fashionable eclipse plugin I am sure).

Jody
> Hi Jody,
>
> I think I will get some time to found/fix this issue.
> Is it possible that you show me which classes I should inspect?
> The data for testing etc. can I produce e.g. by storing the WFS-Response to 
> disk.
>
> Perhaps this information might be usefull. We consume the same data (size and 
> structure) with the Oracle-Datastore without any problem.
>
> It would be nice when I get introductions where I can start searching the 
> leak.
>
> thanks a lot
>
> Tim
>
> -------- Original-Nachricht --------
> Datum: Thu, 07 Jun 2007 08:00:22 -0700
> Von: Jody Garnett <[EMAIL PROTECTED]>
> An: Tim Englich <[EMAIL PROTECTED]>
> CC: [email protected]
> Betreff: Re: [Geotools-gt2-users] Memory Leak in WFS-Plugin
>
>   
>> Hi Tim - looks like it is time to write a stress test - I have tested 
>> WFSDataStore before with a variety of content sizes and buffer sizes. 
>> There are two threads going on here ... one that reads from the WFS as 
>> fast as data is produced (into an internal buffer) and another that 
>> sucks data out of that buffer one at a time (ie. FeatureReader).
>>
>> We should try and reproduce your request and problem with the "direct" 
>> reader ... to see if this is some mistake in the parsing code.  If that 
>> test goes okay we are then down to a leak in the buffer/reader 
>> relationship which is something we can test artifically and offline 
>> (produce one million fake features and stuff them into the buffer while 
>> reading in another thread).
>>
>> So bring on the test cases; I am totally booked right now on some Java 
>> EE CRS Authority stuff - but others may be available. Let's see how far 
>> we get informally first.
>>
>> Cheers,
>> Jody
>>
>> Tim Englich wrote:
>>     
>>> Hello,
>>>
>>> I think that I have found a Memory Leak in the WFS-Plugin.
>>> I use the Reader to fetch the Data from the WFS.
>>> When I consume FeatureTypes with many Features (over one Million) the
>>>       
>> Memoryconsumtion increases and at least I get an OutOfMemory-Error.
>>     
>>> Has anyone an Idea how I can solve the Problem?
>>>
>>> Best regrats
>>> Tim
>>>   
>>>       
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Geotools-gt2-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>     
>
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to