[
https://issues.apache.org/jira/browse/DERBY-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3337:
----------------------------------
Attachment: derby-3337_noprop_diff.txt
Here is a patch with the property removed. Instead of the sleep, we call
runFinalization() if there is less than a half MB of free memory.
On IBM JDK 1.6 where (with the first patch), I was seeing the test fail
intermittently with 16MB and the property not set, it now seems to pass
consistently, just calling runFinalization() a few times (as can be seen with
-Dderby.tests.debug=true
I think I like this approach better and think it still tests that Derby does
not leak.
> convert jdbcapi/derbyStress.java to JUnit
> -----------------------------------------
>
> Key: DERBY-3337
> URL: https://issues.apache.org/jira/browse/DERBY-3337
> Project: Derby
> Issue Type: Task
> Components: Test
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3337_diff.txt, derby-3337_noprop_diff.txt
>
>
> Convert derbyStress to JUnit. Framework will have to be setup for running in
> a low memory profile. Temporarily moved the test back to derbyall. See
> DERBY-3336 for details and possible options moving forward.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
