"session will be purged from storage"

318 views
Skip to first unread message

magg...@gmail.com

unread,
Jun 8, 2014, 8:57:11 PM6/8/14
to memcached-se...@googlegroups.com
Hi,

I have some questions about msm. Could you please help me on that?

Please look at the log info below. The CNFE problem are reported as a WARN, but not an ERROR. If the session could be purged from storage, can we think it is the right way that memcached-session-manager dealing with the session if it can not be found in memory?

Jun 02, 2014 12:23:08 PM de.javakaffee.web.msm.MemcachedSessionService loadFromMemcached
WARNING: Could not deserialize session with id 15D4BFCEA5966FD926A68516B2FD1AD0-n1 from memcached, session will be purged from storage.
de.javakaffee.web.msm.TranscoderDeserializationException: Caught CNFE decoding data
at de.javakaffee.web.msm.JavaSerializationTranscoder.deserializeAttributes(JavaSerializationTranscoder.java:185)
at de.javakaffee.web.msm.TranscoderService.deserializeAttributes(TranscoderService.java:171)
at de.javakaffee.web.msm.TranscoderService.deserialize(TranscoderService.java:128)
at de.javakaffee.web.msm.MemcachedSessionService.loadFromMemcached(MemcachedSessionService.java:1084)
at de.javakaffee.web.msm.MemcachedSessionService.findSession(MemcachedSessionService.java:569)
at de.javakaffee.web.msm.MemcachedBackupSessionManager.findSession(MemcachedBackupSessionManager.java:222)
at org.apache.catalina.connector.Request.doGetSession(Request.java:2419)
at org.apache.catalina.connector.Request.getSession(Request.java:2157)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833)
at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:844)
at com.demandforce.facebook.service.BusinessService.getBusiness(BusinessService.java:83)
at com.demandforce.facebook.controller.ControllerServlet.doPost(ControllerServlet.java:33)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at de.javakaffee.web.msm.RequestTrackingContextValve.invoke(RequestTrackingContextValve.java:99)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:156)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:124)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:615)
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.Http11NioProcessor.process(Http11NioProcessor.java:889)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:744)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.ClassNotFoundException: org.acegisecurity.context.SecurityContextImpl
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at org.apache.catalina.util.CustomObjectInputStream.resolveClass(CustomObjectInputStream.java:75)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at de.javakaffee.web.msm.JavaSerializationTranscoder.deserializeAttributes(JavaSerializationTranscoder.java:172)

Here are the config code. We are using "de.javakaffee.web.msm.JavaSerializationTranscoderFactory" but not kryo. While, we still see "java.lang.ClassNotFoundException: org.acegisecurity.context.SecurityContextImpl". How can we resolve this?

<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
    memcachedNodes="n1:localhost:11211"
    sticky="false"
    sessionBackupAsync="false"
    lockingMode="auto"
    sessionBackupTimeout="500"
    requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
    transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory"
    />
 
Any comments would be appreciated.

Best, 

Maggie
 

Martin Grotzke

unread,
Jun 9, 2014, 4:20:40 AM6/9/14
to memcached-session-manager

Hi Maggie,

Am 09.06.2014 09:07 schrieb <magg...@gmail.com>:
>
> Hi,
>
> I have some questions about msm. Could you please help me on that?
>
> Please look at the log info below. The CNFE problem are reported as a WARN, but not an ERROR. If the session could be purged from storage, can we think it is the right way that memcached-session-manager dealing with the session if it can not be found in memory?

I'm not sure I understand what you're going to say. Do you want to suggest an alternative way of handling this case?

Not really sure what's the reason for this (assuming that SecurityContextImpl is in your webapps classpath). Can you provide a sample webapp that allows to reproduce this issue?

Cheers,
Martin

>
>> <Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
>>     memcachedNodes="n1:localhost:11211"
>>     sticky="false"
>>     sessionBackupAsync="false"
>>     lockingMode="auto"
>>     sessionBackupTimeout="500"
>>     requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
>>     transcoderFactoryClass="de.javakaffee.web.msm.JavaSerializationTranscoderFactory"
>>     />
>
>  
>
> Any comments would be appreciated.
>
> Best, 
>
> Maggie
>  
>

> --
>
> ---
> 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.

magg...@gmail.com

unread,
Jun 9, 2014, 5:42:24 AM6/9/14
to memcached-se...@googlegroups.com, martin....@googlemail.com
Many thanks for your response and sorry that my question was not clear.

Based on this line: "WARNING: Could not deserialize session with id ... from memcached, session will be purged from storage.", I asked this question and would like to know if that is OK that we leave it alone.

We have been seeing this kind of log several times, but we were not able to reproduce it. Seems no reason that SecurityContextImpl could cause this problem, since it was not happened all the time. We just guess it might be related with our release activities. 

Thanks anyway. 


在 2014年6月9日星期一UTC+8下午4时20分40秒,Martin Grotzke写道:

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

Martin Grotzke

unread,
Jun 9, 2014, 6:01:11 AM6/9/14
to memcached-session-manager

If it happens during deployments this should explain the issue, when it happens during normal operations you probably would like to further analyze this.

Cheers,
Martin

Reply all
Reply to author
Forward
0 new messages