Any kind updates ? is this an issue with struts2 TokenSessionStoreInterceptor ?
On Mon, May 25, 2015 at 5:06 PM, Sreekanth S. Nair < sreekanth.n...@egovernments.org> wrote: > Once again i have tested afresh, but the same issue is coming. We have > also found when we are using spring-http-session via redis data store only > we are getting this issue. What could be the issue, does > TokenSessionStoreInterceptor really trying to store the Container which is > not issuing any error in HttpSession (because httpsession can accept > nonserializable object where redis store can't)? > > > On Mon, May 25, 2015 at 2:28 PM, Lukasz Lenart <lukaszlen...@apache.org> > wrote: > >> 2015-05-25 10:29 GMT+02:00 Sreekanth S. Nair < >> sreekanth.n...@egovernments.org>: >> > Hi Lukasz, >> > Based on your comment on WW-4028 issue, struts2 should >> not >> > try to store ActionInvocation in session, from the log i have attached >> > points that its getting stored into session which basically breaks your >> > point. FYI we are using redis and spring session to manage HttpSession >> > object. >> >> Not, it isn't like that. Without ActionInvocation you won't be able >> use Session Token. ActionInvocation has a reference to Container (DI) >> which isn't serializable and that was resolved with WW-4028. >> Now I'm trying figure out why do you see this exception and my only >> guess is that you must have serialized an old version of >> ActionInvocation which is now restored and used after upgrading to >> 2.3.24. Does it happen locally on a fresh instance? >> >> >> Regards >> -- >> Łukasz >> + 48 606 323 122 http://www.lenart.org.pl/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> For additional commands, e-mail: user-h...@struts.apache.org >> >> >
