jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudiu Muresan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3569) Sometimes Jackrabbit fails locating child nodes of a versioned node
Date Tue, 16 Apr 2013 07:55:16 GMT

     [ https://issues.apache.org/jira/browse/JCR-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Claudiu Muresan updated JCR-3569:

    Summary: Sometimes Jackrabbit fails locating child nodes of a versioned node  (was: Sometimes
Jackrabbit fails locating child nodes of a version node)
> Sometimes Jackrabbit fails locating child nodes of a versioned node
> -------------------------------------------------------------------
>                 Key: JCR-3569
>                 URL: https://issues.apache.org/jira/browse/JCR-3569
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6
>         Environment: Linux jaguar 2.6.32-262.el6.x86_64 #1 SMP Sun Apr 8 18:38:00 EDT
2012 x86_64 x86_64 x86_64 GNU/Linux
> Jackrabbit 2.6.0 JCA deployed on JBoss AS 7.1.0.final cluster configuration (domain setup
with 2 managed server instances on the same machine)
>            Reporter: Claudiu Muresan
>            Priority: Minor
>         Attachments: repository.xml
> Jackrabbit repository is configured with versioning capabilities (please check attached
> Sometimes during load conditions on our app (connected to Jackrabbit repository) - 100%
read requests, Jackrabbit fails to find child nodes of a frozen node. 
> The structure under the frozen node is as follows:
> /jcr:system/jcr:versionStorage/../1.0/jcr:frozenNode (fact node)
> /jcr:system/jcr:versionStorage/../1.0/jcr:frozenNode/AssetMap (asset node)
> /jcr:system/jcr:versionStorage/../1.0/jcr:frozenNode/AssetMap/kmp:file (file node)
> /jcr:system/jcr:versionStorage/../1.0/jcr:frozenNode/AssetMap/kmp:file/jcr:content (content
> kmp:file named node is the one that cannot be found.
> No exception is thrown as we are using the iterator way of retrieving the node:
> NodeIterator nit = asset.getNodes();
> if (nit.hasNext()) { // the iterator does not find any child nodes under it
>   Node file = nit.nextNode();
>    ...
> }
> The problem is really hard to reproduce and all the logs are set to ERROR level.
> We suspect the problem may came from the CacheManager, because if we do JCR-SQL2 queries
we have no problem in finding the file node under the asset node.
> The bundle cache size for version workspace is set to default value 8 MB.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message