Installed and configured Endevor Web Services/Interface on test system with limited resource, and noticed the following messages in the Tomcat log:
13.30.40 STC07691 *BPXI039I SYSTEM LIMIT SHRLIBRGNSIZE HAS REACHED 90% OF ITS CURRENT CAPACITY OF 78643200
13.30.40 STC07691 *BPXI039I SYSTEM LIMIT SHRLIBRGNSIZE HAS REACHED 95% OF ITS CURRENT CAPACITY OF 78643200
13.30.50 STC07691 BPXM023I (WSTOMSTC) CATC0001I CA-CCS Tomcat is starting
13.35.54 STC07691 BPXM023I (WSTOMSTC) CATC0002I CA-CCS Tomcat started in: 210795 ms (Apache Tomcat/9.0.27)
Are there any configurations to lower and/or limit the resources that the task can take?
Endevor V19
Web Services
The web services server resides in a test system with limited resource, before starting Endevor Tomcat instance, system is already close to the SHRLIBRGNSIZE limit, increase SHRLIBRGNSIZE could resolve the BPXI039I message.
Use the DISPLAY OMVS,OPTIONS command to display current OMVS options.
Use the SETOMVS operator command to change SHRLIBRGNSIZE dynamically, or the BPXPRMxx PARMLIB member for permanent changes.
By default, CCS Apache Tomcat has the -Xshareclasses option to improve performance, and Endevor web service is based on CCS Tomcat.
Comment out the following line in WSTOMENV to disable Tomcat caching, which will lower Tomcat STC usage towards SHRLIBRGNSIZE.
#IJO="$IJO -Xshareclasses:name=cache1"
Restart Tomcat after any change made in WSTOMENV
If there are other Web Based application (Tomcat) installed on the same system, use the same Java version for all Tomcat instance could save JVM shared library (.so) storage usage.
Follow IBM document to adjust SHRLIBRGNSIZE and learn how to analyze shared library space usage.