[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-1465:
--------------------------------------
Attachment: DERBY-1465hangibm15_12_29_08.txt
Attaching a java core dump of the test run that hung with ibm15.
I only now noticed that there were a number (15 to 20) of Errors both with
ibm142 and ibm15, starting with the fixture testGrantAndRevoke. But of course
there is no list of these at the bottom of the output, because I killed the
test run...
Unfortunately, there is no 'fail' directory, not sure why not...
> 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,
> DERBY-1465hangibm142_12_29_08.txt, DERBY-1465hangibm15_12_29_08.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.
