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 i
on of the underlying message size, 300+ bytes minimum for an
empty message, do you have any thoughts on that?
Thanks again-
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-bandwidth-overheads-how-to-reduce-tp3718866p3729673.html
Sent from the ActiveMQ - User mailing list a
type-less, parameter-less, body-less message is 329
> bytes of data (383 bytes on the wire). That seems like a huge overhead when
> only sending small status messages comprising a few properties (obviously
> less of a concern if the message body runs into many KB or MB).
>
> Are t
ng a few properties (obviously
less of a concern if the message body runs into many KB or MB).
Are there any further options for reducing this size ?
Thanks again -
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-bandwidth-overheads-how-to-reduce-tp3718866p3721276.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ion-doesn-t-work-because-of-reference-to-specific-Ionic-Zlib-assembly-td3168180.html
> this posting I read that compression only applies to the message body, so
> not sure it would help with a property-only message like this one.
>
> I'd be grateful for any advice, or pointers to relevant c
ny advice, or pointers to relevant configuration
options which I've missed.
Would I see substantial differences using STOMP rather than Openwire?
Thanks in advance-
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-bandwidth-overheads-how-to-reduce-tp3718866p3718866.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
