felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-338) Framework FilterImpl is not thread safe on execution
Date Wed, 12 Sep 2007 17:54:32 GMT

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

Karl Pauls closed FELIX-338.
----------------------------


Seems to work now.


> Framework FilterImpl is not thread safe on execution
> ----------------------------------------------------
>
>                 Key: FELIX-338
>                 URL: https://issues.apache.org/jira/browse/FELIX-338
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 0.8.0, 1.0.0
>            Reporter: Felix Meschberger
>            Assignee: Karl Pauls
>         Attachments: filter.patch, FilterImpl_rewrite.patch
>
>
> Executing a Filter implemented by the Felix Framework FilterImpl class is not thread
safe, as the Filter.Implmatch() methods are not synchronized but use a Mapper and Evaluator
instance fields which are modified while matching the filter.
> Two options seem to exist:
>    1. Make the match() methods synchronized
>    2. Create Mapper and Evaluator instances on each match() call
> My assumption is that the second method tends to be better because of the synchronization
needed with the first approach.
> Reported by Tom Remoleur, thanks. The full mail thread leading to this issue may be found
at [1].
> [1] http://www.mail-archive.com/users@felix.apache.org/msg00145.html

-- 
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