Causing a Graceful Timeout - Remote Call

rocksolidhq

Hey,

i have a php app that calls a method on a remote system. I have no way of testing the remote system to ensure it is responsive as it has a web front end that responds despite the fact that it's background listener has died. The result is that my php script calls just sit and eventually hit the php timeout and toss an ugly error. (usually stack overflow errors).

i've seen that there are ways to adjust the system time out (set_time_out) but this doesn't help. i still get the ugly message.

i also see lots of folks suggesting using fsocketopen but again this doesn't help as the remote system's web front end will respond.

does anyone have any idea how i can even just present a customized message once a given time has passed on my function call?

thanks,
dean

halojoy

I am really very sorry to hear you have had a listener who died.
But can this be such a problem?
After all it must be extremely rare this happens.
The chance they will die while in contact with your stuff is probable like 1 in a million.
How many have died for you?

Regards
🙂

bradgrafelman

halojoy;10948773 wrote:
I am really very sorry to hear you have had a listener who died.
But can this be such a problem?
After all it must be extremely rare this happens.
The chance they will die while in contact with your stuff is probable like 1 in a million.
How many have died for you?

Regards
🙂

Erm... I think the OP's description might have been "lost in translation" across the language barrier here, halojoy. When he said his "background listener has died", I believe he means that his "background service/daemon is no longer responding" rather than the death of a fan/admirer. :p

rocksolidhq: How do you call the remote app? Can you show us some code that you use to do this? We might be able to offer alternatives (e.g. PHP streams with timeouts set), but it's hard to say since there are many ways one might communicate with a remote service.