[
https://issues.apache.org/jira/browse/DERBY-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707006#action_12707006
]
Kathey Marsden commented on DERBY-1432:
---------------------------------------
Is this still a problem with the JUnit test NSInSameJVMTest?
> derbynetmats/NSinSameJVM.java fails to run due to Warning
> "UnknkownHostException: dyn<xx>" on Linux with DHCP generated hostname
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1432
> URL: https://issues.apache.org/jira/browse/DERBY-1432
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, Test
> Affects Versions: 10.1.2.1, 10.1.3.1
> Environment: Linux Operating Systems using DHCP IP address *and*
> hostname generation
> Reporter: Stan Bradbury
> Priority: Minor
>
> The test derbynetmats/NSinSameJVM.java reports that the Network Server failed
> to start and aborts on Linux machines that use DHCP to generate a hostname
> that reflects the generated IP address (e.g. hostname like: dyn<xx> where
> <xx> is the IP address string like 216101116144). Network server does, in
> fact, start.
> derby.log entry:
> Warning: UnknkownHostException: dyn<someIP>: dyn<someIP>.
> Server is ready to accept connections on port <some-port>.
> derbyall.sum entry:
> > FAIL Network Server did not start
> Test Failed.
> *** End: NSinSameJVM jdk1.5.0_07 DerbyNetClient derbynetmats:derbynetmats
> 2006
> Appears to be related to reported JVM issue: Bug ID: 4665037
> Synopsis InetAddress.getLocalHost() ambiguous on Linux systems
> see: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665037
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
