Uploaded image for project: 'AMQ Documentation'
  1. AMQ Documentation
  2. AMQDOC-2135

Release Note for Broker doesn't adhere to <max-size-bytes> setting

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0
    • None
    • Broker DOC
    • None
    • Release Notes
    • Hide
      Issue: The Broker doesn't adhere to the <max-size-bytes> or <address-full-policy> is set to BLOCK settings when using non-core protocols.
      Description: The Broker continues to receive messages even after the queue size limit is reached and the Java process runs out of RAM. As a result, the Broker becomes unresponsive and has to be restarted.
      Show
      Issue: The Broker doesn't adhere to the <max-size-bytes> or <address-full-policy> is set to BLOCK settings when using non-core protocols. Description: The Broker continues to receive messages even after the queue size limit is reached and the Java process runs out of RAM. As a result, the Broker becomes unresponsive and has to be restarted.

          rhn-support-pfestoso_jira Phil Festoso (Inactive)
          sjay@redhat.com Susan Jay
          Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

            Created:
            Updated:
            Resolved: