[jira] [Updated] (OAK-373) OOME running TCK

2013-11-13 Thread Michael Marth (JIRA)
[ https://issues.apache.org/jira/browse/OAK-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-373: -- Fix Version/s: (was: 0.12) 0.11 > OOME running TCK > > >

[jira] [Updated] (OAK-373) OOME running TCK

2013-11-07 Thread Michael Marth (JIRA)
[ https://issues.apache.org/jira/browse/OAK-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-373: -- Fix Version/s: 0.12 > OOME running TCK > > > Key: OAK-373 >

[jira] [Updated] (OAK-373) OOME running TCK

2013-02-27 Thread JIRA
[ https://issues.apache.org/jira/browse/OAK-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-373: -- Component/s: it > OOME running TCK > > > Key: OAK-373 >

[jira] [Updated] (OAK-373) OOME running TCK

2012-12-19 Thread Alex Parvulescu (JIRA)
[ https://issues.apache.org/jira/browse/OAK-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated OAK-373: Attachment: OAK-373.patch I think that the OOME is caused by the NodeStore caching. It appears to have