[
https://issues.apache.org/jira/browse/DERBY-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-5941.
---------------------------------------
Resolution: Cannot Reproduce
I am resolving this as Cannot Reproduce, which is a bit of a gamble because I
don't think the LDAP test has been run for a while - and I no longer have an
LDAP server set up to verify this. But it was still running last year and the
last test report/comment on this is older than that.
> 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
> Labels: derby_triage10_10
> 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 was sent by Atlassian JIRA
(v6.2#6252)
