Hi,
Just recently I experienced an out of memory problem with Jackrabbit.
I analyzed the memory usage and found the problem is the combined size
of the various caches of Jackrabbit, and other libraries (Lucene, the
database, and others). The biggest problem was the combined size of
the
On 11/2/06, Thomas Mueller [EMAIL PROTECTED] wrote:
Hi,
Just recently I experienced an out of memory problem with Jackrabbit.
I analyzed the memory usage and found the problem is the combined size
of the various caches of Jackrabbit, and other libraries (Lucene, the
database, and others). The
good idea.
+1
On 11/2/06, Thomas Mueller [EMAIL PROTECTED] wrote:
Hi,
Just recently I experienced an out of memory problem with Jackrabbit.
I analyzed the memory usage and found the problem is the combined size
of the various caches of Jackrabbit, and other libraries (Lucene, the
database,
Angela Schreiber schrieb:
hi julian
why do you think the ValueFactory comes from the SessionInfo?
Because I was confused :-) (and had been looking at JCR's Session
interface immediately before).
as far as i know, the ValueFactory is retrieved from the
configuration. so, perhaps you simply
Jaka Jaksic wrote:
//element(*, nt:linkedFile)[jcr:contains(@jcr:content, 'search string')]
the jcr:content property on nt:linkedFile is a reference property and matching
the uuid against 'search string' will of course never match.
//element(*,
Angela Schreiber schrieb:
...
btw: there is a simple ValueFactory in the jackrabbit-commons
package. you may use this one or provide your own.
BTW:
That ValueFactory unfortunately isn't as generic as I would like: it
enforces Reference properties to use UUID syntax, which of course isn't
hi julian
that was exactly the reason for not 'hardcoding' the
ValueFactoryImpl as it is the case in jackrabbit.
if you look at the spi2dav project you will find
a slightly modified ValueFactoryImpl, that deals
with exactly this issue.
however i would argue, that it depends on the spi
Angela Schreiber schrieb:
hi julian
that was exactly the reason for not 'hardcoding' the
ValueFactoryImpl as it is the case in jackrabbit.
if you look at the spi2dav project you will find
a slightly modified ValueFactoryImpl, that deals
with exactly this issue.
however i would argue, that it
Hi,
I noticed that we don't have JIRA components for SPI yet. Shouldn't we
create those, or do we want to rely on the mailing list?
Best regards, Julian
Hi,
I'm getting an NPE inside jcr2spi if my QPropertyDefinition returns null
upon getDefaultValues(). Looking at the JCR API for
PropertyDefinition, it seems to me that null and empty arrays have
different semantics, so SPI should support both...
Best regards, Julian
===
Hi,
On 11/2/06, Julian Reschke [EMAIL PROTECTED] wrote:
I noticed that we don't have JIRA components for SPI yet. Shouldn't we
create those, or do we want to rely on the mailing list?
I would suggest using Jira, at least for specific bug reports and
improvement/feature requests. I just
OutOfMemoryError when re-indexing the repository
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
[
http://issues.apache.org/jira/browse/JCR-550?page=comments#action_12446831 ]
Jukka Zitting commented on
OutOfMemoryError when re-indexing the repository
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
[
http://issues.apache.org/jira/browse/JCR-550?page=comments#action_12446843 ]
Marcel Reutegger commented on
13 matches
Mail list logo