08-29-06 06:11 PM
[ http://issues.apache.org/jira/brows...243
1256 ]
Emmanuel Lecharny commented on DIRSERVER-720:
---------------------------------------------
The dn we receive is really invalid ;
0x64 0x6E 0x3A 0x20 0x75 0x69 0x64 0x3D 0x75 0x73 0x65 0x72 0x2E 0x31 0x2C 0
x64 0x63 0x3D 0x65 0x78 0x61 0x6D 0x70 0x6C 0x65 0x2C 0x64 0x63 0x3D 0x63 0x
6F 0x6D
are the bytes for :
dn: uid=user.1,dc=example,dc=com
And the full received PDU is :
30 25
02 01 02
4A 20
64 6E 3A 20 75 69 64 3D 75 73 65 72 2E 31 2C 64 63 3D 65 78 61 6D 70 6C 65 2
C 64 63 3D 63 6F 6D
(d n : u i d = u s e r . 1 , d c
= e x a m p l e , d c = c o m)
the first chars ( "dn: ") should not be there. Ldapdelete command is bugged,
I think.
> Delete operation fails due to decoder failure to properly read DN in reque
st
> --------------------------------------------------------------------------
--
>
> Key: DIRSERVER-720
> URL: http://issues.apache.org/jira/browse/DIRSERVER-720
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: asn1
> Affects Versions: 1.0-RC4
> Environment: SUN JVM 1.5.0_08
> ApacheDS 1.0-RC4-SNAPSHOT
> Reporter: Alex Karasulu
> Assigned To: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.1.0, 1.0-RC4
>
> Attachments: ldifs.tgz
>
>
> Standard delete requests with the OpenLDAP (ldapdelete) client has started
to fail. I'm getting the following stack trace from ApacheDS:
> [20:34:41] ERROR [org.apache.directory.shared.ldap.codec.del.DelRequestGra
mmar] - The DN to delete : dn: uid=user.1,dc=example,dc=com (0x64 0x6E 0x3A 0x20 0x7
5 0x69 0x64 0x3D 0x75 0x73 0x65 0x72 0x2E 0x31 0x2C 0x64 0x63 0x3D 0x65 0x78 0x61 0x
6D 0x70 0x6
C 0x65 0x2C 0x64 0x63 0x3D 0x63 0x6F 0x6D ) is invalid : Bad DN : dn: uid=user.1,dc=example,
dc=com
> [20:34:41] ERROR [org.apache.directory.shared.asn1.ber.Asn1Decoder
] - The PDU is decoded, but we should have had more TLVs
> [20:34:41] WARN [org.apache.directory.server.ldap.LdapProtocolProv
ider$LdapProtocolHandler] - [/127.0.0.1:47133] Unexpected exception forc
ing session to close: sending disconnect notice to client.
> org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.director
y.shared.ldap.message.MessageException: decoder failture: Truncated PDU. Som
e elements are lacking, accordingly to the grammar (Hexdump: 30 05 02 01 03
42 00)
> at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceive
d(ProtocolCodecFilter.java:168)
> at org.apache.mina.common.support.AbstractIoFilterChain.callNextMe
ssageReceived(AbstractIoFilterChain.java:501)
> at org.apache.mina.common.support.AbstractIoFilterChain.access$100
0(AbstractIoFilterChain.java:51)
> at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$
1.messageReceived(AbstractIoFilterChain.java:787)
> at org.apache.mina.filter.ThreadPoolFilter.processEvent(ThreadPool
Filter.java:718)
> at org.apache.mina.filter.ThreadPoolFilter$Worker.processEvents(Th
readPoolFilter.java:474)
> at org.apache.mina.filter.ThreadPoolFilter$Worker.run(ThreadPoolFi
lter.java:429)
> Caused by: org.apache.directory.shared.ldap.message.MessageException: deco
der failture: Truncated PDU. Some elements are lacking, accordingly to the g
rammar
> at org.apache.directory.shared.ldap.message.MessageDecoder.decode(
MessageDecoder.java:231)
> at org.apache.mina.filter.codec.asn1.Asn1CodecDecoder.decode(Asn1C
odecDecoder.java:52)
> at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceive
d(ProtocolCodecFilter.java:157)
> ... 6 more
> I'm also getting the following output (error message) from ApacheDS on the
clientside:
> Delete Result: Invalid DN syntax (34)
> Additional info: The DN to delete : dn: uid=user.1,dc=example,dc=com (0x64 0x6E 0x
3A 0x20 0x75 0x69 0x64 0x3D 0x75 0x73 0x65 0x72 0x2E 0x31 0x2C 0x64 0x63 0x3D 0x65 0
x78 0x61 0x6D 0x70 0x6C 0x65 0x2C 0x64 0x63 0x3D 0x63 0x6F 0x6D ) is invalid
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://iss
ues.apache.org/ji...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ Post a follow-up to this message ]
|