|There's more than one way to do things|
Re^4: SOAP::LITE client timeout makes ALL my Catalyst app to waitby miguelele (Beadle)
|on Jun 26, 2012 at 09:57 UTC||Need Help??|
Thank you for keep on trying!
Your help and your links seem to describe the usual world, in which a remote delay makes the user to wait. I can live with it. Mostly because I can't change it by now. If the remote server goes down, its not my problem.
BUT, what wonders me is that all other users must wait too, even if they try pages without SOAP connections
- User "A" requests the page with the remote Web service and waits until timeout because the service is down.
- User "B" (and C, D, E, etc.) can't view any page in the app.
If I run 2 Fcgi processes in nginx, user "B" can navigate without any delay, but if he request the web service during the timeout of "A", all the app gets closed for "D", "E", etc, until timeouts of the previous users.
Isn't it weird????