Which version (0.30, 0.32, 6.0) of the Java Broker are you using? How much memory (-Xmx) are you giving the broker? What persistent store are you using? How many messages are you expecting the broker to hold while the consumer is stopped?
The documentation gives guidance on flow to disk, and setting the memory correctly for your use case. For v6.0 you can find the documentation here http://qpid.apache.org/releases/qpid-java-6.0.0/java-broker/book/Java-Broker-Runtime-Flow-To-Disk.html http://qpid.apache.org/releases/qpid-java-6.0.0/java-broker/book/Java-Broker-Runtime-Memory.html Hope this helps? -- Rob On 19 January 2016 at 08:14, ecnuh <[email protected]> wrote: > > hello every body: > > I use java qpid, when consumer stoped but producer send message all > the time,cause memory not enough. > this may be becase all message Stored in memory. So, if I can set a > number when message reaching this number,then stored in disk? > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/java-qpid-when-consumer-stoped-but-producer-send-msg-all-the-time-cause-memory-not-enough-tp7636800.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
