(From [EMAIL PROTECTED]) The GSI Secure Conversation is a mechanism where the security context created during handshake is stored as a resource object. The security context and hence the resource, by default has the lifetime of the credential used to create the security context. So if you used your proxy with default lifetime, the security context resource will not be destroyed for about 12 hours. Changing the sweeper delay does not affect this, since the resources don't expire in time for sweeper to delete them.
You can configure the lifetime of the context by setting an Integer property for this constant on the stub. org.globus.wsrf.impl.security.authentication.Constants.CONTEXT_LIFETIME Rachana > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of andrea manzi > Sent: Monday, November 05, 2007 8:50 AM > To: [email protected] > Subject: [gt-user] Heap size & GSI-Secure-Conversation > > Hi all, > I'm trying to use GSI-Secure-Conversation to authenticate calls to my > WEB-Services. > With my test client that performs one web-service call every two > seconds, the JAVA heap size on server side increase on every calls until > my container crashes. I'm setting client stubs with full-delegation and > no-integrity.I read documentation about GSI-Secure-Conversation and in > particular about a sweeper thread that cleans expired security contexts. > I tried to activate it on the container security descriptor but the > problem still persists. > The context expires when the proxy attached to stubs expires? > Is there someone else that have the same problem? Can't be a memory > leak on GSI-Secure-Conversation implementation? > > thanks & best regards > > Andrea Manzi
