directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Temple (JIRA)" <>
Subject [jira] Commented: (DIREVE-340) Connecting to embedded server via LDAP generates log warnings
Date Wed, 08 Feb 2006 15:13:38 GMT
    [ ] 

Simon Temple commented on DIREVE-340:

The problem is with ProtocolCodecFactoryImpl in

If you don't specify the name of the Provider.BERLIB_PROVIDER then no environment is given
to the provider and hence java.naming.ldap.attributes.binary is null!

As a workaround I specify:


> Connecting to embedded server via LDAP generates log warnings
> -------------------------------------------------------------
>          Key: DIREVE-340
>          URL:
>      Project: Directory Server
>         Type: Improvement
>   Components: server main
>     Versions: 1.0-RC1
>  Environment: JBoss 3.2, JDK 1.4.2_10
>     Reporter: Simon Temple
>     Assignee: Alex Karasulu
>     Priority: Minor

> I get this each time an LDAP client connects:
> 2006-02-06 11:14:14,978 WARN [org.apache.ldap.common.message.MessageDecoder](IoThreadPool-2)
Could not find java.naming.ldap.attributes.binary key in environment. Using empty set for
> java.naming.ldap.attributes.binary is iset in the envrionment when the server starts.
 It is set to:
> photo personalSignature audio jpegPhoto javaSerializedData userPassword userCertificate
cACertificate authorityRevocationList certificateRevocationList crossCertificatePair x500UniqueIdentifier

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message