You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/10/17 05:58:34 UTC
[jira] Created: (DERBY-1966) NetworkServer startup can take 50+
seconds if a client holds an open connection to the previous server booted
within the same vm
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: http://issues.apache.org/jira/browse/DERBY-1966
Project: Derby
Issue Type: Bug
Components: Network Server
Affects Versions: 10.3.0.0
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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475194 ]
Daniel John Debrunner commented on DERBY-1966:
----------------------------------------------
the interaction between NetworkServerControlImpl and DRDAServerStarter is overly complex and convoluted.
It results in the method startNetworkServer in NetworkServerControlImpl being called twice on two different instances of NetworkServerControlImpl. Strangely enough both are required (but it's not obvious why from casual reading,
it is due to some ordering issues) and it's further confused by the fact that the method startNetworkServer does not
in fact start the server. Not sure of its exact role :-)
Separating out some of the code in DRDAServerStarter into separate methods (and adding comments) allows
a more natural interface between these two classes. Will submit a patch for this soon. Probably does not solve the 60+
second issue, but makes the code more understandable.
> 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.0.0
> 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.
[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
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475200 ]
Bryan Pendleton commented on DERBY-1966:
----------------------------------------
I completely agree with your observations regarding the complexity. Deepa and Knut Anders and I wrestled with this code a bunch as part of DERBY-1219 and DERBY-1326. See e.g. https://issues.apache.org/jira/browse/DERBY-1326#action_12415277
I'm not sure if any of the comments in those issues are of much help; just wanted to chime in and agree with your comments.
> 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.0.0
> 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.
[jira] Updated: (DERBY-1966) NetworkServer startup can take 50+
seconds if a client holds an open connection to the previous server booted
within the same vm
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-1966:
--------------------------------------
Urgency: Normal
Bug behavior facts: [Performance]
Triaged for 10.5.2.
> 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.
[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
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475211 ]
Daniel John Debrunner commented on DERBY-1966:
----------------------------------------------
Thanks Bryan, I see some of the same thoughts came up, I'll look through them in more detail before submitting a patch.
> 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.0.0
> 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.
[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
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.
[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
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1966?page=comments#action_12450772 ]
Daniel John Debrunner commented on DERBY-1966:
----------------------------------------------
Also occurs if a reference to the NetworkServerControl used to start the server is kept.
Can reproduce this by not nulling out networkServerController in the tearDown method of NetworkServerTestSetup and then run a JUnit test that uses the decorator repeatably within the same JVM. Using the MathTrigFunctionsTest in the swingui (just keep clicking run once the test completes) I saw about 2 failures to start the network server every 15 runs.
> 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: http://issues.apache.org/jira/browse/DERBY-1966
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.3.0.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira