[
https://issues.apache.org/jira/browse/QPID-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-396.
------------------------------
Resolution: Won't Fix
As stated in the comments once you get an OOM exception you really can't do
anything. We *should* institute measures so that the broker pro-actively
monitors the amount of memory it is using and tries to prevent ever getting to
the point where it can no longer allocate memory
> Broker OutOfMemory Error handling
> ---------------------------------
>
> Key: QPID-396
> URL: https://issues.apache.org/jira/browse/QPID-396
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M1, M2
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
>
> When the broker runs out of memory the response to the client can be
> unpredicatable.
> If this is something that you believe may occur currently the best thing to
> do is to ensure that you are not hammering the broker with data. A slight
> pause between message sending should allow the broker time to throw the
> OutOfMemory Error during the handling of one of the methods rather than at
> the mina level when receiving the data.
> This should allow the broker to write a ConnectionClose frame back to the
> client. We could signal here that we are out of memory and stop listening for
> new connectons that will cause further OoM Errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
