Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of JAVA_OPTS instead of CATALINA_OPTS. Fix for #602 #603

Merged

Conversation

vjrj
Copy link
Collaborator

@vjrj vjrj commented Jul 26, 2022

@sbearcsiro
Copy link
Contributor

sbearcsiro commented Aug 5, 2022

The Debian maintainer seems to not understand CATALINA_OPTS. CATALINA_OPTS is correct AFAIK.

CATALINA_OPTS is used only for catalina.sh run, start and debug, so you're not setting, eg Xmx=4G and Xms=4G when running catalina.sh stop (which launches a separate jvm process with JAVA_OPTS that stops tomcat. Or at least it did back in the day).

The above still holds for Tomcat 9, I've just checked the package locally.

To fix the debian package, export CATALINA_OPTS needs to be added to /usr/libexec/tomcat9/tomcat-start.sh. I'll look into submitting a patch to debian.

@vjrj
Copy link
Collaborator Author

vjrj commented Aug 5, 2022

Thanks @sbearcsiro for the clarifications. Anyway, if you check ala-install we only use CATALINA_OPTS to set the GEOSERVER_DATA_DIR and GEOWEBCACHE_CACHE_DIR. So I think that don't merit the effort (to send patch to debian) if we can accomplish the same using JAVA_OPTS in the geoserver install.

@sbearcsiro
Copy link
Contributor

Thanks @vjrj, you're right, it's not setting memory limits or anything so this change is fine IMHO.

@djtfmartin djtfmartin merged commit 0478815 into AtlasOfLivingAustralia:master Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants