Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8073

SynchronizationImple.afterCompletion gobles up Exception

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • Transaction Manager
    • None
    • Release Notes
    • Hide
      If an unexpected failure occurred during execution of the <systemitem>Synchronization.afterCompletion</systemitem> method, the original exception thrown after the failure was not logged and the following warning was logged instead:
      <programlisting>
      2012-02-08 12:47:31,402 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkerThread#0[127.0.0.1:46304]) [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@3c255a5a
      </programlisting>
      This behavior prevented exact identification of the failure. With this update, logging has been extended to include such exceptions. The exceptions are now logged, enabling easier identification of failures that occur.
      Show
      If an unexpected failure occurred during execution of the <systemitem>Synchronization.afterCompletion</systemitem> method, the original exception thrown after the failure was not logged and the following warning was logged instead: <programlisting> 2012-02-08 12:47:31,402 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkerThread#0[127.0.0.1:46304]) [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@3c255a5a </programlisting> This behavior prevented exact identification of the failure. With this update, logging has been extended to include such exceptions. The exceptions are now logged, enabling easier identification of failures that occur.
    • Documented as Resolved Issue
    • NEW

    Description

      If there is an unexpected failure in a Synchronization.afterCompletion the original exception is gobled up.

      2012-02-08 12:47:31,402 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkerThread#0[127.0.0.1:46304]) [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@3c255a5a

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users JBTM-257 Add more logging to participants when they fail

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              rhn-engineering-cdewolf Carlo de Wolf
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: