[
http://issues.apache.org/jira/browse/DIREVE-340?page=comments#action_12365575 ]
Simon Temple commented on DIREVE-340:
-------------------------------------
The problem is with ProtocolCodecFactoryImpl in
org.apache.directory.server.ldap.LdapProtocolProvider
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:
asn.1.berlib.provider=org.apache.ldap.common.codec.TwixProvider
> Connecting to embedded server via LDAP generates log warnings
> -------------------------------------------------------------
>
> Key: DIREVE-340
> URL: http://issues.apache.org/jira/browse/DIREVE-340
> 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 binaries.
> 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 krb5Key
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
