ok, one more question for clarification :-) The vendor docs say this: "Define CATALINA_OPTS to configure the following JVM settings: CATALINA_OPTS=-server -Xms2048m -Xmx4g -XX:MaxMetaspaceSize=512m Note:If you are deploying multiple [vendor] applications to the same Tomcat server, -Xmx must be increased by 2g and -XX:MaxMetaspaceSize must be increased by 128m."
Given that they are (ostensibly, based on the above statement) JVM settings, would these settings be better placed under JAVA_OPTS instead of CATALINA_OPTS? On Wed, Jun 16, 2021 at 10:29 AM Noelette Stout <noelettest...@isu.edu> wrote: > This confirms something that I was thinking originally, which is that we > have no good reason to have both in setenv.sh. I'm pretty sure that these > were both mentioned in various pieces of documentation from the application > vendor. Their documentation tends to be less than stellar. Combine bad > documentation with app admins that are completely unfamiliar with tomcat... > and you get messy setups. Unfortunately, there are more of them than me, so > I have to have ALL of my facts straight before I go into battle. > > Thanks for this additional information. It is much appreciated. > > On Wed, Jun 16, 2021 at 10:14 AM Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> Noelette, >> >> On 6/16/21 11:29, Noelette Stout wrote: >> > Thanks! I was mostly trying to figure out if there was precedence or if >> it >> > was additive (i.e. 2GB to tomcat itself and another 2GB to the apps). >> We're >> > having some resource issues on one of our servers, so I wanted to make >> sure >> > I understood how the resources were being allocated. >> >> No additivity at all: the last one on the command-line wins. There is no >> heap separation between Tomcat and the applications: it's one(ish) big, >> happy heap. :) >> >> A note about CATALINA_OPTS versus JAVA_OPTS: when you use the various >> scripts provided by Tomcat, CATALINA_OPTS is only used when launching a >> Tomcat instance. JAVA_OPTS is used when launching *any* Java process. >> There are many Java processes those scripts will launch that aren't >> actually launching Tomcat. Examples include: >> >> 1. catalina.sh configtest >> 2. catalina.sh stop (also shutdown.sh) >> 3. catalina.sh version >> 4. tool-wrapper.sh [anything] >> >> In all of those cases, JAVA_OPTS will be passed to the JVM. >> >> Do you really need a 2 gig heap to send a "shutdown" command to a >> running server? Probably not. >> >> -chris >> >> > On Wed, Jun 16, 2021 at 9:17 AM Rob Sargent <rsarg...@xmission.com> >> wrote: >> > >> >> >> >> >> >> On 6/16/21 9:06 AM, Noelette Stout wrote: >> >>> openjdk version "1.8.0_292" >> >>> >> >>> >> >>> On Wed, Jun 16, 2021 at 9:04 AM Rob Sargent <rsarg...@xmission.com> >> >> wrote: >> >>> >> >>> >> >> Both as for the same minimum so you should get 2G at start up. I'm not >> >> sure which has precedency but I would be on java opt. I don't have a >> >> catalina env, but you can see how CATALINA_OPTS is used in relationship >> >> with JAVA_OPTS >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > -- > Noelette Stout > > ITS Enterprise Applications - Application Administrator - Senior > > Business Administration Building, Rm 109L > 921 South 8th Ave 8037 > Idaho State University > Pocatello ID 83209 > E-mail: stounoel "at" isu "dot" edu > Desk: 208-282-2554 > -- Noelette Stout ITS Enterprise Applications - Application Administrator - Senior Business Administration Building, Rm 109L 921 South 8th Ave 8037 Idaho State University Pocatello ID 83209 E-mail: stounoel "at" isu "dot" edu Desk: 208-282-2554
