You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Strasser (JIRA)" <ji...@apache.org> on 2004/11/18 21:25:35 UTC
[jira] Assigned: (JCR-20) Logging into a repository with a big version history takes a long time
[ http://nagoya.apache.org/jira/browse/JCR-20?page=history ]
Tobias Strasser reassigned JCR-20:
----------------------------------
Assign To: Tobias Strasser
> Logging into a repository with a big version history takes a long time
> ----------------------------------------------------------------------
>
> Key: JCR-20
> URL: http://nagoya.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://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira