Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6593

(7.0.z) JBJCA-1321 - Statement.cancel() is not invoked until the statement is completed

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.4.CR1, 7.0.4.GA
    • None
    • None
    • None
    • EAP 7.0.4

    Description

      Hi,

      in our application we are using the Statement.cancel() method to stop long-running queries; in Wildfly 9.0.2 this is not working because the cancel() method is synchronized using a lock which is not released until the query is executed. In WrappedStatement:

      public void cancel() throws SQLException
    {
      if (doLocking)
          lock();
       try
       {
        /* ... */

      It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final WrappedStatement.cancel doesn't try to obtain the lock.
      Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion.

      Thank you,

      lorenzo

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5084 Statement.cancel() is not invoked until the statement is completed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1321 Statement.cancel() is not invoked until the statement is completed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6489 (7.0.z) Upgrade to IronJacamar from 1.3.4 to 1.3.5

          • 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.
          • Verified

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: