[
https://issues.apache.org/jira/browse/DERBY-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020720#comment-13020720
]
Lily Wei commented on DERBY-5163:
---------------------------------
Thanks Dave and Kathey. When I post a patch, I usually run suites.All and
derbyall using the following script:
java -client -Dderby.tests.trace=true -XX:MaxPermSize=192M -Xmx1024M -Xms512M -D
derbyTesting.oldReleasePath=c:/derby/oldrelease/jars junit.textui.TestRunner org
.apache.derbyTesting.functionTests.suites.AllPackages 2>&1 | tee rjall.out
and
java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall 2>&1 | tee
djall.out
> [patch] fix up sql cleanup handling
> -----------------------------------
>
> Key: DERBY-5163
> URL: https://issues.apache.org/jira/browse/DERBY-5163
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.7.1.1
> Reporter: Dave Brosius
> Priority: Trivial
> Fix For: 10.8.1.1
>
> Attachments: sql_cleanup_fixes.diff
>
>
> When a sql exception occurs, don't allow potential cascading sql problems
> when closing sql objects from masking the original cause of the exception.
> Also make sure statements get closed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
