glassfish
  1. glassfish
  2. GLASSFISH-3960

Possible deadlock when using connection leak tracing and reclaim

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 9.1.1
    • Fix Version/s: 9.1.1
    • Component/s: jca
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      3,960
    • Status Whiteboard:
      Hide

      911Approved

      Show
      911Approved

      Description

      When using connection-leak-tracing and leak-reclaim, there is a possibility of
      deadlock.

      Two locks are used
      1) Pool
      2) connection-leak-lock

      There is a code path in which order of acquisition of lock is inverse which may
      result in dead-lock.

      code-path :
      Path - 1:
      addResource(ResourceSpec spec, ResourceHandle h)[acquires pool-lock]
      setResourceStateToBusy
      startConnectionLeakTracing [acquires connection-leak-lock]

      Path - 2:
      potentialConnectionLeakFound [acquires connection-leak-lock]
      freeResource [acquires pool-lock]

        Activity

          People

          • Assignee:
            Shalini
            Reporter:
            Jagadish
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: