You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2005/02/07 04:29:13 UTC

[jira] Closed: (DIRMINA-7) FilterManagers are not thread-safe.

     [ http://issues.apache.org/jira/browse/DIRMINA-7?page=history ]
     
Trustin Lee closed DIRMINA-7:
-----------------------------

    Resolution: Fixed

http://svn.apache.org/viewcvs?view=rev&rev=151670

I replaced complex Double-linked list with array to store the chain of filters.  Instead the range of filter priorities are limited.  You will find IoHandlerFilter.MIN/MAX_PRIORITY and ProtocolHandlerFilter.MIN/MAX_PRIORITY constants.  Because FilterManagers has been changed to store filter entries to an array whose index is priority value, the filter chain traversal is not very efficient.  But the range of the filter priority is 100 which is fairly small, so I think it is OK at most situation.

> FilterManagers are not thread-safe.
> -----------------------------------
>
>          Key: DIRMINA-7
>          URL: http://issues.apache.org/jira/browse/DIRMINA-7
>      Project: MINA
>         Type: Bug
>     Versions: 0.7
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>      Fix For: 0.7

>
> FilterManagers will malfunction if events are fired while any filter is added or removed simultaneously.  We'll have to fix this issue by using ReadWriteLock.  Is it OK for us to use Doug Lea's concurrent package here?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira