RE: number of sessions and OutOfMemoryException

[Allistair Crossley <Al...@QAS.com>]

well, that's one (not so good) way to look at it. i can't think why you would want session data to hang around forever in your web application. either add session-timeout, or determine a time when session.invalidate() can be called. you don't really want to throw memory at a system that is effectively supporting a memory leak.
 

	-----Original Message----- 
	From: Mark [mailto:sendmailtomark@yahoo.com] 
	Sent: Thu 02/12/2004 21:40 
	To: Tomcat Users List 
	Cc: 
	Subject: RE: number of sessions and OutOfMemoryException
	
	

	I'm I getting it right: that once OOME occures I need more memory or
	need to deside in my application how to remove sessions ?
	
	Thanks,
	Mark.
	--- "Shapira, Yoav" <Yo...@mpi.com> wrote:
	
	>
	> Hi,
	>
	> >If I set session-timeout to -1 in web.xml will I get eventualy
	> >OutOfMemoryException or Tomcat will remove the session and not
	> die?
	>
	> You will get OOMEs.  Session removal is your responsibility.
	>
	> (BTW note that OutOfMemory is an Error, not an Exception, with
	> everything the former implies).
	>
	> >Is there any easy way to calculate how much memory will be used
	> per
	> >session ( I know what objects will be stored)
	>
	> If you know the objects exactly, you can calculate, yeah, but it's
	> usually not worth the effort.
	>
	> Yoav Shapira http://www.yoavshapira.com
	>
	>
	>
	> This e-mail, including any attachments, is a confidential business
	> communication, and may contain information that is confidential,
	> proprietary and/or privileged.  This e-mail is intended only for
	> the individual(s) to whom it is addressed, and may not be saved,
	> copied, printed, disclosed or used by anyone else.  If you are not
	> the(an) intended recipient, please immediately delete this e-mail
	> from your computer system and notify the sender.  Thank you.
	>
	>
	>
	---------------------------------------------------------------------
	> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
	> For additional commands, e-mail:
	> tomcat-user-help@jakarta.apache.org
	>
	>
	
	
	
	               
	__________________________________
	Do you Yahoo!?
	Yahoo! Mail - Helps protect you from nasty viruses.
	http://promotions.yahoo.com/new_mail
	
	---------------------------------------------------------------------
	To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
	For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
	
	



<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> 
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com">www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>

timeout + SingleSignOn + pre-compiled JSPs

[Paulo Alvim <al...@powerlogic.com.br>]

Hi,

I'm using TC 5.0.28 running 3 WARs with  SingleSignOn feature.

I also have code that modify the user's timeout for authenticated users only. (Anonymous have 5 minutes and authenticated users have 1 hour). It has been worked for a year without problems!

Recently I'm getting short (5 minutes) timeouts when changing contexts even for authenticated users...Since we haven't modified our apps, the only suspect I could identify (so far) is our deployment schema - We've just changed our deployments from exploded files to 3 WAR files with pre-compiled jsps using the Tomcat Deployer...

Is there anyone with the same problem? Is it possible to get into timeout problems using WAR instead of files?

Thanks in advance...

Paulo Alvim
Powerlogic - Brazil


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