-
Bug
-
Resolution: Done
-
Major
-
EAP70 1.6.0.GA
Currently activemq thread pool system properties are set only according to CONTAINER_CORE_LIMIT value, but JAVA_CORE_LIMIT should still take precedence (see https://issues.jboss.org/browse/CLOUD-1524).
- is incorporated by
-
CLOUD-2369 [EAP7.1] OpenShift image updates and fixes
- Closed
- relates to
-
CLOUD-1524 [JAVA8] Recognize JAVA_CORE_LIMIT env var setting or replace it with CONTAINER_CORE_LIMIT in the documentation
- Verified
-
CLOUD-1925 [EAP71] Set activemq thread pool system properties
- Verified