db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3308) Broken synchronization for event handling in ClientPooledConnection40
Date Tue, 05 Feb 2008 13:20:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-3308:
-----------------------------------

    Fix Version/s: 10.3.2.2
                   10.2.2.1

Backported the fix (revision 614536):
10.2 -> revision 618639
10.3 -> revision 618640

I ran all tests for both branches without errors, and both merges were clean.
Updated the fix versions accordingly.

> Broken synchronization for event handling in ClientPooledConnection40
> ---------------------------------------------------------------------
>
>                 Key: DERBY-3308
>                 URL: https://issues.apache.org/jira/browse/DERBY-3308
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.2.0, 10.3.2.1, 10.4.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.2.2.1, 10.3.2.2, 10.4.0.0
>
>         Attachments: derby-3308-1a-eventlisteners_synchronization.diff, derby-3308-1b-eventlisteners_synchronization.diff
>
>
> Access to the the list of event listeners is not synchronized properly.
> Taken the rather infrequent use of the relevant methods and the small critical sections,
I mean it is sufficient to add synchronization to all the methods that access it at the method
level. The same approach is taken in ClientPooledConnection (although not followed through
consistently, some of the methods are unsynchronized).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message