can always add more servers to handle the load.
Good luck - Richard
> -Original Message-
> From: BB Commish [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 21, 2005 2:45 PM
> To: users@tomcat.apache.org
> Subject: RE: Managing concurrent high memory processes
>
rceive it anyway) of deploying to a multi-machine environment.
>
>
> >From: "Richard Mixon" <[EMAIL PROTECTED]>
> >Reply-To: <[EMAIL PROTECTED]>
> >To: "'Tomcat Users List'"
> >Subject: RE: Managing concurrent high memory pro
-machine environment.
From: "Richard Mixon" <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
To: "'Tomcat Users List'"
Subject: RE: Managing concurrent high memory processes
Date: Fri, 18 Nov 2005 11:14:55 -0700
BB,
It sounds like you are talking abou
Subject: RE: Managing concurrent high memory processes
Date: Fri, 18 Nov 2005 10:45:01 -0800 (PST)
Sure you can pawn off the processing to other
processes. It's still going to use memory and the
processor regardless however. This would at least
leave your main process memory for handling requests
> -Original Message-
> From: BB Commish [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 18, 2005 12:50 PM
> To: users@tomcat.apache.org
> Subject: Managing concurrent high memory processes
>
> We have a Struts application running on Tomcat where
> a few actions
ystem monitor to monitor the CPU utilization (assuming tomcat
and the backend database are on different machines).
ND
-Original Message-
From: BB Commish [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 12:50 PM
To: users@tomcat.apache.org
Subject: Managing concurrent high memory proc
bundled together.
Hope these thoughts are useful.
- Richard
> -Original Message-
> From: BB Commish [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 18, 2005 10:50 AM
> To: users@tomcat.apache.org
> Subject: Managing concurrent high memory processes
>
> We have a Struts appli
sounds like you have a heafty reporting process, which loads a ton of data
and generates a large report. I definitely wouldn't recommend running these
processes within a single instance of Tomcat. You'll easily eat all the
available RAM and get OOME.
A better approach would be to off-load the proc
We have a Struts application running on Tomcat where a few actions within
the app can invoke processing that consumes 300+ MB of RAM and can run for
several hours. The issue is how to make the application more scalable to
accommodate multiple concurrent 'high load' processes and also make better
