[jira] Commented: (SLING-486) Filter chain is not updated when filters are updated

2008-05-28 Thread Felix Meschberger (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.

[jira] Commented: (SLING-486) Filter chain is not updated when filters are updated

2008-05-28 Thread Carsten Ziegeler (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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

2008-05-28 Thread Carsten Ziegeler (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 [EMAIL 
PROTECTED] : [EMAIL PROTECTED]
28.05.2008 15:23:45.547 *WARN* [Background Updatecom.day.cq.cq-linkchecker 
(65)] com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: deactivate 
[EMAIL PROTECTED] : null
28.05.2008 15:23:45.591 *WARN* [SCR Component Actor] 
com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: activate [EMAIL 
PROTECTED] : [EMAIL PROTECTED]
28.05.2008 15:23:45.592 *WARN* [Configuration Updater] 
com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: deactivate [EMAIL 
PROTECTED] : null
28.05.2008 15:23:45.597 *WARN* [SCR Component Actor] 
com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: activate [EMAIL 
PROTECTED] : [EMAIL PROTECTED]
28.05.2008 15:24:26.560 *WARN* [http-8080-1] 
com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: filter [EMAIL 
PROTECTED] : null
28.05.2008 15:24:26.562 *WARN* [http-8080-1] 
com.day.cq.cms.linkchecker.filter.LinkCheckerFilter FILTER: filter [EMAIL 
PROTECTED] : [EMAIL PROTECTED]


 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.