[
https://issues.apache.org/jira/browse/ARIES-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-1621.
------------------------------------
Resolution: Fixed
Assignee: Guillaume Nodet
> Aries Transaction Manager is published to the OSGi registry then immediately
> re-published
> -----------------------------------------------------------------------------------------
>
> Key: ARIES-1621
> URL: https://issues.apache.org/jira/browse/ARIES-1621
> Project: Aries
> Issue Type: Improvement
> Components: Transaction
> Affects Versions: transaction-manager-1.3.0
> Reporter: Marc Durand
> Assignee: Guillaume Nodet
> Fix For: transaction-manager-1.3.1
>
>
> The Aries Transaction Manager's bundle activator publishes an implementation
> of the javax.transaction.TransactionManager service when the bundle
> activator's start method is called. Because the activator implements the
> ManagedService interface, it then almost immediately receives its
> configuration from config admin, causing the transaction manager to be
> unregistered and then re-registered.
> This very short term initial registration of the TransactionManager sometimes
> allows other components that have a reference to the TransactionManager to
> start up only to then almost immediately be shut down as the
> TransactionManager is being re-published.
> See
> http://karaf.922171.n3.nabble.com/Karaf-4-x-startup-Aries-causing-components-to-deactivate-and-re-activate-multiple-times-td4047996.html
> for more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
