[
https://issues.apache.org/jira/browse/DERBY-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571588#action_12571588
]
Daniel John Debrunner commented on DERBY-3448:
----------------------------------------------
Another mt issue is the re-setting of the auto-commit state in DbTasks, it uses
a static field so all threads will be using it at the same time. Better just to
use a local variable, or even set the threads up once to use autocommit false
all the time if that's what really is going on.
While the auto-commit state is reset carefully (though not mt safe) the
isolation level is not handled the same way. The read mail method sets the
isolation to read-uncommitted but never resets it, that thread may then proceed
to update the database using read-uncommitted. I don't think this is
intentional, it would be good to clean this up to ensure that the logical
actions are occurring at the intended isolation level.
> Allow the MailJdbc system test to run under junit.
> --------------------------------------------------
>
> Key: DERBY-3448
> URL: https://issues.apache.org/jira/browse/DERBY-3448
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Daniel John Debrunner
> Priority: Minor
> Attachments: derby_3448_dbtasks_cleanup.txt
>
>
> It would be good to get the mailjdbc test to run under junit to allow use of
> the utilities there and decorators such as running the test getting all
> connections from a data source with a statement caching.
> Could still allow the test to run standalone in its current form
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
