Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 30 Apr 2009 17:02:00 +0200 (CEST)
From: jfmelian@free.fr
To: users@directory.apache.org
Message-ID: 
 <240717655.3826241241103720505.JavaMail.root@zimbra3-e1.priv.proxad.net>
In-Reply-To: 
 <1361642134.3825801241103556360.JavaMail.root@zimbra3-e1.priv.proxad.net>
Subject: Re: [Apache DS] Null LdapSession given to cleanUpSession
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


This exception occurs many times but I don't know the reason.
I think this also happens at disconnect but not systematically.
I have turn on the pooling connection for SSL.
  -Dcom.sun.jndi.ldap.connect.pool.protocol=3D"plain ssl"


30.04.2009 16:55:08.623 [WARN ] AbandonableRequest with messageId 2 not fou=
nd in outstandingRequests. (LdapSession.java, line 214, class org.apache.di=
rectory.server.ldap.LdapSession)
30.04.2009 16:55:08.639 [WARN ] The PDU has been fully decoded but there ar=
e still bytes in the buffer. (Asn1Decoder.java, line 814, class org.apache.=
directory.shared.asn1.ber.Asn1Decoder)
30.04.2009 16:55:08.639 [WARN ] AbandonableRequest with messageId 2 not fou=
nd in outstandingRequests. (LdapSession.java, line 214, class org.apache.di=
rectory.server.ldap.LdapSession)
30.04.2009 16:55:08.639 [WARN ] Unexpected exception forcing session to clo=
se: sending disconnect notice to client. (LdapProtocolHandler.java, line 21=
5, class org.apache.directory.server.ldap.LdapProtocolHandler)
org.apache.mina.core.write.WriteToClosedSessionException
=09at org.apache.mina.filter.ssl.SslFilter.exceptionCaught(SslFilter.java:4=
95)
=09at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextExcepti=
onCaught(DefaultIoFilterChain.java:480)
=09at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1100(Def=
aultIoFilterChain.java:48)
=09at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.exc=
eptionCaught(DefaultIoFilterChain.java:797)
=09at org.apache.mina.core.filterchain.IoFilterAdapter.exceptionCaught(IoFi=
lterAdapter.java:112)
=09at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextExcepti=
onCaught(DefaultIoFilterChain.java:480)
=09at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireExceptionCa=
ught(DefaultIoFilterChain.java:468)
=09at org.apache.mina.core.polling.AbstractPollingIoProcessor.clearWriteReq=
uestQueue(AbstractPollingIoProcessor.java:532)
=09at org.apache.mina.core.polling.AbstractPollingIoProcessor.removeNow(Abs=
tractPollingIoProcessor.java:479)
=09at org.apache.mina.core.polling.AbstractPollingIoProcessor.remove(Abstra=
ctPollingIoProcessor.java:458)
=09at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(Ab=
stractPollingIoProcessor.java:57)
=09at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run=
(AbstractPollingIoProcessor.java:872)
=09at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnabl=
e.java:65)
=09at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source=
)
=09at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
=09at java.lang.Thread.run(Unknown Source)
30.04.2009 16:55:08.733 [WARN ] Null LdapSession given to cleanUpSession. (=
LdapProtocolHandler.java, line 108, class org.apache.directory.server.ldap.=
LdapProtocolHandler)


----- Mail Original -----
De: "Alex Karasulu" <akarasulu@gmail.com>
=C3=80: users@directory.apache.org
Envoy=C3=A9: Jeudi 23 Avril 2009 18h32:31 GMT +01:00 Amsterdam / Berlin / B=
erne / Rome / Stockholm / Vienne
Objet: Re: [Apache DS] Null LdapSession given to cleanUpSession

I'd have to investigate the connection handling code to say for sure but I
think this may be coming from processing an abandon request.  Let me
explain.

The client sends an abandon request just before it drops the connection
(socket).  Then the server gets the abandon message and tries to close the
socket on it's end.  But before it can do that, the MINA handler code
already cleans up the MINA session.  So when the AbandonRequest handler
picks up and looks up the LdapSession object it does not see it.  This is
the warning message you're getting.  So the message is harmless as you
observed.

HTH

On Thu, Apr 23, 2009 at 11:06 AM, <jfmelian@free.fr> wrote:

>
> little more informations :
>
> SSL connections.
>
> With this sample, i have the warning message at each context.close().
>
> InitialLdapContext context =3D initializeLdapContext(ldapEnv);
> context.close();
>
>
> ----- Mail Original -----
> De: jfmelian@free.fr
> =C3=80: users@directory.apache.org
> Envoy=C3=A9: Jeudi 23 Avril 2009 16h50:57 GMT +01:00 Amsterdam / Berlin /=
 Berne
> / Rome / Stockholm / Vienne
> Objet: [Apache DS] Null LdapSession given to cleanUpSession
>
>
> Hi
>
> I have embbeded an Apache DS : trunck revision 767919
>
> I've got a lot of warning messages when jndi clients request the server :
> connect + search + close
> It seems working despite warning messages.
>
> How can I avoid this ?
>
> 23.04.2009 16:18:11.009 [WARN ] Null LdapSession given to cleanUpSession.
> (LdapProtocolHandler.java, line 108, class
> org.apache.directory.server.ldap.LdapProtocolHandler)
>
>
>
>
>


--=20
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org