Uploaded image for project: 'Aries'
  1. Aries
  2. ARIES-1621

Aries Transaction Manager is published to the OSGi registry then immediately re-published

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gnt Guillaume Nodet
                Reporter:
                marc.durand Marc Durand
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: