msxml3.dll error '80072ee2' The operation timed out
Is there some way I can handle this?
I am sending data to a remote page which should in turn send back a reply if the data is found on the remote server.
However, if it is not found, it does not send back a reply, it times out which completely halts my script.
msxml3.dll error '80072ee2'
The operation timed out
What I would like is if after a certain amount of time, to maybe response.write "No one's home, continuing..."
That would seem like the way to go if there's no way to stop that error from arising.
The timeout is already set for the XMLRPC:
const XRPC_RESOLVE_TIMEOUT = 5000
const XRPC_CONNECT_TIMEOUT = 500
const XRPC_SEND_TIMEOUT = 1000
const XRPC_RECEIVE_TIMEOUT = 10000
So if the data IS found, then we can use those timeout values, but is there some way to say
Call the script for 4 seconds, ..."ok 4 seconds is up...No one's home, continuing..."?
I am sending data to a remote page which should in turn send back a reply if the data is found on the remote server.
However, if it is not found, it does not send back a reply, it times out which completely halts my script.
msxml3.dll error '80072ee2'
The operation timed out
What I would like is if after a certain amount of time, to maybe response.write "No one's home, continuing..."
That would seem like the way to go if there's no way to stop that error from arising.
The timeout is already set for the XMLRPC:
const XRPC_RESOLVE_TIMEOUT = 5000
const XRPC_CONNECT_TIMEOUT = 500
const XRPC_SEND_TIMEOUT = 1000
const XRPC_RECEIVE_TIMEOUT = 10000
So if the data IS found, then we can use those timeout values, but is there some way to say
Call the script for 4 seconds, ..."ok 4 seconds is up...No one's home, continuing..."?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah hongjun, didn't see your solution there. I will give it a try as well. Looks interesting to check the status before sending the data!
ASKER
hongjun, that does check the status of the URL, but does not check the actual channel that is being send va xmlrpc. The problem was that the channel no longer exists on the remote server so it could not send a response back. That is why the time out error kept happening. So while it is good to check if the URL is up, I still need to be able to know if the channel is alive or not. The only way to know if it's not there is if I get a script timeout error and to handle it...it seems.
ASKER