[
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.
