You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2012/10/11 00:01:11 UTC
[jira] [Created] (OAK-373) OOME running TCK
Michael Dürig created OAK-373:
---------------------------------
Summary: OOME running TCK
Key: OAK-373
URL: https://issues.apache.org/jira/browse/OAK-373
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Michael Dürig
This is caused by JCR-3444 and the changes in revision 1396552 which seem to make sessions more expensive memory wise.
--
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
[jira] [Commented] (OAK-373) OOME running TCK
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473611#comment-13473611 ]
Michael Dürig commented on OAK-373:
-----------------------------------
In revision 1396825 I split up the TCK tests into several suites in order to give the GC a chance to run in-between and clean the leftovers from JCR-3444 up. I also increased the heap for the test runner to 512M.
> OOME running TCK
> ----------------
>
> Key: OAK-373
> URL: https://issues.apache.org/jira/browse/OAK-373
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Michael Dürig
>
> This is caused by JCR-3444 and the changes in revision 1396552 which seem to make sessions more expensive memory wise.
--
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