Seeing a lot of "Found no validity info for session id" entries in catalina log

240 views
Skip to first unread message

RobZ

unread,
Mar 20, 2014, 11:02:23 AM3/20/14
to memcached-se...@googlegroups.com

Hello,

I am new to this group and seeing these entries in our catalina log files.  (many per second in production)

20-Mar-2014 10:59:44.430 WARNING [tomcat-http--17624] de.javakaffee.web.msm.LockingStrategy.onBackupWithoutLoadedSession An error when trying to load/update validity info.
 java.lang.IllegalStateException: Shutting down
        at net.spy.memcached.MemcachedConnection.checkState(MemcachedConnection.java:824)
        at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:640)
        at net.spy.memcached.MemcachedClient.asyncGet(MemcachedClient.java:841)
        at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1003)
        at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1024)
        at de.javakaffee.web.msm.LockingStrategy.loadSessionValidityInfoForValidityKey(LockingStrategy.java:337)
        at de.javakaffee.web.msm.LockingStrategy.onBackupWithoutLoadedSession(LockingStrategy.java:228)
        at de.javakaffee.web.msm.MemcachedSessionService.backupSession(MemcachedSessionService.java:1031)
        at de.javakaffee.web.msm.RequestTrackingHostValve.backupSession(RequestTrackingHostValve.java:229)
        at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:154)
        at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:151)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
        at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)



We are using RHEL 6.5 and  vfabric-tc-server-standard-2.9.2.RELEASE and Memcached V 1.4.4.

I know that if we turn on sticky, it will go away but need to be non-sticky.  We tried to change lockingMode but to no avail.

we have 4 MemC nodes and here is the context.xml file:

        memcachedNodes="n1:node01:11211,n2:node02:11211,n3:node03:11211,n4:node04:11211"
        enabled="true"
        sticky="false"
        lockingMode="none"
        memcachedProtocol="binary"
        sessionBackupAsync="false"
        sessionBackupTimeout="1000"
        transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory" />


Here is the conf files:

-rw-r--r--. 1 tomcat tomcat 132158 Sep 20 10:54 memcached-session-manager-1.6.3.jar
-rw-r--r--. 1 tomcat tomcat   9116 Sep 20 10:51 memcached-session-manager-tc7-1.6.5.jar
-rw-r--r--. 1 tomcat tomcat 401028 Sep 18  2013 spymemcached-2.8.4.jar
-rw-r--r--. 1 tomcat tomcat 247878 Sep 18  2013 couchbase-client-1.1.4.jar


Any ideas why we are getting this warning all the time?

thanks

Martin Grotzke

unread,
Mar 20, 2014, 1:26:12 PM3/20/14
to memcached-session-manager

Hi,

this sounds as if the memcached connection is being shut down:

"java.lang.IllegalStateException: Shutting down
        at net.spy.memcached.MemcachedConnection.checkState"

Not sure why, perhaps it's related to your infrastructure.

Can you reproduce this issue?

Cheers,
Martin

--

---
You received this message because you are subscribed to the Google Groups "memcached-session-manager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to memcached-session-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RobZ

unread,
Mar 20, 2014, 2:51:23 PM3/20/14
to memcached-se...@googlegroups.com
Thanks for the reply- and yes, it happens all the time.  not sure why the connection to memc nodes would get closed.  Those memcached daemon never stops or hangs..

thanks
Rob

Martin Grotzke

unread,
Mar 20, 2014, 3:10:32 PM3/20/14
to memcached-session-manager

Can you provide a complete sample that allows me to reproduce this?

You could also check/search the spymemcached forum/group to see if s.o. else ran into this issue before.

Cheers,
Martin

RobZ

unread,
Mar 21, 2014, 1:29:18 PM3/21/14
to memcached-se...@googlegroups.com, martin....@googlemail.com
Thank you but we cannot provide a sample at this time.  Is there more logging we can enable?  We have the -vvv flag for memc but didn't know if we can get more info out of  spymemcached.  This warning happens when tomcat is trying to backup the session info to the memc node correct? ..  But we are not seeing many app errors for that..

thanks
Rob
To unsubscribe from this group and stop receiving emails from it, send an email to memcached-session-manager+unsub...@googlegroups.com.

Martin Grotzke

unread,
Mar 22, 2014, 5:54:31 AM3/22/14
to memcached-session-manager

For spymemcached logging check out https://code.google.com/p/spymemcached/wiki/Logging. You should also ask the spymemcached devs regarding this issue.

Cheers,
Martin

Reply all
Reply to author
Forward
0 new messages