Thanks for the reply and comments.
So we only use Dancer::Standalone for development. For production, we use
uwsgi (which btw works phenomenally well as compared to Starman).
This particular version of the software, including with the latest version of
Dancer 1, is not yet in production, so I don’t yet know if we will see this
same problem during production. If the problem only surfaces with
Dancer::Standalone, I suppose we can live with it…. what I want to avoid is
releasing new software into production that has this problem from day 1. I
understand uwsgi will simply restart the crashed process, but that’s no way to
run at scale, and also the user will experience an error and may not know to
just “refresh”.
From: Stefan Hornburg (Racke)
Sent: Wednesday, March 13, 2019 10:00 AM
To: dancer-users@dancer.pm
Subject: Re: [dancer-users] Dancer crashing
On 3/13/19 4:51 PM, Hermann Calabria wrote:
> I don’t have fatal warnings turned on.
>
>
>
> Also, reviewing the stack trace, none of the calls appear to go through the
> app. The only packages involved are:
>
>
>
> HTTP::Server::Simple
>
> Dancer::Handler::Standalone
>
> Dancer::Handler
>
> Dancer
>
>
Hello Herrmann,
at any rate my advise would be to not use dancer standalone at all, especially
not in a production environment.
With plackup + starman you get a more reliable environment, and you can
restrict the lifetime of the workers
by using plackup's --max-requests option.
That is useful to limit memory growth and other hard to track problems
occurring on long running applications.
Regards
Racke
>
>
>
> *From: *Andrew Beverley <mailto:a...@andybev.com>
> *Sent: *Tuesday, March 12, 2019 3:56 PM
> *To: *Perl Dancer users mailing list <mailto:dancer-users@dancer.pm>
> *Cc: *Hermann Calabria <mailto:herm...@ivouch.com>
> *Subject: *Re: [dancer-users] Dancer crashing
>
>
>
> On Tue, 12 Mar 2019 15:08:46 -0700 Hermann Calabria wrote:
>
>> Sure, it’s probably something my app is doing. However I expect
>
>> Dancer to be resilient enough to not crash in this manner.
>
>
>
> FWIW, I did notice that the crash appeared to happen because of an
>
> uninitialized value. Do you have fatal warnings turned on, and could
>
> that be one of the causes? I don't know, but does Dancer normally run
>
> without fatal warnings, and maybe the problem you encountered wouldn't
>
> normally be fatal?
>
>
>
> Andy
>
>
>
>
> _______________________________________________
> dancer-users mailing list
> dancer-users@dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>
--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
_______________________________________________
dancer-users mailing list
dancer-users@dancer.pm
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
