Thanks Joe for the reply. Yes the two client end points connect to the broker via the url
//jndi.properties java.naming.provider.url=failover\:tcp\://ipaddress\:78954?trace\=true&w ireFormat.maxInactivityDuration\=3600000 -----Original Message----- From: ttmdev [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2008 5:30 AM To: [email protected] Subject: Re: keep alive info frequency The two connection endpoints negotiate the value and settle on the lesser of the two. Do you have the same setting at both ends? Joe www.ttmsolutions.com Suchitha Koneru (sukoneru) wrote: > > Hello Active MQ users , > Our application uses active mq 4.1.1. > The max inactivity duration is set as 3600000(1hr). > So as per theory , the keep alive info message should be sent evey 30 > minutes if channel is inactive. > > The logs show that the keep alive info message is sent every 15 > seconds (the default value of 30 seconds is being used for max > inactivity duration). > > 2008-06-18 23:20:16,543 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - Message sent since last write check, > resetting flag > 2008-06-18 23:20:16,543 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - Message sent since last write check, > resetting flag > 2008-06-18 23:20:16,747 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - Message sent since last write check, > resetting flag > 2008-06-18 23:20:16,762 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - No message sent since last write check, > sending a KeepAliveInfo > 2008-06-18 23:20:16,762 [ActiveMQ Scheduler] DEBUG > TransportLogger.Connection:2 - SENDING: KeepAliveInfo {} > 2008-06-18 23:20:31,589 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - No message sent since last write check, > sending a KeepAliveInfo > 2008-06-18 23:20:31,589 [ActiveMQ Scheduler] DEBUG > transport.InactivityMonitor - No message sent since last write check, > sending a KeepAliveInfo > 2008-06-18 23:20:31,589 [ActiveMQ Transport: tcp:///127.0.0.1:2300] > DEBUG TransportLogger.Connection:1 - RECEIVED: KeepAliveInfo {} > 2008-06-18 23:20:31,589 [ActiveMQ Scheduler] DEBUG > TransportLogger.Connection:1 - SENDING: KeepAliveInfo {} > > > Please let me know if it is a bug and any possible fixes. > thanks, > Suchitha > > -- View this message in context: http://www.nabble.com/keep-alive-info-frequency-tp17998229p18007924.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
