On Mon, Mar 7, 2011 at 10:14 AM, Hasini Gunasinghe <has...@wso2.com> wrote:
>
>
> On Thu, Mar 3, 2011 at 10:50 PM, Amila Jayasekara <ami...@wso2.com> wrote:
>>
>>
>> On Wed, Mar 2, 2011 at 8:43 PM, Hasini Gunasinghe <has...@wso2.com> wrote:
>>>
>>> Hi,
>>> Yes, I too did not get above error message from a latest build from trunk
>>> (from IS or ESB), instead, I only see an unnecessary INFO log as below:
>>>
>>> [2011-03-02 10:29:59,072] INFO
>>> {org.apache.directory.server.ldap.handlers.LdapRequestHandler} - ignoring
>>> the message
>>> org.apache.directory.shared.ldap.message.UnbindRequestImpl@b8f305e3 received
>>> from null session
>>> I checked in apacheds source code, it is being printed by a following
>>> code segment:
>>> if( ldapSession == null )
>>> {
>>> // in some cases the session is becoming null though the
>>> client is sending the UnbindRequest
>>> // before closing
>>> LOG.info( "ignoring the message {} received from null
>>> session", message );
>>> return;
>>> }
>>> Following is what I heard about the possible cause for such a log from
>>> apacheds-user's list:
>>> "If your client disconnect immediately after having sent an
>>> UnbindRequest, the session will be null, as the disconnection will be
>>> processed faster than the UnbindRequest.
>>>
>>> You can ignore the message, it's an INFO level log."
>>
>> I also see this message from apacheds user list. It seems we can ignore
>> the message. Maybe we can get rid of the annoyance by suppressing the log
>> level to WARNING, for org.apache.directory.server.ldap.handlers.
>>
>> Also i am not sure how an unbind request is originating from our LDAP user
>> manager code (Hope you comment all the places where we close the context).
>
> looking further into this:
> I connected IS (both trunk and released version) to an external ApacheDS
> LDAP, and in their console also, I see a similar continuous warning log
> after logging into management console.
> [22:39:53] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] -
> Null LdapSession given to cleanUpSession.
> [22:39:53] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] -
> Null LdapSession given to cleanUpSession.
> I guess this is corresponding to the above INFO log we saw in carbon server
> console, with embedded-ldap.
> I just wrote a separate sample code that connects to external LDAP and does
> queries. There, above messages do not appear unless ldapcontext.close is
> executed.
> So may be there is a place we can fix in user-core to avoid above messages,
> which I could not exactly identify yet.
> According to the references [1,2,3] we can ignore this also.
> So for now, shall we add the log4j property to log4j file in carbon/core to
> get rid of the INFO messages in carbon console?
+1. Please do this in all log4j.properties files.
Thanks
AmilaJ
> Please let me know if there is any objections.
> [1]http://osdir.com/ml/users/2011-03/msg00381.html
> [2]http://www.mail-archive.com/users@directory.apache.org/msg02348.html
> [3]https://issues.apache.org/jira/browse/DIRSERVER-1432
> Thanks,
> Hasini.
>
>>
>>
>>>
>>> In the user-core code, even though I commented out all the places where
>>> ldap context is closed, still this log is printed.
>>> So I could not find a way to get rid of it yet. I will look more into
>>> it.
>>> Please let me know if you have an idea about the cause.
>>> On a side note, when I checked in ESB, I did not see any logs printed by
>>> ApacheDS component, and may be because it is not included in
>>> log4j.properties file of ESB. In log4j.properties files of IS and AS(I
>>> checked only AS additionally), logs from apacheds component are enabled. Is
>>> there any reason why it is not enabled in ESB?
>>
>> It seems ESB is using a different log4j.properties file than that is in
>> the core/distribution/carbon-home/lib/log4j.properties file. AS and IS is
>> using the log4j.properties file in core/distribution/carbon-home/lib/ and it
>> has the apacheds specific log properties. Since apacheds is becoming the
>> user store of ESB also we also need to add properties in
>> core/distribution/carbon-home/lib/log4j.properties to ESB log4j.properties
>> (products/esb/modules/distribution/src/main/conf/log4j.properties) file.
>>
>> Thanks
>> AmilaJ
>>
>>>
>>> Thanks,
>>> Hasini.
>>> On Tue, Mar 1, 2011 at 9:03 PM, Hasini Gunasinghe <has...@wso2.com>
>>> wrote:
>>>>
>>>> Sure.. I will look into it. At the moment, I only have the latest code
>>>> of user-core(where I do not get this). So I will get a complete update from
>>>> trunk and check this.
>>>>
>>>> On Tue, Mar 1, 2011 at 6:51 PM, Prabath Siriwardana <prab...@wso2.com>
>>>> wrote:
>>>>>
>>>>> Hi Hasini,
>>>>> Can you please have a look.. Login to the console and click on some
>>>>> menu items.. [from the latest trunk]
>>>>> [2011-03-01 18:49:03,404] INFO
>>>>> {org.apache.directory.server.core.authn.AuthenticationInterceptor} -
>>>>> Cannot
>>>>> bind to the server
>>>>> [2011-03-01 18:49:03,404] ERROR
>>>>> {org.apache.directory.server.ldap.handlers.LdapRequestHandler} - ERR_732
>>>>> Cannot process a Request while binding
>>>>> [2011-03-01 18:49:03,405] ERROR
>>>>> {org.apache.directory.server.ldap.handlers.LdapRequestHandler} - ERR_732
>>>>> Cannot process a Request while binding
>>>>> [2011-03-01 18:49:03,406] ERROR
>>>>> {org.apache.directory.server.ldap.handlers.LdapRequestHandler} - ERR_732
>>>>> Cannot process a Request while binding
>>>>> --
>>>>> Thanks & Regards,
>>>>> Prabath
>>>>>
>>>>> http://blog.facilelogin.com
>>>>> http://RampartFAQ.com
>>>>>
>>>>> _______________________________________________
>>>>> Carbon-dev mailing list
>>>>> Carbon-dev@wso2.org
>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>
>>>
>>
>
>
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
