Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re^5: SOAP::LITE client timeout makes ALL my Catalyst app to wait

by Anonymous Monk
on Jun 27, 2012 at 10:50 UTC ( #978615=note: print w/ replies, xml ) Need Help??


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


Comment on Re^5: SOAP::LITE client timeout makes ALL my Catalyst app to wait

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://978615]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (7)
As of 2014-07-12 11:47 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    When choosing user names for websites, I prefer to use:








    Results (239 votes), past polls