P
PhilF
Guest
> I have noticed that every morning the socket connection seems to have been lost overnight. I know that this is far too late to be of any use to you -- but I thought I would add a comment for others who might find this on a search. We ran into a similar problem -- our connection to ActiveMQ would regularly hang for no obvious reason. What we found was this: 1) There was a state-aware firewall between the client and the server. A connection would be opened between the two, but after about 90 minutes the firewall would notice that there had been no traffic, and would drop the connection. Neither end was notified. 2) The ABL STOMP client system is installed on Cent/OS 7 system with the default TCP/IP configuration. That means that after 2 hours the TCP/IP stack noticed the lack of traffic. It would try to contact the remote system 10 times, separated by 75 seconds. Since the firewall had closed the connection, these attempts failed and the TCP/IP stack closed the local connection. Our ABL Stomp client was so informed, and it shut down. This problem was resolved (in a manner of speaking) by adding heart-beat:0,60000 to the (hard-coded) connect frame. This tells the ActiveMQ system to send a heart-beat every minute, keeping the network connection alive. I don't know what was happening on the ActiveMQ server at the same time -- but it never dropped the stale consumer from the queue. Heartbeats would probably resolve that issue too -- but that's a separate conversation.
Continue reading...
Continue reading...