Hmm, I can't say I know this stuff cold, but I thought that timeout controlled how long any one individual remote request can take before failing.
I thought "jmx.remote.x.server.connection.timeout" was the one that controlled the timeout you describe? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Geert Bevin > Sent: Tuesday, February 26, 2008 12:56 PM > To: [email protected] > Subject: Re: [tc-dev] JMX connection timeout in ClientConnectEventHandler > > Meant this of course: > > environment.put("jmx.remote.x.request.timeout", new Long(Long.MAX_VALUE)); > > On Tue, Feb 26, 2008 at 9:54 PM, Geert Bevin <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Gary discovered that when letting the CVT idle for too long, the > > connections between L1 agents and L2 times out. This can be solved by > > changing ClientConnectEventHandler so that: > > > > environment.put("jmx.remote.x.request.timeout", Long.MAX_VALUE); > > > > is used instead of the current 60000. > > > > Does anybody know if this could badly impact other things? I want to > > make sure before changing some timeout value that maybe something else > > relies on. > > > > Thanks, > > > > Geert > > > > -- > > Geert Bevin > > Terracotta - http://www.terracotta.org > > Uwyn "Use what you need" - http://uwyn.com > > RIFE Java application framework - http://rifers.org > > Music and words - http://gbevin.com > > > > > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
