Hiya, Did you figure out your problem? Web applications don't need shiro's native session management - but if you enable native session management, you have to ensure that your SessionDAO mechanism (or cache) stores sessions persistently. If you're using an in-memory-only cache, you could have session loss if the cache memory is exhausted.
Cheers, -- Les Hazlewood | @lhazlewood CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282 On Tue, Sep 3, 2013 at 6:41 AM, ramonfacchin <[email protected]> wrote: > Occurs that the documentation has a note explaining that Web Applications > should implement native session management. > > I will test that. And check if it works. > > Sorry for bothering. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Losing-SessionId-after-a-couple-Requests-tp7579104p7579105.html > Sent from the Shiro User mailing list archive at Nabble.com. >
