You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2012/10/01 20:17:09 UTC
[jira] [Commented] (DERBY-5941) Assert failure in
jdbcapi.InvalidLDAPServerAuthenticationTest.testInvalidLDAPServerConnectionError
[ https://issues.apache.org/jira/browse/DERBY-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467038#comment-13467038 ]
Kristian Waagan commented on DERBY-5941:
----------------------------------------
The test still fails.
Looks like there are two failure modes:
a) UnknownHostException
b) Connection refused : javax.naming.CommunicationException: noSuchServer.invalid:389 [Root exception is java.net.ConnectException: Connection timed out]
Does anyone know what causes the JVM to choose either of them?
Is it something on the OS level, for instance in the network stack?
(this is a somewhat specialized Ubuntu Linux, I think its for the Calxeda Highbank platform)
In general I don't see a big problem in considering both exceptions as expected, but it would be nice to know why the error condition gives rise to different exceptions (i.e. JVM, OS, or something else).
> Assert failure in jdbcapi.InvalidLDAPServerAuthenticationTest.testInvalidLDAPServerConnectionError
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-5941
> URL: https://issues.apache.org/jira/browse/DERBY-5941
> Project: Derby
> Issue Type: Bug
> Components: Test
> Environment: ARM processor, Ubuntu Linux, Java SE Embedded 1.7.0_06-b24
> Reporter: Kristian Waagan
> Priority: Minor
> Attachments: derby-5941-1a-rfc2606.diff
>
>
> The test jdbcapi.InvalidLDAPServerAuthenticationTest.testInvalidLDAPServerConnectionError fails in an assert:
> assertTrue(se.getMessage().indexOf("java.net.UnknownHostException")>1)
> The error reported is:
> Connection refused : javax.naming.CommunicationException: noSuchServer:389 [Root exception is java.net.ConnectException: Connection timed out]
> The failure is reproducible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira