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] Resolved: (FELIX-338) Framework FilterImpl is not thread safe on execution
Date Wed, 15 Aug 2007 20:15:30 GMT

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

Karl Pauls resolved FELIX-338.

    Resolution: Fixed

The patch is in trunk as of r566323. Please try to test whether this makes your issue go away
(or not appear in this case). I'll try to run the framework in the project I saw the same
issue too. Hopefully, it should be gone now. I'll close this issue if I don't hear anything
for some time.

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

View raw message