Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <12333324.58221272465634922.JavaMail.jira@thor>
Date: Wed, 28 Apr 2010 10:40:34 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1966) NetworkServer startup can take 50+
 seconds if a client holds an open connection to the previous server booted
 within the same vm
In-Reply-To: <4769997.1161057514893.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861816#action_12861816 ] 

Kristian Waagan commented on DERBY-1966:
----------------------------------------

Unable to reproduce on OpenSolaris with the procedure described above.
Is this a Windows-only bug, or has it been observed on another operating system too?

> NetworkServer startup can take 50+ seconds if a client holds an open connection to the previous server booted within the same vm
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1966
>                 URL: https://issues.apache.org/jira/browse/DERBY-1966
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.3.1.4
>         Environment: Windows XP - IBM JVM 1.4.2
>            Reporter: Daniel John Debrunner
>
> Seen when a client in the same jvm held a open connection to a previously booted network server within the same jvm.
> Order would be:
> boot server
> client connect to server (hold onto connection and don't close)
> shutdown server
> boot server  <<<<<------ this boot will take 50+ seconds

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