[ARIES-1621] Aries Transaction Manager is published to the OSGi registry then immediately re-published

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: transaction-manager-1.3.0
• Fix Version/s: transaction-manager-1.3.1
• Component/s: Transaction
• Assignee: Guillaume Nodet
• Reporter: Marc Durand
• Created: 27/Sep/16 13:00
• Updated: 19/Dec/19 17:36
• Resolved: 27/Sep/16 14:06

Description

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.

Issue Links

• relates to: KARAF-4758 Upgrade to Aries Transaction Manager 1.3.1