You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/10/06 18:25:35 UTC
[jira] Created: (DIRSERVER-1563) The server does not accept message
bigger than 80Kb
The server does not accept message bigger than 80Kb
---------------------------------------------------
Key: DIRSERVER-1563
URL: https://issues.apache.org/jira/browse/DIRSERVER-1563
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.7
Reporter: Emmanuel Lecharny
Priority: Blocker
Fix For: 2.0.0-RC1
As I was trying to send a schema modification will 1400 ObjectClasses in it, the ModifyMessage which was created was 350Kb big, and it wasn't correctly swallowed by the server.
The analysis proved that once the first 80Kb were read (the incoming buffer is 80Kn big), the next block of data was generating a Protocol_error. This was due to the fact that the message container was reinitialized when the new block of data arrived.
This is bad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-1563) The server does not accept
message bigger than 80Kb
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1563.
------------------------------------------
Resolution: Fixed
Fixed with http://svn.apache.org/viewvc?rev=1005086&view=rev
We now don't reinitialize the LdapMessageContainer, it's simply reused.
> The server does not accept message bigger than 80Kb
> ---------------------------------------------------
>
> Key: DIRSERVER-1563
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1563
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.7
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 2.0.0-RC1
>
>
> As I was trying to send a schema modification will 1400 ObjectClasses in it, the ModifyMessage which was created was 350Kb big, and it wasn't correctly swallowed by the server.
> The analysis proved that once the first 80Kb were read (the incoming buffer is 80Kn big), the next block of data was generating a Protocol_error. This was due to the fact that the message container was reinitialized when the new block of data arrived.
> This is bad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.