Re: [xmlblaster] Testing Protocols

["McIlwee, Craig" <craig.mcilwee at openroadsconsulting.com>]

Mohannad,

 

Why rely on xmlBlaster for your statistics at all? Would it not be easier to record the statistics yourself since you will be writing both the sending and receiving components? 

 

Have the sender mark the time that some number of messages were sent, then have the receiver mark the time that all messages were received.  (End time - start time) / # msgs = average time to process each message.  Repeat with different # of messages and different protocols.

 

If you need additional information at the xmlBlaster server you  can also look into something like a publish filter, or even build a custom version of xmlB and add insert your timing code there.

Craig
Open Roads Consulting, Inc.
757-546-3401
http://www.openroadsconsulting.com

---

From: Marcel Ruff [mailto:mr at marcelruff.info]
To: xmlblaster at server.xmlBlaster.org
Sent: Wed, 16 Apr 2008 05:45:45 -0400
Subject: Re: [xmlblaster] Testing Protocols

Mohannad wrote:
> thanks Zied,
> These files will be helpful. However, I need tools for measurement. I
> used jconsole but I didn't find for example a way to measure the time
> delay or packet transmission time.
>
> Is there any function in Jconsole will help to support this ?
MBeans -> org.xmlBlaster -> node/xyz/client/aClient/session/1

Here you have very limited possibilities:

Operations: pingClientCallbackServer() -> will ping the client and
report the millis needed
Attributes: pingRoundTripDelay -> Double click and you see a chart about
the millis needed

Marcel