[
https://issues.apache.org/jira/browse/QPID-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-396:
----------------------------------
Fix Version/s: (was: M2)
M3
Affects Version/s: M2
M1
Moving unresolved JIRAs from M2 to M3, in preparation for M2 release
> 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
> Fix For: M3
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
