Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-93

Oracle setTransactionTimeout only propagates to server during XAResource.start method invocation

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.2.1
    • 4.2
    • JTA, JTS
    • None

    Description

      Invocations of the XAResource.setTransactionTimeout method are cached by the Oracle driver until a call to the XAResource.start method has occurred.

      The Type 4 driver accepts the new value and stores it locally but this does not appear to be propagated except as part of the start method invocation.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users JBTM-99 Fine grained control over setTransactionTimeout execution

          • 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

              kconner@redhat.com Kevin Conner (Inactive)
              kconner@redhat.com Kevin Conner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d