[
https://issues.apache.org/jira/browse/CXF-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957839#comment-15957839
]
Sergey Beryozkin edited comment on CXF-7309 at 4/5/17 10:02 PM:
----------------------------------------------------------------
Np, thanks, please take your time as I won't have much time to look at this
issue as I'm away next week, unlikely will have much time this week too, but
positive we'll get the issue resolved for CXF 3.1.12, thanks
was (Author: sergey_beryozkin):
Np, thanks, please take you time as I won't have much time to look at this
issue as I'm away next week, unlikely will have much time this week too, but
positive we'll get the issue resolved for CXF 3.1.12, thanks
> JAX-RS @Context fields throw NPE in OSGI hot deployed filters
> -------------------------------------------------------------
>
> Key: CXF-7309
> URL: https://issues.apache.org/jira/browse/CXF-7309
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.12, 3.1.10
> Reporter: Ezequiel Rosas Garcia
>
> Hello.
> This happens with a PreMatching filter that is loaded from OSGI.
> I found that when the filter OSGI bundle is hot deployed, all other already
> running bundles using it would start throwing NPE when trying to access the
> injected fields inside the filter (like CXF-7248)
> This seems to happen due to other bundles retaining their ThreadLocal
> references in their own AbstractResourceInfo#getSetterProxyMap() while the
> OSGI Proxy starts redirecting to a new filter object which has new different
> ThreadLocal references as soon as it is used for the first time after hot re
> deployment.
> Test:
> [Link](https://github.com/nhtzr/osgiee-web/blob/42faf2cbe0c54497ea706e97cd91a9ee8c29e020/src/test/java/mx/nhtzr/osgiee/web/internal/MyFilterTest.java)
> PR: [Link](https://github.com/apache/cxf/pull/253)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
