[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641992#action_12641992
]
Myrna van Lunteren commented on DERBY-1465:
-------------------------------------------
Since Bernt has now (see update to DERBY-2412) no plans to complete redesign of
NetworkServerControlImpl, I was thinking it might make sense to revisit this
issue.
However, I am not sure about one of Dan's comments:
" wonder if the code could be modifed slightly to use the old thread, rather
than creating a new thread ... "
I can imagine DRDAServerStarter.boot(...) carrying an additional parameter to
indicate whether to throw an exception or not, is that what was meant? Or is
there another solution?
> 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
> Priority: Minor
> Attachments: DERBY-1465_diff.txt, DERBY-1465_diff.txt,
> DERBY-1465_stat.txt, DERBY-1465_stat.txt, releaseNote.html
>
>
> 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.
