Hi Gonzalo, I haven't experienced that kind of problem here recently with the current trunk. IMHO, the problem could be caused by some customized codes or some (portlet) application(s), not by the portal itself. So, I'd like to suggest you inspect the request/response cookie headers carefully. I know it's hard to reproduce and tedious to look into headers. However, sometimes the cookies could be corrupted for some reasons and so the existing JSESSIONID could be gone. Just for an example, if a page adds too many cookie items, then the browser could remove the existing ones. Anyway, there could be different reasons like this. So, I think you can record how the cookie headers are passed between request and response, when the JSESSIONID cookie is missing in the request cookie header, and when the response sends new JSESSIONID cookie value.
Just my two cents, Woonsan ----- Original Message ---- > From: Gonzalo Aguilar Delgado <[email protected]> > To: [email protected] > Sent: Thu, March 11, 2010 6:23:30 PM > Subject: Possible problem with session management > > Hi all, > > We are doing intensive tests with new portal 2.2.X-Trunk and found that > the session is lost after X periods of time (cannot determine yet). > > I think it's due session expiration, what's normal. > > What is not normal is that session expires even when the user has > interactions with the portal. > > ¿Maybe is one action missing (refresh session) in the pipelines? > > Someone with enough knowledge can check this, please? > > Thank you. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
