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] Issue Comment Edited: (DERBY-3308) Broken synchronization for event handling in ClientPooledConnection40
Date Thu, 24 Jan 2008 10:03:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561688#action_12561688
] 

kristwaa edited comment on DERBY-3308 at 1/24/08 2:02 AM:
-----------------------------------------------------------------

Committed 'derby-3308-1b-eventlisteners_synchronization.diff' to trunk with revision 614536.

I don't expect there will be more work on this issue, will close in a few days.

      was (Author: kristwaa):
    Committed 'derby-3308-1a-eventlisteners_synchronization.diff' to trunk with revision 614536.

I don't expect there will be more work on this issue, will close in a few days.
  
> 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.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