search

vaseems / xmemcached

Automatically exported from code.google.com/p/xmemcached
Apache License 2.0
0 stars 0 forks source link

disabling the slf4j logging for the xmemcached client #239

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. instantiate the client
2. do a put/get cache operation
3. as long as the application is running, heavy debug logs like below are 
printed every second.

12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingquit

12/11/30 20:35:54 DEBUG impl.MemcachedHandler: Check session (%s) is alive,send 
heartbeat
12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingversion

12/11/30 20:35:54 DEBUG impl.Optimizer: Optimieze merge buffer:quit

12/11/30 20:35:54 DEBUG impl.AbstractSession: send buffers:
[
 buffer:position=0,limit=15,capacity=15
]
12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingquit

12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingquit

12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingquit

12/11/30 20:35:54 DEBUG impl.MemcachedHandler: Check session (%s) is alive,send 
heartbeat
12/11/30 20:35:54 DEBUG impl.AbstractSession: After encodingversion

What is the expected output? What do you see instead?

need a way to configure to disable debug logging in production environment 
as this will impact performance.

What version of the product are you using? On what operating system?

xmemcached 1.3.8

Please provide any additional information below.

Original issue reported on code.google.com by meyap...@gmail.com on 30 Nov 2012 at 3:08

GoogleCodeExporter commented 9 years ago 
Hi,please configure your log4j.properties if u are using log4j.

Original comment by killme2...@gmail.com on 8 Jan 2013 at 12:03

GoogleCodeExporter commented 9 years ago

Original comment by killme2...@gmail.com on 8 Jan 2013 at 12:03

GoogleCodeExporter commented 9 years ago 
i got same issue, i have configured the log4j.properties, which level is error, 
but the debug level logs are printed very seconds, heavily affect the 
performance.

Original comment by qingshe...@gmail.com on 23 Sep 2013 at 2:10

GoogleCodeExporter commented 9 years ago 
I am using 1.4.2 and facing the same thing

Original comment by shoaib.k...@gmail.com on 16 Mar 2014 at 7:21

GoogleCodeExporter commented 9 years ago 
Though it's an old post, but just for information, depending on you logger 
implementation, change you logger properties file. I used logback. So, changed 
logback.xml as,
<logger name="net.rubyeye.xmemcached" level="ERROR" />
<logger name="com.google.code.yanf4j" level="ERROR" />

Original comment by mukit...@gmail.com on 21 Jan 2015 at 6:50