Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.4, 2.2, 3.0.0
    • Fix Version/s: 2.1.5, 2.2, 3.0.0
    • Component/s: connector
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Patch Info:
      Patch Available

      Description

      Tranql has just released new wrappers that recognize some non-fatal sql exceptions and use ConnectionPoolDatasource rather than Driver or Datasource when we have figured out how.

        Activity

        Hide
        David Jencks added a comment -

        2.2 rev 829426.

        Show
        David Jencks added a comment - 2.2 rev 829426.
        Hide
        David Jencks added a comment -

        trunk rev 829427

        Show
        David Jencks added a comment - trunk rev 829427
        Hide
        Ashish Jain added a comment -

        Hi David,
        Can you please apply the changes to 2.1 branch as well?

        Thanks
        Ashish

        Show
        Ashish Jain added a comment - Hi David, Can you please apply the changes to 2.1 branch as well? Thanks Ashish
        Hide
        Ashish Jain added a comment -

        Please apply this fix to geronimo 2.1 branch

        Show
        Ashish Jain added a comment - Please apply this fix to geronimo 2.1 branch
        Hide
        Rex Wang added a comment - - edited

        if no objections, I will update these for G2.1.5

        branch 21 with rev. 916184
        branch 22 with rev. 920239

        Show
        Rex Wang added a comment - - edited if no objections, I will update these for G2.1.5 branch 21 with rev. 916184 branch 22 with rev. 920239
        Hide
        Ashish Jain added a comment -

        Hi rex There are some issues with the newly release tranql informix driver. The jira number is TQL-21.

        Show
        Ashish Jain added a comment - Hi rex There are some issues with the newly release tranql informix driver. The jira number is TQL-21.
        Hide
        Rex Wang added a comment -

        I see https://issues.apache.org/jira/browse/GERONIMO-5044 is closed by you?
        and TQL-21 has been apply to informix connector 1.2, you mean the 1.2 has some problems so that we have to release a new one?

        Show
        Rex Wang added a comment - I see https://issues.apache.org/jira/browse/GERONIMO-5044 is closed by you? and TQL-21 has been apply to informix connector 1.2, you mean the 1.2 has some problems so that we have to release a new one?
        Hide
        Rex Wang added a comment -

        HI, Ashish, can this jira be closed?

        Show
        Rex Wang added a comment - HI, Ashish, can this jira be closed?
        Hide
        Ashish Jain added a comment -

        Hi Rex,
        There were some issues seen with informix db and hibernate. We are testing it with openjpa and will let you know.
        Thanks
        Ashish

        Show
        Ashish Jain added a comment - Hi Rex, There were some issues seen with informix db and hibernate. We are testing it with openjpa and will let you know. Thanks Ashish
        Hide
        Ashok Poralu added a comment -

        Hello Rex/Ashish,

        I have tested the functionality of PreparedStatementCacheSize with Informix database, Its seems working fine without any issues. Have created a very simple test case to verify the functionality,

        1. Created a Prepared statement.
        2. Executed the statement in loop.
        3. Closed the Prepared statement object.
        4. Tried again using the prepared statement object to execute another loop, as this should be cached by the datasource connection when closing the object (in step3).

        This confirms the functionality. Working as designed.

        Thanks,
        Ashok Poralu

        Show
        Ashok Poralu added a comment - Hello Rex/Ashish, I have tested the functionality of PreparedStatementCacheSize with Informix database, Its seems working fine without any issues. Have created a very simple test case to verify the functionality, 1. Created a Prepared statement. 2. Executed the statement in loop. 3. Closed the Prepared statement object. 4. Tried again using the prepared statement object to execute another loop, as this should be cached by the datasource connection when closing the object (in step3). This confirms the functionality. Working as designed. Thanks, Ashok Poralu
        Hide
        Ashish Jain added a comment -

        Thanks Ashok for the test. Can you also update the tranql JIRA with this information?? The JIRA no is tql-21.

        Show
        Ashish Jain added a comment - Thanks Ashok for the test. Can you also update the tranql JIRA with this information?? The JIRA no is tql-21.
        Hide
        Rex Wang added a comment -

        closing it per above comments
        thanks, Ashish and Ashok.

        Show
        Rex Wang added a comment - closing it per above comments thanks, Ashish and Ashok.

          People

          • Assignee:
            Ashish Jain
            Reporter:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development