Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of tabish121@gmail.com
 designates 209.85.212.43 as permitted sender)
Subject: Re: Message bandwidth/overheads - how to reduce?
From: Timothy Bish <tabish121@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <1312889401295-3729673.post@n4.nabble.com>
References: <1312468130869-3718866.post@n4.nabble.com>
	 <1312548580.2675.2.camel@office> <1312552957681-3721276.post@n4.nabble.com>
	 <1312553356.2675.3.camel@office> <1312889401295-3729673.post@n4.nabble.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 09 Aug 2011 08:39:28 -0400
Message-ID: <1312893568.2751.3.camel@office>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2011-08-09 at 04:30 -0700, Phil White wrote:
> Thanks Tim
> 
> The subscriber URI is now:
>  
> activemq:tcp://HUSH7:61616?wireFormat.tightEncodingEnabled=true&transport.useLogging=true
> but I don't see any log files. I must be missing something - do I need to
> enable something else, or install a logger on the subscriber?
> 
> On the question of the underlying message size, 300+ bytes minimum for an
> empty message, do you have any thoughts on that?
> 
> Thanks again-
> 

Take a look at the ITrace and Tracer classes in NMS and the NMSTracer in
the NMS Unit tests src, that should give you an idea of what you need to
do to direct to logging to whatever source you want, we don't create
files since everyone has their own way of logging and storing that data.

There is no such thing as an empty message, each message has information
in it about the destination its directed to, the connection it came
from, and other provider specific properties that allow the broker to
route the messages.  

Regards

-- 
Tim Bish
------------
FuseSource
Email: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/