[ https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498057
]
Kathey Marsden commented on DERBY-1465:
---------------------------------------
Thanks Dan for looking.
I don't think it should be a daemon thread if I understand the concept of a daemon thread
correctly. I don't want the jvm to exit while this thread is running. I'll add comments
for serverStartComplete.
> 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
> Fix For: 10.3.0.0
>
> 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.
|