[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659851#action_12659851
]
Myrna van Lunteren commented on DERBY-1465:
-------------------------------------------
Well, it seems there still is a hang.
With ibm142 on another machine than where I ran my tests before, suites.All is
hanging (it's been at it for about 11 hours, should take about 5 hours on this
particular machine) - the test run seems wedged currently in
testReplication_Local_existingTestsAsReplLoad.
I'll back out my changes...(again). Apologies for the trouble.
> 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
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1465.diff3, DERBY-1465.diff4, DERBY-1465.diff5,
> DERBY-1465.diff6, DERBY-1465.diff7, DERBY-1465.diff8, DERBY-1465_diff.txt,
> DERBY-1465_diff.txt, DERBY-1465_stat.txt, DERBY-1465_stat.txt,
> releaseNote.html, releaseNote.html, 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.
