[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648611#action_12648611
]
Myrna van Lunteren commented on DERBY-1465:
-------------------------------------------
I committed the latest patch with revision 718616.
Now - this issue has 'release note needed' flagged, but I'm not certain why
It does need to be in the release notes, of course, but does this need a
special explanation? It seems to me, that either way, the server is not started
(as it's already started), and we're still also printing the exceptions, so I
have some trouble seeing how this could affect existing applications. Any
thoughts?
> 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.diff3, 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.
