Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of srp@illinois.edu designates
 141.142.199.3 as permitted sender)
From: Stephen Pietrowicz <srp@illinois.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: when should you set maxInactivityDuration=0?
Date: Tue, 2 Dec 2014 11:43:00 -0600
Message-Id: <A3763A9F-D107-488E-BC31-35772851830F@illinois.edu>
To: users@activemq.apache.org
Mime-Version: 1.0 (Apple Message framework v1283)

Some time ago I noticed a dropped connection, and saw an error along the =
lines of "Channel was inactive for too long".   I made note of various =
folks here and elsewhere saying that the way to prevent this from =
happening is adding

wireFormat.maxInactivityDuration=3D0

So now I've got the time to look into this, and after reading further =
into the documentation, I'm not sure under which circumstances I should =
change this parameter at all.   The inactivity threads are set up in =
such a way that if no messages come across after the default (30000 ms) =
time, a message is sent to keep the connection active.   If there's no =
activity because of a broken socket, the "Channel was inactive for too =
long" exception gets issued.

I'm really hesitant to add this to the URL since I've only seen this =
error once.   It used to be that sending really long messages would make =
this exception come up, but that was fixed several versions ago.   =20

Under what circumstances would you set this parameter equal to zero?

Steve=