[
https://issues.apache.org/jira/browse/ARIES-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090964#comment-14090964
]
Heath Kesler commented on ARIES-1233:
-------------------------------------
I believe this ticket can be closed, I believe it was an implementation issue.
The issue was that a single bean from bundle A was being initialized in spring
and exposed in 2 different service with 2 different interfaces. if you
initialize a separate bean for each service the problem goes away.
> Stale service reference retention on consumer bundle after service provider
> bundle update.
> ------------------------------------------------------------------------------------------
>
> Key: ARIES-1233
> URL: https://issues.apache.org/jira/browse/ARIES-1233
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Environment: Apache Karaf 3.0.1
> Reporter: Jamie goodyear
>
> Three Bundles, A, B, and C.
> Bundle A provides a service, which is wired via BP.
> Bundles B and C consume the service via BP references. Service trackers are
> enabled, showing that both bundles are aware of when the service provider
> updates.
> Bundle A configuration property tells the service to use bundle B or C for
> processing. Upon a configuration update the consuming bundles B and C will
> contain stale references to the Bundle A service. Refreshing/Restarting their
> bundles will correct the wiring. The BP container should refresh these
> service references automatically.
> I'm working on a stripped down demonstration test case to illustrate the
> issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
