Chapter 4. Resolved issues
4.1. Broker pod fails with an OutOfMemoryError
message
When restarted, the broker was using more memory to read messages from the journal than to process the same messages at runtime. This issue was causing the broker pod to fail with an OutOfMemoryError
message. This issue was related to ENTMQBR-2313. With AMQ Broker 7.7, ENTMQBR-2313 has been resolved and therefore the workaround documented for ENTMQMAAS-1952 is not required for AMQ Online 1.5.
4.2. Resolved issues for AMQ Online 1.5.1
The AMQ Online 1.5.1 patch release is now available. This micro release updates the Operator Metadata that is used to install AMQ Online 1.5.1 from the OpenShift OperatorHub or OLM.
For additional details about the issues resolved in AMQ Online 1.5.1, see AMQ Online 1.5.x Resolved Issues.
4.3. Resolved issues for AMQ Online 1.5.2
For additional details about the issues resolved in AMQ Online 1.5.2, see AMQ Online 1.5.x Resolved Issues.
4.4. Resolved issues for AMQ Online 1.5.3
For additional details about the issues resolved in AMQ Online 1.5.3, see AMQ Online 1.5.x Resolved Issues.
4.5. Resolved issues for AMQ Online 1.5.4
For additional details about the issues resolved in AMQ Online 1.5.4, see AMQ Online 1.5.x Resolved Issues.