Oh...
Sorry.
I missed DERBY-1560
Best regards.
Bryan Pendleton wrote:
Dominique Pfister wrote:
I looked at the relevant parts of the derby client driver (version
10.1.3.1) and quickly coded a solution for large objects exceeding
1MB, using temporary files that are deleted as soon as
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
Hello.
I'm afraid that your case is not addressed yet ...
Several improvement around memory usage for LOB was achieved / is under
work.
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
Hello Tomohito,
thank you very much for your reply! Jackrabbit, the JSR-170 reference
implementation, uses an embedded derby database to store its content,
by default. In order to cluster several repository nodes, derby is
started standalone and all cluster nodes, possibly running on
different
Dominique Pfister wrote:
I looked at the relevant parts of the derby client driver (version
10.1.3.1) and quickly coded a solution for large objects exceeding
1MB, using temporary files that are deleted as soon as the blob is no
longer referenced. If there is interest, I could further refine my
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?
DERBY-208
Øystein Grøvlen wrote:
DERBY-208 is filed to address this.
Thanks Øystein ! I linked DERBY-1560 to DERBY-208 because
they seem closely related.
bryan
Øystein Grøvlen wrote:
Dominique Pfister wrote:
I looked at the relevant parts of the derby client driver (version
10.1.3.1) and quickly coded a solution for large objects exceeding
1MB, using temporary files that are deleted as soon as the blob is no
longer referenced. If there is
