Both active sessions and the number of webapps will fill up your heap. Within
64MB I think you will struggle to run 15-20 webapps but without knowing the
exact size of them all and the amount of hits you expect I couldn't say for
sure.
Ta
Matt
-Original Message-
From: Charl Gerber
The webapps are small: the actuall jars are about 2MB.
Traffic is relative lowkey, a few thousand hits per
day AT MOST (more likely less).
Each .war at the moment has its own struts and jstl
jars. Would it help if I move them to the common/lib
directory? I put them seperately at first because I
If Tomcat does run out of memory, what will happen?
Will a user just temporarily not be able to access the
apps until another session becomes available, or will
it crash and I have to restart?
Will 128MB be fine?
--- Dale, Matt [EMAIL PROTECTED] wrote:
Both active sessions and the number
I think struts would not support gracefully to be put in common/lib
Le Mardi 14 Juin 2005 11:46, Charl Gerber a écrit :
The webapps are small: the actuall jars are about 2MB.
Traffic is relative lowkey, a few thousand hits per
day AT MOST (more likely less).
Each .war at the moment has its
I suspected that, as each web-app needs its own
instance to be configured with mappings etc
--- delbd [EMAIL PROTECTED] wrote:
I think struts would not support gracefully to be
put in common/lib
Le Mardi 14 Juin 2005 11:46, Charl Gerber a écrit :
The webapps are small: the actuall
64MB is tight. But class definitions (IIRC) do not go onto the heap so you
could have a lot of classes without any worries.
But I recommend
- Not using sessions (or severely limiting its use)
- Tweak your server.xml to not have any of the examples, etc
- Be very careful in creating large
Thanks. All things I will look into.
I have to use sessions, as users logon to the apps,
but it will probably help if I bring the session
timeout down to 5 or 10 minutes
--- Tim Funk [EMAIL PROTECTED] wrote:
64MB is tight. But class definitions (IIRC) do not
go onto the heap so you
As you may never know where the Error occured, it may be some tools of the
webapp are left in an unconsistent state (transactions not closed,
inconsistent session, jsp not compiled and so on).
So restarting is probably needed.
Le Mardi 14 Juin 2005 11:49, Charl Gerber a écrit :
If Tomcat does
but I
personally would write a JSP or servlet to return the memory useage at any
given time. That way you can keep an eye on it.
Ta
Matt
-Original Message-
From: Charl Gerber [mailto:[EMAIL PROTECTED]
Sent: 14 June 2005 10:49
To: Tomcat Users List
Subject: RE: Tomcat memory question
Wow...where to begin...to answer in very general terms...
What affects memory usage?
The short answer is everything, and includes the two points you listed
below.
The long answer is it depends...how many concurrent sessions will each
webapp require...what size do you anticipate each session
Wow...where to begin...to answer in very general terms...
What affects memory usage?
The short answer is everything, and includes the two points you listed
below.
The long answer is it depends...how many concurrent sessions will each
webapp require...what size do you anticipate each session
From: Tim Funk [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat memory question
But class definitions (IIRC) do not go onto the heap so you
could have a lot of classes without any worries.
Actually, an instance of java.lang.Class is created for each
classloader/class combination
12 matches
Mail list logo
