felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Moore (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-827) URLHandlers does not restore the previous URLStreamHandlerFactory after stopping Felix
Date Tue, 02 Dec 2008 01:21:44 GMT

    [ https://issues.apache.org/jira/browse/FELIX-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652227#action_12652227
] 

Tim Moore commented on FELIX-827:
---------------------------------

Karl,

I tried applying the patch to our custom build of felix-framework, but it didn't apply cleanly
over my own patch. I'll keep watching in hopes that the underlying issue with URLHandlers
is eventually resolved.

Thanks,
Tim

> URLHandlers does not restore the previous URLStreamHandlerFactory after stopping Felix
> --------------------------------------------------------------------------------------
>
>                 Key: FELIX-827
>                 URL: https://issues.apache.org/jira/browse/FELIX-827
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: felix-1.2.1
, felix-1.4.0
>            Reporter: Tim Moore
>            Assignee: Karl Pauls
>             Fix For: felix-1.4.1
>
>         Attachments: felix-827.patch, leak.patch, test-felix-handler-1.0-SNAPSHOT.jar,
test-felix-handler.zip
>
>
> I'm running Felix embedded inside a webapp, running in Tomcat.
> Tomcat installs its own URLStreamHandlerFactory. Felix swaps it out correctly when I
start it, and seems to delegate properly. When the webapp is unloaded, however, and it stops
Felix, it does not restore the previous implementation, but rather leaves the existing URLHandlers
instance installed. Then, if I try to redeploy the webapp without restarting the JVM, I get
errors, because Tomcat automatically sets the URLHandlers class's static members to null when
it unloads the webapp. (see https://issues.apache.org/bugzilla/show_bug.cgi?id=41939)
> I've tested this on 1.2.1 and 1.4.0, and both versions have this problem.

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