db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TomohitoNakayama <tomon...@basil.ocn.ne.jp>
Subject Re: Derby Client Driver and LOBs
Date Wed, 06 Dec 2006 14:28:46 GMT

I'm afraid that your case is not addressed yet ...

Several improvement around memory usage for LOB was achieved / is under 
But I think memory usage in NetworkClient driver when receiving LOB from 
NetworkServer is not improved yet.

If you don't mind, could you tell us your case in more detail ?
I want to file it as our task for improvement.

Best regards.

Dominique Pfister wrote:

> Hi,
> I'm a developer in the Apache Jackrabbit project and in the process of
> making it clusterable we're facing some serious problem: we have all
> nodes in the cluster share the repository data and are using derby as
> database back end, running standalone. When retrieving large binary
> data through the derby client driver, I get OutOfMemoryErrors. The
> resource paper "Derby Network Client" says:
>  "The client driver fully materializes LOBS when the row is retrieved"
> which would of course explain those errors when the data gets too
> large. Is this limitation being addressed? Or is there some other way
> of retrieving binary data from a standalone derby database that
> bypasses it?
> Thanks
> Dominique


        Tomohito Nakayama



View raw message