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

Upport JBPAPP-2811: EJB3 timer service doesn't retry on rollback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.2 ER1
    • EAP 5.0.0, EAP 5.0.1
    • EJB
    • None
    • Hide
      In the event of a transaction rollback during a timeout callback, the timeout callback must be retrieved as per spec EJB 3.1 FR 18.4.3. The container did not enlist the timer into the transaction and the timer could not be retrieved on rollback. Timer callback implementation has been changed to support running within transactions so that after the timeout callback is rolled back, the callback is retired by the service.
      Show
      In the event of a transaction rollback during a timeout callback, the timeout callback must be retrieved as per spec EJB 3.1 FR 18.4.3. The container did not enlist the timer into the transaction and the timer could not be retrieved on rollback. Timer callback implementation has been changed to support running within transactions so that after the timeout callback is rolled back, the callback is retired by the service.
    • Documented as Resolved Issue

    Attachments

      Issue Links

        is blocked by

        Sub-task - The sub-task of the issue EJBTHREE-2035 Upport JBPAPP-2811: EJB3 timer service doesn't retry on rollback

        • 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.
        • Resolved
        is incorporated by

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBPAPP-6225 Upgrade jboss-ejb3-bom-eap5 to 1.0.3

        • 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
        relates to

        Bug - A problem that impairs or prevents the functions of the product. JBPAPP-2811 EJB3 timer service doesn't have retry

        • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
        • Closed

        Activity

          People

            rhn-engineering-cdewolf Carlo de Wolf
            rhn-support-tkimura Takayoshi Kimura
            Jared Morgan Jared Morgan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: