Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <10761370.1189936292442.JavaMail.jira@brutus>
Date: Sun, 16 Sep 2007 02:51:32 -0700 (PDT)
From: "Alexey Petrenko (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-4634) [classlib][swing]SplitPane triggers
 the deadlock in AbstractDocument$ReadWriteLock
In-Reply-To: <1414794.1187175450562.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Petrenko closed HARMONY-4634.
------------------------------------


> [classlib][swing]SplitPane triggers the deadlock in AbstractDocument$ReadWriteLock
> ----------------------------------------------------------------------------------
>
>                 Key: HARMONY-4634
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4634
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: Win32
>            Reporter: Alexey Petrenko
>            Assignee: Alexey Petrenko
>         Attachments: HARMONY-4634-ReadWriteLock.patch
>
>
> We need a better patch for HARMONY-4624.
> Here is a description from HARMONY-4624:
>  Dead lock possibilities are seen in the synchronized metnods of AbstractDocument$ReadWriteLock.
>         public final synchronized void readLock() {
>             final Thread thread = Thread.currentThread();
>             if (writer != thread) {
>                 while (writerCount > 0) {
>                     try { wait(); }
>                     catch (final InterruptedException e) { }
>                 }
>             }
>             readers.add(thread);
>         }
>  Waiting in synchronized methods (requires another synchronized method to wakeup it) likely just dies there.
>  Multithreaded SplitPane application triggers the possibility. One thread can operate at the texts of the LeftComponent, thus in a critical section after setting writercount(writeLock()). The other thread can operate at the rightComponent, then call the readLock() of LeftComponent via layout managment and just waits there.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.