[
https://issues.apache.org/jira/browse/QPID-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484425
]
Martin Ritchie commented on QPID-396:
-------------------------------------
116795 [SocketAcceptorIoProcessor-0.0] WARN
org.apache.mina.common.support.DefaultExceptionMonitor - Unexpected exception.
java.lang.OutOfMemoryError: Java heap space
Setting the ExceptionMonitor.setInstance(...) would allow us to catch this OOM
via the Mina callback.
> Broker OutOfMemory Error handling
> ---------------------------------
>
> Key: QPID-396
> URL: https://issues.apache.org/jira/browse/QPID-396
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Fix For: M2
>
>
> 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.
