Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: Apache Processes Hung on Socket Issue

by vsespb (Hermit)
on Jul 03, 2013 at 20:33 UTC ( #1042278=note: print w/ replies, xml ) Need Help??


in reply to Apache Processes Hung on Socket Issue

local $SIG{ALRM} = sub { die 'timed out' };
Above is connection timeout.
Timeout => $connect_timeout,
Above is socket timeout.
You need both.


Comment on Re: Apache Processes Hung on Socket Issue
Select or Download Code
Replies are listed 'Best First'.
Re^2: Apache Processes Hung on Socket Issue
by eallenvii (Novice) on Jul 03, 2013 at 23:13 UTC
    I'm not sure what the difference is...but i could see a leap in logic to state that by cutting off the socket creation with a connection timeout would support my theory of the thread being left in a state unable to create further sockets?

      Internet is full of recommendations to use SIG ALARM while socket connect, and as far as I remember, socket "Timeout" option was not working right for connection stage (and/or for DNS timeouts). (not sure about current IO::Socket versions, through)

      Also SIG ALARM is not affecting socket read/write timeouts happened after alarm(0)

      thread being left in a state unable to create further sockets?
      Need probably to see more code, what happening after/before eval?

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (11)
As of 2015-07-29 17:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (266 votes), past polls