[
https://issues.apache.org/jira/browse/DERBY-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner resolved DERBY-3514.
------------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
Assignee: Daniel John Debrunner
Revision: 634865 closes the client socket for network server commands in all
situations.
> SecureServerTest failing with timeout waiting for the network server to start
> only when run in derbynet._Suite
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3514
> URL: https://issues.apache.org/jira/browse/DERBY-3514
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Regression Test Failure
> Affects Versions: 10.4.0.0
> Environment: IBM 1.5 windows
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.4.0.0
>
>
> Running the test by itself shows no problems.
> From some debugging it seems the spawned network server (separate jvm) is
> coming up correctly and listening on the right address, however the pings to
> see if it started are never seen by the ClientThread. I checked the timing
> and they do overlap.
> The server address is the wildcard address 0.0.0.0.
> If a server is listening to localhost:1527 then another server fails to start
> if it is listening to 0.0.0.0:1527, I wondered if it would start on the real
> address and just wait for the loopback to become free.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
