On Mon, 2009-02-23 at 07:45 -0800, ffrenchm wrote:
> I've two questions :
>
> 1) I would like to know how I can disable the debug trace when I use the BDB
> persisent store in QPid (I've to much traces like bellow and it's realy not
> good for my benchmarks) :
>
> 2009-feb-23 16:34:10 trace RECV [127.0.0.1:60321]: Frame[BEbe; channel=0;
> {SessionCompletedBody: commands={ [39936,39993] }; }]
...
> 2009-feb-23 16:34:10 debug DeliveryRecord::setEnded() id=39995
> 2009-feb-23 16:34:10 debug Accepted 39995
These traces are controlled by the broker options -t/--trace or
--log-enable; the store has no separate controls for traces. If you use
-t, then the trace is turned ON for the broker AND all loaded modules.
Instead of that, you can use the --log-enable option, using trace+,
debug+ info+, notice+ warning+, error+ or critical+ as arguments for the
different trace levels. The "+" is optional, it prints all messages
levels at the one specified and above (eg warning prints only warning
messages; warning+ prints warning, error and critical messages.) The
-t/--trace option is equivalent to --log-enable trace+. See the broker
help info under --log-enable for details.
> Where are the options to have synchronous / asynchronous IO ? Did I make a
> mistake when downlowding the BDB module ? Is there another one ?
This store is only asynchronous. Although BDB is still used, it is no
longer on the message path for normal usage patterns - ie no message
data is stored in BDB. However, BDB will be used if flow-to-disk is
triggered, either because the messages are too large or other conditions
that may trigger this condition. All message content and transactions
are no stored in the async journal.
I hope this helps,
Kim
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
