-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
-
Possibly other Jolokia calls could "leak" to a thirdparty SS as well
Setup:
1. Operator 7.11.1.CR2
2. AMQ Broker Stateful Set
3. A third-party statefulset (I've had Keycloak stateful set, but it doesn't seem to matter)
4. ActiveMQArtemisAddress instance
In this case, attached log would be printed out by AMQ Operator.
According to the log, it loops through all available statefulsets, including unrelated `keycloak` stateful set, and tries to contact them using Jolokia API call.
- is related to
-
ENTMQBR-8148 deprecate the address CR in favour of <address> broker properties
- Code Review