Apache ActiveMQ released v5.16.4. It includes improvements to support platform and cloud-readiness features for event-driven and queued messaging applications.
Join the DZone community and get the full member experience. In previous versions of ActiveMQ, an exception case that limited the ability for developers to code fully self-healing message flows was when a client sends a message that exceeds the broker’s max message size limit. ActiveMQ brokers detect this scenario and immediately close the connection to prevent any negative impact to the broker by misbehaving clients. While this approach is great for protecting the broker, it does not provide any signaling to the client as to how to respond. Before 5.16.4, clients configured with failover would reconnect and retry messages that were too large, causing sent messages to run in an infinite loop. In 5.16.4, the client library detects the scenario and throws a JMSException with Error Code (41300). Also, there is now a MaxFrameSizeExceeded exception that is accessible as the linked exception off the JMSException.
