You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/05/28 14:27:45 UTC
[jira] Created: (SLING-486) Filter chain is not updated when
filters are updated
Filter chain is not updated when filters are updated
----------------------------------------------------
Key: SLING-486
URL: https://issues.apache.org/jira/browse/SLING-486
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: 2.0.0
Reporter: Carsten Ziegeler
Fix For: 2.0.0
When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-486) Filter chain is not updated when filters
are updated
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-486.
----------------------------------
Resolution: Fixed
With the upgrade to latest SCR implementation, this is fixed as well.
> Filter chain is not updated when filters are updated
> ----------------------------------------------------
>
> Key: SLING-486
> URL: https://issues.apache.org/jira/browse/SLING-486
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Fix For: 2.0.1
>
>
> When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-486) Filter chain is not updated when
filters are updated
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-486:
-----------------------------------
Fix Version/s: (was: 2.0.0)
2.0.1
As this is not a bug in Sling but in Felix I'll remove it from the 2.0.0 schedule.
> Filter chain is not updated when filters are updated
> ----------------------------------------------------
>
> Key: SLING-486
> URL: https://issues.apache.org/jira/browse/SLING-486
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Fix For: 2.0.1
>
>
> When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-486) Filter chain is not updated when
filters are updated
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600471#action_12600471 ]
Carsten Ziegeler commented on SLING-486:
----------------------------------------
Yes, I did refresh - here are some updates:
During an update, the old instance is disposed, a new instance is created, activate is called, then the configuration updater kicks in, deactivates the old instance and creates a new one. From this point on, both instances are in the filter chain.
28.05.2008 15:23:11.552 *WARN* [SCR Component Actor] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: activate com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@e8b496 : org.apache.felix.framework.BundleContextImpl@a6c44f
28.05.2008 15:23:45.547 *WARN* [Background Updatecom.day.cq.cq-linkchecker (65)] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: deactivate com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@e8b496 : null
28.05.2008 15:23:45.591 *WARN* [SCR Component Actor] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: activate com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@1a1546 : org.apache.felix.framework.BundleContextImpl@6ad043
28.05.2008 15:23:45.592 *WARN* [Configuration Updater] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: deactivate com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@1a1546 : null
28.05.2008 15:23:45.597 *WARN* [SCR Component Actor] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: activate com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@1734ba : org.apache.felix.framework.BundleContextImpl@6ad043
28.05.2008 15:24:26.560 *WARN* [http-8080-1] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: filter com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@1a1546 : null
28.05.2008 15:24:26.562 *WARN* [http-8080-1] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: filter com.day.cq.cms.linkchecker.filter.LinkCheckerFilter@1734ba : org.apache.felix.framework.BundleContextImpl@6ad043
> Filter chain is not updated when filters are updated
> ----------------------------------------------------
>
> Key: SLING-486
> URL: https://issues.apache.org/jira/browse/SLING-486
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-486) Filter chain is not updated when
filters are updated
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600475#action_12600475 ]
Carsten Ziegeler commented on SLING-486:
----------------------------------------
Further debugging seems to reveal that this is the same problem as https://issues.apache.org/jira/browse/FELIX-550
Two instances are created and registered, however if the timing is different, for instance during debugging everything works as expected.
> Filter chain is not updated when filters are updated
> ----------------------------------------------------
>
> Key: SLING-486
> URL: https://issues.apache.org/jira/browse/SLING-486
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-486) Filter chain is not updated when
filters are updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600460#action_12600460 ]
Felix Meschberger commented on SLING-486:
-----------------------------------------
I cannot reproduce this issue. Did you do refreshPackages after the update ? (should be default in the current Web Console and sling plugin)
> Filter chain is not updated when filters are updated
> ----------------------------------------------------
>
> Key: SLING-486
> URL: https://issues.apache.org/jira/browse/SLING-486
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> When a bundle containing a servlet filter is updated, the old already disposed instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.