It's RMI. You don't have much control over it. You can inject a custom factory if you want.
You can tune the event queue on top of the connection. The client uses a queue. You can use a single threaded model or a pooled event queue. Aaron --- On Tue, 9/8/09, sachamul <sacha_...@yahoo.com> wrote: > From: sachamul <sacha_...@yahoo.com> > Subject: Connection Details of Local to Remote cache > To: jcs-users@jakarta.apache.org > Date: Tuesday, September 8, 2009, 4:11 AM > > Hi, > We use JCS Remote Caching. > > I have observed that the number of "established" > connections between Local > and Remote Cache keeps fluctuating. It varies between > approx 5-120 > connection in a min or so. > > Our application gets 100-120 requests/sec and for every > request the Local > Cache is queried and if not found then Remote Cache gets > queried. And at the > end of processing a put call happens on Local Cache, which > i think results > into a put call on the Remote Cache. > > What i want to know is > 1. the life cycle of the Connection between Local and > Remote Cache > 2. any configuration parameters for this connection > 3. is it pooled connection > > Thanks in advance. > > ^Sachin$ > -- > View this message in context: > http://www.nabble.com/Connection-Details-of-Local-to-Remote-cache-tp25344143p25344143.html > Sent from the JCS - Users mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jcs-users-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jcs-users-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: jcs-users-unsubscr...@jakarta.apache.org For additional commands, e-mail: jcs-users-h...@jakarta.apache.org
