Do you know where your variables are? | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
When I see "Connection timed out", my first thought is that the TCP socket has been closed on the Server side due to lack of traffic. I often see Apache servers routinely configured to close unused sockets after a period of inactivity (usually 300 seconds, but that just may be the default. It is a configuration parameter). That is what I suspect is occurring here.
The solution is to sent periodic "keep-alive" messages to your server. This will reset the inactive-socket timer and keep your connection established while you wait for your 120 minutes to pass. You will have to talk to the Server SysAdmin to find out what the appropriate interval is and possibly include code on the Server side to handle the "keep-alive" messages. A more resource friendly solution would be to establish your connection, send your MQ message and process the reply; then close the connection before you go to sleep for 120 minutes. Repeat the connect/send-receive/disconnect sequence when you wake up.
---- OGB In reply to Re: Stomp time out error
by Old_Gray_Bear
|
|