RE: Master cache machine no longer reachable causes spurious threads?

["Smuts, Aaron" <aa...@amazon.com>]

Remove, and put requests to the remote rmi server are done asynchronously; however, get's are synchronous.  

If a get locks up, then it could potentially block other put and remove requests locally.  Are you seeing all requests block.  

Why is the situation different if the machine goes down, versus the rmi server not running?  I haven't dug into the sun rmi code very far.

What do you suggest? 

You could run in put only mode with remove on put set to false, if you frequently have machines shutting down thereby killing the remote server.

Aaron  

-----Original Message-----
From: Tim Cocks [mailto:tcocks@gmail.com] 
Sent: Tuesday, December 07, 2004 9:53 AM
To: Smuts, Aaron
Cc: turbine-jcs-user@jakarta.apache.org
Subject: Re: Master cache machine no longer reachable causes spurious threads?

Thanks for your time.  We are using the remote server.  We have found it is almost exactly 15 minutes between when the machine running the master cache shuts down and when the clients realise the remote cache is no longer accessible.  During those 15 minutes, calls to JCS block.
 After the 15 minutes, the calls return.

The problem appears to be an RMI one. The fact the delay is consistently ~15 minutes seems to imply the timeout is working correctly, but is set too high.  We considered changing the RMI timeouts by overriding RMISocketFactory. Unfortunately this would require us to change the JCS source code, something we would like to avoid.

Tim

On Mon, 6 Dec 2004 13:45:59 -0800, Smuts, Aaron <aa...@amazon.com> wrote:
> I'll need to look into this.
> 
> You are using the remote server?  The client reconnect must not be timing out properly.
> 
> Aaron
> 
> 
> 
> 
> -----Original Message-----
> From: Tim Cocks [mailto:tcocks@gmail.com]
> Sent: Friday, December 03, 2004 2:39 AM
> To: turbine-jcs-user@jakarta.apache.org
> Subject: Master cache machine no longer reachable causes spurious threads?
> 
> We use JCS outside of Turbine on about 20 machines connected to a JCS master cache.
> 
> On occasion we have had to kill the JCS master cache process and have observed the client machines gracefully realise the master cache is no longer available.  They continue to work indefinitely, albeit without access to the master cache.
> 
> However, when the machine running the master cache goes down completely the clients continue attempting to connect.  In the process, they are creating more and more blocking threads and the JVM eventually terminates.
> 
> Is this a known problem?  If so, are there any solutions?
> 
> Thanks in advance for any help,
> 
> Tim Cocks
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
> turbine-jcs-user-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org

Re: Master cache machine no longer reachable causes spurious threads?

[Matthew Cooke <mp...@lineone.net>]

> Why is the situation different if the machine goes down, versus the rmi server not running?  I haven't dug into the sun rmi code very far.

Because a  "can't connect to port" style error times out quickly, but a 
NoRouteToHost takes quite a while to recieve - the RMI default is too 
long for time critical code like gets (that hold a sync lock) in JCS.

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org