You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Ole Solberg (JIRA)" <ji...@apache.org> on 2009/05/07 08:32:30 UTC
[jira] Closed: (DERBY-3817) 'java.lang.OutOfMemoryError: Java heap
space' in 'xtestMaxOpenStatementsWithQueryTimeout(....StatementJdbc30Test)'
since 676946 2008-07-15 18:01:08 MEST
[ https://issues.apache.org/jira/browse/DERBY-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg closed DERBY-3817.
------------------------------
Resolution: Cannot Reproduce
Not seen since r703193 2008-10-09
> 'java.lang.OutOfMemoryError: Java heap space' in 'xtestMaxOpenStatementsWithQueryTimeout(....StatementJdbc30Test)' since 676946 2008-07-15 18:01:08 MEST
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3817
> URL: https://issues.apache.org/jira/browse/DERBY-3817
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.5.1.1
> Environment: OS: Solaris 10 5/08 s10x_u5wos_10 X86 64bits - SunOS 5.10 Generic_127128-11
> JVM: Sun Microsystems Inc.
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22 mixed mode 64-bit)
> Reporter: Ole Solberg
> Priority: Minor
>
> 'xtestMaxOpenStatementsWithQueryTimeout(org.apache.derbyTesting.functionTests.tests.jdbcapi.StatementJdbc30Test)' failing with 'java.lang.OutOfMemoryError: Java heap space' since 676946 2008-07-15 18:01:08 MEST http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/676946.txt .
> The failure is seen on SunOS 5.10 / Sun Jvm 1.6.0 only.
> See e.g. http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/sol/682186-suitesAll_diff.txt
> The test (suites.All) is run with '-XX:-UseThreadPriorities -XX:MaxPermSize=128M -Xmx256M -d64'.
> When run with '-XX:MaxPermSize=128M -Xmx256M' as is used for the other platforms in this set of tests we do not see a failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.