Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <14139549.435751285649674171.JavaMail.jira@thor>
Date: Tue, 28 Sep 2010 00:54:34 -0400 (EDT)
From: "Wendy Feng (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Created: (HARMONY-6663) Time-consuming operation with lock
 held in ServerSocketChannelImpl.java
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Time-consuming operation with lock held in ServerSocketChannelImpl.java 
------------------------------------------------------------------------

                 Key: HARMONY-6663
                 URL: https://issues.apache.org/jira/browse/HARMONY-6663
             Project: Harmony
          Issue Type: Bug
          Components: Classlib
    Affects Versions: 6.0M1
         Environment: Windows XP
            Reporter: Wendy Feng


I found a time-consuming operation with lock held in modules/nio/src/main/java/common/org/apache/harmony/nio/internal/ServerSocketChannelImpl.java

public SocketChannel accept() throws IOException {
      ...
            synchronized (acceptLock) {
                    boolean isBlocking = isBlocking();
                    ...
                    do {
                        try {
                            ((ServerSocketAdapter) socket).accept(socketGot,
                                    (SocketChannelImpl) sockChannel);
                            // select successfully, break out immediately.
                            break;
                        } catch (SocketTimeoutException e) {
                            // continue to accept if the channel is in blocking
                            // mode.
                        }
                    } while (isBlocking);
            }
        ...
    }

Thread A executes accept() method, holds a lock on "acceptLock ", but may block at socket.accept() for a long time.
Thread B executes accept(), cannot acquire the lock on "acceptLock ".

Consequence:
Lock contends, significantly downgrade software performance.

I suggest to move the do-while block out of the synchronization block as follow:
public SocketChannel accept() throws IOException {
      ...
            boolean isBlocking = isBlocking();
            synchronized (acceptLock) {   
                    ...
             }
               do {
                        try {
                            ((ServerSocketAdapter) socket).accept(socketGot,
                                    (SocketChannelImpl) sockChannel);
                            // select successfully, break out immediately.
                            break;
                        } catch (SocketTimeoutException e) {
                            // continue to accept if the channel is in blocking
                            // mode.
                        }
                    } while (isBlocking);

        ...
    }


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