Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-563

Thread leak reported by Tomcat when using the connector

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 2.2.1
    • 2.5.0
    • batch
    • None
    • Linux 64-bit rhel07

    Description

      When used in a Tomcat application, the following thread leaks are reported sometimes:

      WARNING: The web application [...] appears to have started a thread named [MariaDb-bulk-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method)

      The Driver is properly unloaded. It seems like these threads are not being joined.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. CONJ-671 MariaDb bulk threads occupy full cpu(99%) while db connections broken

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. CONJ-683 Timer task doesn't stop after finishing query

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Diego Dupin made transition -
            Open Closed
            		378d 4h 50m 1
            Diego Dupin made transition -
            Closed Stalled
            		242d 5h 4m 2
            Diego Dupin made transition -
            Stalled Closed
            		23h 53m 2

            People

              diego dupin Diego Dupin
              bgedik Bugra Gedik
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.