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 16:02:07 UTC
[jira] [Updated] (DERBY-5941) Assert failure in
jdbcapi.InvalidLDAPServerAuthenticationTest.testInvalidLDAPServerConnectionError
[ https://issues.apache.org/jira/browse/DERBY-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5941:
-----------------------------------
Attachment: derby-5941-1a-rfc2606.diff
I committed patch 1a to trunk with revision 1392338 just to rule out that the test fails because the specified host actually exists. I added ".invalid" to the host name as suggested by RFC 2606.
I will rerun suites.All on the ASF ARM cluster (https://builds.apache.org/job/Derby-trunk-suites.All-ARM)
> 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