[
https://issues.apache.org/jira/browse/DIRAPI-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526509#comment-13526509
]
Emmanuel Lecharny commented on DIRAPI-83:
-----------------------------------------
There were a wrong log level (WARNING instead of DEBUG) here. This is supposed
to be an informative message, when more than one LdapMessage is contained into
a PDU. Nothing wrong, just a scarrying warning.
Changed the log level in http://svn.apache.org/viewvc?rev=1418379&view=rev
> Debug logging causes never ending loop whn decoding messages
> ------------------------------------------------------------
>
> Key: DIRAPI-83
> URL: https://issues.apache.org/jira/browse/DIRAPI-83
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M11
> Environment: Fedora 16 x64, Java 7, OpenLDAP 2.4.26
> Reporter: Sumit Raja
> Priority: Minor
> Fix For: 1.0.0-M12
>
>
> When a lookup for an entry is done with debug enabled the message decoding
> goes into a continuous loop till the search times out. This happens with
> OpenLDAP when the "ERR_00043_REMAINING_BYTES_FOR_DECODED_PDU The PDU has been
> fully decoded but there are still bytes in the buffer." error occurs
> I don't have a test case but a simple LdapConnection.lookup with debug
> logging enabled causes this.
> The fix looks pretty straightforward - the actual offending code is in
> org.apache.directory.shared.ldap.codec.protocol.mina.LdapProtocolDecoder.decode().
> The buffer.position is set(:134) and reset(:145) without a mark being set.
> The workaround is to turn off debug logging for the "org.apache.directory"
> logger
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
