jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-20) Logging into a repository with a big version history takes a long time
Date Thu, 10 Nov 2005 16:41:04 GMT
     [ http://issues.apache.org/jira/browse/JCR-20?page=all ]
     
Stefan Guggisberg closed JCR-20:
--------------------------------


closing resolved issue

> Logging into a repository with a big version history takes a long time
> ----------------------------------------------------------------------
>
>          Key: JCR-20
>          URL: http://issues.apache.org/jira/browse/JCR-20
>      Project: Jackrabbit
>         Type: Bug
>  Environment: Jackrabbit SVN 76106
>     Reporter: Felix Meschberger
>     Assignee: Tobias Strasser
>     Priority: Critical

>
> Wenn a SessionImpl instance is created, the VersionManager.getVirtualItemStateProvider
method is called. This method - amongst other things - loads the complete (!) version history
into memory and walks through it to do some mapping.
> Besides taking a long time (near 1 minute just to get the version history through PersistentVersionManager.getVersionHistories())
mapping the version histories ultimately results in an "OutOfMemoryError".
> Currently there are 768 version histories and this is only a very small fraction of the
expected final number of version histories in my application

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message