-
Bug
-
Resolution: Done
-
Major
-
7.9.1.GA
-
None
-
OCP 4.6
BA Operator 7.9.1
-
False
-
False
-
CR1
-
-
-
-
-
-
CR1
-
Undefined
-
-
-
---
-
---
-
With new default value for MaxMetaspaceSize (env. var. GC_MAX_METASPACE_SIZE), added as part of RHPAM-3245, we are now disabling automated configuration of the JVM values for the OCP images. We already have default values for MaxMetaspaceSize set in jboss kie modules. For some images, e.g. Business Central is set MaxMetaspaceSize to 1024m, is MaxMetaspaceSize override to lower value.
Places in jboss kie modules, where are set default values for images:
https://github.com/jboss-container-images/jboss-kie-modules/blob/master/os-eap-legacy/os-eap7-openshift/added/standalone.conf#L4
https://github.com/jboss-container-images/jboss-kie-modules/blob/master/jboss-kie-workbench/added/launch/jboss-kie-workbench.sh#L293
We need to make clear where and to what is this value for MaxMetaspaceSize set.
Probably the best would be to remove configuration of default value for MaxMetaspaceSize in Operator and just keep the one for images. We can probably increase the default value in standalone.conf file.
- is documented by
-
BXMSDOC-7009 Update default value for `MaxMetaspaceSize`
- Closed