[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
----------------------------------
Attachment: DERBY-1465_diff.txt
Patch for this issue. start() will now wait until the server has been started.
It will wait until just before the server started message prints to return and
will throw an exception if one occurred. One possible problem with the
existing. One possible problem with the existing code is that it prints
"server started" before launching the client thread. If that needs to be
moved, I will log it as a separate issue.
derbynetmats, derbynetclientmats and suites.All passed.
I'll commit this late today if I hear no comments, but I would appreciate if
someone would take a look.
Thanks
Kathey
> NetworkServerControl.start() should throw an exception and not just print
> exceptions if the server fails to start
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1465
> URL: https://issues.apache.org/jira/browse/DERBY-1465
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.1.2.1
> Reporter: Kathey Marsden
> Assigned To: Kathey Marsden
> Priority: Minor
> Attachments: DERBY-1465_diff.txt, DERBY-1465_diff.txt,
> DERBY-1465_stat.txt, DERBY-1465_stat.txt
>
>
> NetworkServerControl.start() will not throw an exception if another server
> is already running on the same port. I am not sure but think perhaps this
> was changed at one point to accomodate the derby.drda.startNetworkServer
> property so that the embedded server could continue to boot even if the
> network server failed to start, but I think this is wrong for normal usage.
> http://www.nabble.com/Questions-about-Network-Server-API-Behavior-p5055814.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
