in reply to Re^4: SOAP::LITE client timeout makes ALL my Catalyst app to wait
in thread SOAP::LITE client timeout makes ALL my Catalyst app to wait
BUT, what wonders me is that all other users must wait too, even if they try pages without SOAP connections ... sn't it weird????
No it isn't weird, its simply how it works
If client A is timing out, don't let others (like client B) to try to connect, simply assume it will fail also, and report failure (sorry, try again later)
This way one of your two app-servers stays alive and clients C D E can get their turn.
This is the basic lesson of "Watching long processes through CGI (Aug 02)", much more directly expressed in Highlander: one instance at a time (Oct 00)
Its much nicer than users waiting, or getting a gateway timeout from nginx -- gateway timeout means "stupid website is broken" to regular folks
|
|---|