[
https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054166#comment-13054166
]
Knut Anders Hatlen commented on DERBY-5288:
-------------------------------------------
FWIW, I've never been able to run suites.All on jdk16 with default memory
settings without getting the PermGen space error you saw, even when not running
concurrent tests (default PermGen size is 64MB, I run with 256MB).
Another thing to take into consideration is that some of the tests fork a new
JVM for the network server, so you may get into the situation where your 8 test
runs have 16 processes running at the same time (if all happen to be in such a
test at the same time). Then you'd only have ~240 MB per process, which in my
experience is too little for suites.All. When I run concurrent tests, I
typically split up suites.All in smaller test suites (jdbcapi._Suite,
lang._Suite, etc...) and run them individually so that each process doesn't
grow too big.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a
> different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread:
> http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
