[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652479#action_12652479
]
Myrna van Lunteren commented on DERBY-1465:
-------------------------------------------
I have not seen the hang anymore on my own machine; however, it seems that
since my check-in of November 18, tests are hanging regularly in nightlies on
windows, see:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/index.html
I don't understand the hang, so I don't have a solution...
I have two approaches currently;
1. check in the latest patch
2. back out my first change
Or is there someone who can spot a mistake in the (patch) code?
> 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.diff4, DERBY-1465.diff5,
> 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.
