Hello Ram,

may I refer you to the relevant section of the documentation [1].
As explained there in more detail, the broker keeps a representation of each message in heap even when flowing the message to disk. Therefore the amount of JVM heap memory puts a hard limit on the number of message the broker can hold.

Kind Regards,

[1] https://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Runtime-Memory.html

On 13/10/16 16:40, rammohan ganapavarapu wrote:

We are doing some load test using java broker 6.0.2 by stopping all
consumers, broker was crashed at 644359 messages. Even if i try to restart
broker its crashing with the same oom error.

  "persistentEnqueuedBytes" : 12731167222,
     "persistentEnqueuedMessages" : 644359,
     "queueDepthBytes" : 12731167222,
     "queueDepthMessages" : 644359,
     "totalDequeuedBytes" : 0,
     "totalDequeuedMessages" : 0,
     "totalEnqueuedBytes" : 12731167222,
     "totalEnqueuedMessages" : 644359,

JVM settings of broker: -Xmx512m -XX:MaxDirectMemorySize=1536m

"broker.flowToDiskThreshold" : "644245094",

So theoretically broker should flow those messages to disk after the
threshold right then broker shouldn't have caused OOM exception right? do i
have to do any other tuning?


To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to