[ http://issues.apache.org/jira/brows...ge=3Dcomments#=
action_12330263 ]=20

J=C3=A9r=C3=B4me Baumgarten commented on DIRSNICKERS-108:
-----------------------------------------------

Actually the patch I sent corrects the issue for positive values, I tried i=
t and it does the job for values over 128. I checked it with my LDAP proxy =
(my running test proxy has served so far 544 messages to the same client / =
same connection).

I actually tracked that bug down by adding traces to the LdapMessageGrammar=
class (incoming int values are correctly decoded and 128 is coded as "0x00=
0x80" as expected) but the decoding was incorrectly dealing with high bit =
set to 1, "0x80" was sent back, a value that the clients decode as -128 mak=
ing it still waiting to the answer to message +128.

J=C3=A9r=C3=B4me

> Wrong int encoding in Value
> ---------------------------
>
>          Key: DIRSNICKERS-108
>          URL: http://issues.apache.org/jira/browse/DIRSNICKERS-108
>      Project: Directory ASN1
>         Type: Bug
>   Components: BER Runtime
>     Reporter: J=C3=A9r=C3=B4me Baumgarten
>     Assignee: Emmanuel Lecharny
>     Priority: Blocker
>  Attachments: Value.patch
>
> Hi,
> Encoding is buggy for int value in the org.apache.asn1new.ber.tlv.Value c=
lass. The affected methods are :
> * public static int getNbBytes( int value )
> * public static byte[] getBytes( int value )
> Regards,
> J=C3=A9r=C3=B4me

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]