| |
How does client discard unwanted results in process? |
|
|
Subject: How does client discard unwanted results in process?
Author: SteveHB
In response to: OperationNotSupportedException
Posted on: 09/07/2006 07:48:58 PM
A sequence of paged search requests is abandoned by the client:
sending a search request containing a pagedResultsControl with the size set to zero (pageSize=0).
sending an LDAP Abandon operation to abandon one paged search request in progress, but this is discouraged.
walking away without informing server, definitely this is strongly discouraged.
>
> On 09/06/2006 01:14:14 PM SteveHB wrote:
If you run the above client against LDAP servers which do not support Paged Results Control, most likely you are going to get error message similar like this.
javax.naming.OperationNotSupportedException from SunOne Directory Server:
javax.naming.OperationNotSupportedException: [LDAP: error code 12 - Unavailable Critical Extension];
remaining name 'dc=mydomain,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3045)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1808)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1731)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321)
at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
References:
|
|
|
|
