I doubt this is related, but DPAE::Database had/has a DB handle caching issue which creates a MySQL connection issue, see https://github.com/PerlDancer/Dancer2-Plugin-Auth-Extensible-Provider-Database/issues/3

It's possible that something in your app (at the "system" module level) is caching something badly (although it wouldn't explain why it only affects one user...)
-N

On Fri, 23 Nov 2018 at 07:38, Nikola Mitev <nik@mitev.eu> wrote:
Thank you for the suggestion, it makes a lot of sense for me as the app
does write to a database and the risk of data corruption is certainly
not worth the efficiency gains at the current load (which is very
unlikely to increase drastically).

I will definitely look into a single threaded server - whether it will
resolve the session issues we will wait and see :)

Nik

On Thu, 2018-11-22 at 12:55 -0700, Warren Young wrote:
> On Nov 22, 2018, at 12:54 PM, Warren Young <warren@etr-usa.com>
> wrote:
> >
> >
> > On Nov 22, 2018, at 1:23 AM, Nikola Mitev <nik@mitev.eu> wrote:
> > >
> > >
> > > I am using Starman with Nginx in front of it
> > ...every code path in your app that touches global state needs to
> > be protected…
> To be clear, by “touch” I mean “modify”.  If your app is fully read-
> only, then none of what I wrote matters.
> _______________________________________________
> dancer-users mailing list
> dancer-users@dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________
dancer-users mailing list
dancer-users@dancer.pm
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users