search

soonyoung / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

Could not find session in local session map. #166

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
2013-06-07 15:06:40 WARN  de.javakaffee.web.msm.MemcachedSessionService - Could 
not find session in local session map.
java.lang.IllegalArgumentException: The given node id is not part of this list
    at de.javakaffee.web.msm.NodeIdList.getNextNodeId(NodeIdList.java:60)
    at de.javakaffee.web.msm.MemcachedNodesManager.getNextAvailableNodeId(MemcachedNodesManager.java:351)
    at de.javakaffee.web.msm.MemcachedSessionService.loadBackupSession(MemcachedSessionService.java:904)
    at de.javakaffee.web.msm.MemcachedSessionService.changeSessionIdOnMemcachedFailover(MemcachedSessionService.java:880)
    at de.javakaffee.web.msm.RequestTrackingContextValve.changeRequestedSessionId(RequestTrackingContextValve.java:128)
    at de.javakaffee.web.msm.RequestTrackingContextValve.invoke(RequestTrackingContextValve.java:98)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:165)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)

Original issue reported on code.google.com by huxiaobi...@gmail.com on 7 Jun 2013 at 7:49

GoogleCodeExporter commented 9 years ago 
Can you share more information? E.g. your configuration, more parts of the log 
that might show which nodeId is requested (there should be s.th. like "Session 
needs to be relocated as node $nodeId is not available, loading backup session 
for $requestedSessionId").

Original comment by martin.grotzke on 7 Jun 2013 at 8:40

GoogleCodeExporter commented 9 years ago 
Here is my configuration  <Manager 
className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
                         memcachedNodes="n1:192.168.3.14:11211,n2:192.168.3.15:11211"
                         sticky="false"
                         operationTimeout="3000"
                         sessionBackupAsync="false"
                         sessionBackupTimeout="1800000"
                         lockingMode="none"
                         requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
                         transcoderFactoryClass="de.javakaffee.web.msm.serializer.kryo.KryoTranscoderFactory"
                /> and there is no such 'Session needs to be relocated as node' info in my log

Original comment by huxiaobi...@gmail.com on 8 Jun 2013 at 3:52

GoogleCodeExporter commented 9 years ago 
Does this occur often, or did it occur only once?
Have you changed your tomcat/msm configuration?
Have you changed your memcached setup, anything in your infrastructure?
So, did it happen during "normal" operation or was anything special?

Original comment by martin.grotzke on 14 Jun 2013 at 9:40

GoogleCodeExporter commented 9 years ago 
Improved logging so that the requested nodeId is logged (and available node 
ids).

Original comment by martin.grotzke on 15 Jun 2013 at 11:09

GoogleCodeExporter commented 9 years ago 
this occur often when my appliacation run  , i don't change anything about 
configuration.

Original comment by huxiaobi...@gmail.com on 18 Jun 2013 at 8:40

GoogleCodeExporter commented 9 years ago 
Can you please upgrade to msm 1.6.5, which contains improved logging for this 
case (prints out the requested node id) and send log output again?
If this does not provide any insight the next step would be to create a sample 
app that allows me to reproduce your issue (until now, with my samples I can't).

Original comment by martin.grotzke on 18 Jun 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
java.lang.IllegalArgumentException: The given node id lwzjB7t is not part of 
this list [n1, n2]
    at de.javakaffee.web.msm.NodeIdList.getNextNodeId(NodeIdList.java:60)
    at de.javakaffee.web.msm.MemcachedNodesManager.getNextAvailableNodeId(MemcachedNodesManager.java:351)
    at de.javakaffee.web.msm.MemcachedSessionService.loadBackupSession(MemcachedSessionService.java:921)
    at de.javakaffee.web.msm.MemcachedSessionService.changeSessionIdOnMemcachedFailover(MemcachedSessionService.java:897)
    at de.javakaffee.web.msm.RequestTrackingContextValve.changeRequestedSessionId(RequestTrackingContextValve.java:128)
    at de.javakaffee.web.msm.RequestTrackingContextValve.invoke(RequestTrackingContextValve.java:98)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:170)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:662)
new issue happen when i change 1.6.5

Original comment by huxiaobi...@gmail.com on 19 Jun 2013 at 7:49

GoogleCodeExporter commented 9 years ago 
Doesn't help much. Can you configure logging according to 
https://code.google.com/p/memcached-session-manager/wiki/SetupAndConfiguration#C
onfigure_logging and send log output? Especially lines containing ">>>>>> 
Request starting:" are of interest (and those that contain a node id from "The 
given node id ... is not part of this list"). I'm wondering what session ids 
are sent by your clients.

Original comment by martin.grotzke on 19 Jun 2013 at 9:39

GoogleCodeExporter commented 9 years ago 
Any feedback?

Original comment by martin.grotzke on 24 Aug 2013 at 10:24