db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5057) Out-of-memory error in istat tests
Date Thu, 03 Mar 2011 09:49:36 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001939#comment-13001939

Knut Anders Hatlen commented on DERBY-5057:

If I understand the config files for the nightly tests correctly, the failing configurations
have been running without explicit memory settings. Not sure if that's the problem, but I've
now reconfigured them to use the same settings that the other test runs use (-Xmx512M -XX:MaxPermSize=256M),
so we'll see...

> Out-of-memory error in istat tests
> ----------------------------------
>                 Key: DERBY-5057
>                 URL: https://issues.apache.org/jira/browse/DERBY-5057
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>         Environment: Java 5, solaris
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_8
> We saw an out-of-memory error in the istat tests during the nightly test run on Java
5 on Solaris last night. See http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-1071310.html

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message