Uploaded image for project: 'CloverETL'
  1. CloverETL
  2. CLO-1613

Long profiler jobs on server fail due to unsuitable default JDBC pool settings

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-3-4-2
    • Component/s: Profiler, Server
    • Security Level: Users (General product issues)
    • Labels:
    • QA Testing:
      GUI manual test
    • OTRS_Ticket_ID:
      2013080810000071

      Description

      JDBC pool settings we use are:
      removeAbandoned=true
      removeAbandonedTimeout=240

      This causes every long profiler job fail after 4 minutes of execution with "Closed Connection" error because Profiler keeps its profiler job status connection open during the whole time of profiler job execution.

      Workarounds:

      1. configure profiler database connection via JNDI
      2. remove all
        <property name="removeAbandoned" value="true"/>

        from WEB-INF/applicationContext.xml

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                raszykj Jan Raszyk (Inactive)
                Reporter:
                raszykj Jan Raszyk (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: