Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4440

Intermittent Java deadlock when running LobStreamsTest with insane jars

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 10.6.1.0
    • None
    • Store
    • None
    • Dual core CPU at 3.2 GHz, OpenSolaris, Java HotSpot(TM) Client VM (14.1-b02 mixed mode)

    Description

      The following deadlock was obtained by using jstack when the test LobStreamsTest hung:

      Found one Java-level deadlock:
      =============================
      "Finalizer":
      waiting to lock monitor 0x080f2038 (object 0xceb8ef08, a org.apache.derby.impl.store.raw.data.StoredPage),
      which is held by "main"
      "main":
      waiting to lock monitor 0x082b5ef8 (object 0xceb98fe8, a org.apache.derby.impl.store.raw.data.BaseContainerHandle),
      which is held by "Finalizer"

      The deadlock is highly intermittent. In many cases the test pass, and when it fails it is mostly with a different symptom than a deadlock (assert error or an IOException / SQLException).
      The problems seem to be triggered by using Clobs, but I don't know if it may be triggered in other environments as well.

      It is likely that DERBY-3844 describes the assert caused by the same underlying issue.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            kristwaa Kristian Waagan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment