[ http://issues.apache.org/jira/brows...VE-256?page=all ]

Alex Karasulu resolved DIREVE-256:
----------------------------------

Resolution: Fixed

Applied and committed patch in revision 291232 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=291232

Also added new test case to apache-server main in commit 291234 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=291234

> Extended operation causes client to hang
> ----------------------------------------
>
>          Key: DIREVE-256
>          URL: http://issues.apache.org/jira/browse/DIREVE-256
>      Project: Directory Server
>         Type: Bug
>   Components: protocol
>     Versions: 0.9.3, 0.9.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>     Priority: Minor
>  Attachments: UnknownExtendedOperationTest.java, patch_DIREVE-256.txt
>
> If a client calls an arbitrary extended operation, the server (namely the 
ExtendedHandler) throws a NotImplementedException. After this, the call of t
he client blocks, and the client hangs.
> I suggest to change the handler to simply send an error code 2 (LDAP_PROTO
COL_ERROR) with message "Unrecognized extended operation" back to the client
. This is the expected behavior if an extended operation is not supported by
 the server.
> Attached you find a test case, which demands an always unknown extended operation 
(OID=1.1) and checks the result. Error code 2 leads to a CommunicationException in J
NDI. I have tested this with several LDAP server implementations, behavior was alway
s a
s expected.
> I have also attached a patch, which changes the ExtendedHandler to behave like des
cribed above. Not a big thing, but it leads to compliant behavior for extended ops, 
even if we do not have any in place yet.

--
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 ]