You _could_ use something like Hazelcast and just set a TTL, and not worry
about it ;)
https://stormpath.com/blog/hazelcast-support-apache-shiro

But if you want to use a DB, and only want to have one service run the
task.  You could always create a single purpose app to do that (a non web
app that has uses the same Shiro configuration, with validation turned on)



On Wed, Jan 25, 2017 at 10:25 AM, emmeblm <[email protected]> wrote:

> Hi there,
>
> We are implementing some session logic with Shiro and MySql (until
> CouchBase
> is ready for us). We need to erase session data from the database
> periodically and SessionValidationScheduler seems pretty good for it.
>
> Our application is being deployed in Docker behind a load balancer. We can
> have from 2 to 10 instances running at the same time in production. There
> is
> where questions arised about SessionValidationScheduler and its behavoiur
> with DA.
>
> For performance reasons and in order to avoid concurrent conflicts, we
> don't
> wan't each instance of our application to run the session validation
> scheduler without control. But we can't seem to find any information about
> making it work properly with distributed applications, so we are looking
> for
> inputs on these, like good or bad experiences/knowledge with it.
>
> Thanks,
>
>
>
> --
> View this message in context: http://shiro-user.582556.n2.
> nabble.com/How-does-SessionValidationScheduler-work-with-distributed-
> applications-tp7581469.html
> Sent from the Shiro User mailing list archive at Nabble.com.
>

Reply via email to