Re: java broker 6.0.2 OOM

Guys, Not sure what i am doing wrong, i have set heap to 1gb and direct mem to 2gb after ~150k msgs queuedepth in the queue i am getting bellow error and broker is getting killed. Any suggestions? 2016-10-13 23:27:41,894 ERROR [IO-/10.16.1.34:46096] (o.a.q.s.Main) - Uncaught exception, shutting

Re: java broker 6.0.2 OOM

On 13 October 2016 at 19:54, rammohan ganapavarapu wrote: > Rob, > > Understood, we are doing negative testing like what will happened to broker > when all the consumers are down but producers are pumping messages, so i > was the in the impression that flow to disk

Re: java broker 6.0.2 OOM

Rob, Understood, we are doing negative testing like what will happened to broker when all the consumers are down but producers are pumping messages, so i was the in the impression that flow to disk threshold will avoid broker go bad because of OOM. So i have bumped up the heap and direct mem

[RESULT] [VOTE] Release Qpid Proton 0.15.0

There were 5 binding +1 votes, and no other votes received. The vote has passed. I will add the archives to the dist release repo and release the maven staging repo shortly. The website will be updated later after the artifacts have had time to sync to the mirrors and maven central.

Re: java broker 6.0.2 OOM

Here is the heap dump if any one interested. "HttpManagement-HTTP-121" prio=5 tid=121 RUNNABLE at java.lang.OutOfMemoryError.(OutOfMemoryError.java:48) at javax.security.auth.SubjectDomainCombiner.combine(SubjectDomainCombiner.java:241) Local Variable:

Re: java broker 6.0.2 OOM

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

java broker 6.0.2 OOM

Hi, 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,