Without looking at NMS, the statement you quote *isn't generally true* for the purposes of keepalive packets being sent.
The first sentence is false: it doesn't need to match, ditto the 2nd and 3rd. "When using the maxInactivityDuration option, the setting must match on both sides of the connection. The default value the maxInactivityDuration option on the broker side is 30 seconds so each consumer must have the same setting so that the option actually takes effect. If the settings do not match, the option will have no effect. " Try not setting maxInactivityDuration to zero - e.g. use the default. You can verify then if the transport gets the minimum of the two values (client end and broker end). Then see if you get keepalives sent at the rate of ~0.5 the value one way (and IIRC ~0.66 the other way). It should be straightforward for you to check the behaviour with snoop/wireshark - look for packets on your client i/f to and from your broker IP/port. ----- Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View this message in context: http://activemq.2283324.n4.nabble.com/maxInactivityDuration-in-Visual-Basic-tp4652956p4652975.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
