Re: Stomp time out error

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.

----
I Go Back to Sleep, Now.

OGB

Comment on Re: Stomp time out error Download Code

Replies are listed 'Best First'.
Re^2: Stomp time out error by magarwal (Novice) on Jun 25, 2010 at 13:36 UTC
I tried to check for connection time out, but it looks fine.In the below code, even after waiting for 120 min., its printing the "connection defined", but when it comes to $stmp-> connect(); I get the same error. `if(defined($stmp->socket->connected)){ print "\nconnection defined\n"; } $stmp->connect();` [download] So, can socket time out be the only reason. How can I set that up. I dont want to send the keep alive message as it may increase the traffic at peak times. Please let me know your inputs. Thanks, Manu	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Stomp time out error
by magarwal (Novice) on Jun 25, 2010 at 13:36 UTC

if(defined($stmp->socket->connected)){
                print "\nconnection defined\n";
            }
$stmp->connect();
[download]

[reply]
[d/l]