The dev server is generally just for testing but it’s also pretty robust and some devs have deployed it to production.
The only times I’ve seen the sort of thing you describe is when doing wonky fork/self-referential code. A potential help would be to add a -k to the command line in case things are just blocking somewhere. You could also start with perl -MCarp::Always script/myapp_server.pl ....
Barring success with that, and not being a perl -d kinda dev unless backed into a corner, I tend to remove new code to get back to a functioning version and then progressively return things till I discover the fail point. I have hardly had to do this since becoming more serious about writing tests for individual pieces before trying to mix them. Skipping test writing is a false economy and there is a wealth of test appliances for Perl and Catalyst.
In reply to Re: Catalyst (app_)server.pl hangs a lot
by Your Mother
in thread Catalyst (app_)server.pl hangs a lot
by miguelele
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |