[
https://issues.apache.org/jira/browse/DERBY-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007489#comment-13007489
]
Bryan Pendleton commented on DERBY-4443:
----------------------------------------
I think this may be rather tricky. Perhaps other developers have a good idea.
One technique,
which is artificial, is to deliberate modify the code for rolllback so that it
fails. Of course,
that would not be a permanent change, just a temporary one so that you can
exercise your
other altered code paths.
I suspect that this modification may be rather a hard one to test,
unfortunately, so you
may have to resort to some unusual techniques.
> Wrap rollback in exception handlers in try-catch
> ------------------------------------------------
>
> Key: DERBY-4443
> URL: https://issues.apache.org/jira/browse/DERBY-4443
> Project: Derby
> Issue Type: Bug
> Components: Demos/Scripts, Documentation, Eclipse Plug-in, JDBC,
> Network Client, Network Server, Replication, Services, SQL, Test, Tools
> Affects Versions: 10.5.3.0
> Reporter: Aaron Digulla
> Labels: derby_triage10_8
> Attachments: DERBY-4443.patch
>
>
> Avoid this pattern everywhere:
> }catch(SQLException se){
> //issue a rollback on any errors
> conn.rollback();
> throw se;
> }
> because an error in rollback will shadow the original exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
