[
https://issues.apache.org/jira/browse/DIRAPI-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662503#comment-13662503
]
Emmanuel Lecharny commented on DIRAPI-140:
------------------------------------------
Weirder and weirder... We do receive an AbandonRequest from the client, which
cause the cursor to be closed :
in DefaultClosureMonitor :
public final void close( final Exception cause )
{
// state check needed to "try" not to overwrite exception (lack of
// synchronization may still allow overwriting but who cares that much
if ( !closed )
{
cause.printStackTrace();
And the trace is :
org.apache.directory.api.ldap.model.exception.OperationAbandonedException
at
org.apache.directory.server.ldap.handlers.SearchAbandonListener.requestAbandoned(SearchAbandonListener.java:91)
at
org.apache.directory.api.ldap.model.message.AbstractAbandonableRequest$1.update(AbstractAbandonableRequest.java:95)
at java.util.Observable.notifyObservers(Observable.java:142)
at java.util.Observable.notifyObservers(Observable.java:98)
at
org.apache.directory.api.ldap.model.message.AbstractAbandonableRequest.abandon(AbstractAbandonableRequest.java:70)
at
org.apache.directory.api.ldap.codec.decorators.SearchRequestDecorator.abandon(SearchRequestDecorator.java:1079)
at
org.apache.directory.server.ldap.LdapSession.abandonOutstandingRequest(LdapSession.java:266)
at
org.apache.directory.server.ldap.handlers.request.AbandonRequestHandler.handle(AbandonRequestHandler.java:47)
at
org.apache.directory.server.ldap.handlers.request.AbandonRequestHandler.handle(AbandonRequestHandler.java:33)
at
org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:207)
at
org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:56)
at
org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:221)
at
org.apache.directory.server.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:217)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:690)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:417)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:47)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:765)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:74)
at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
at
org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.runTask(UnorderedThreadPoolExecutor.java:474)
at
org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.run(UnorderedThreadPoolExecutor.java:428)
at java.lang.Thread.run(Thread.java:680)
> Test ClientSearchRequestTest.testSubDn() fails
> ----------------------------------------------
>
> Key: DIRAPI-140
> URL: https://issues.apache.org/jira/browse/DIRAPI-140
> Project: Directory Client API
> Issue Type: Bug
> Environment: Apache Maven 3.0.5
> (rNON-CANONICAL_2013-02-25_10-23_root; 2013-02-25 11:23:59+0100)
> Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.9.2-1-arch", arch: "amd64", family: "unix"
> Reporter: Stefan Seelmann
>
> In trunk the test ClientSearchRequestTest.testSubDn (module ldap-client-test)
> fails quite often. When adding a for loop around the test code it fails after
> 1-10 executions. The first search works always, but the second search which
> uses the SearchRequest object sometimes doesn't contain a result and
> searchCursor.next() is false. Please note that I'm not sure if that is a pb
> in client or in the server.
--
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
