qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arnaud Simon <asi...@redhat.com>
Subject Re: "Configuration and Instrumentation Content Messages" AM1g/c/i
Date Fri, 01 Aug 2008 07:42:34 GMT
Hi Rahul,

Ted's document says: 
"This message contains a content record. Content records contain the
values of all properties or statistics in an object." 
Based on my observations, 'i' corresponds to the statistics and 'c' to
the properties. Ted can you confirm that please? 

So, for example a content message for a queue will contain the following
statistics: 
Package Name: qpid
Class Name: queue
Current Sample: Fri Jun 03 15:17:48 CEST 38585431
Object Created: Sat Sep 25 10:17:35 CEST 38585430
Object Deleted: Thu Jan 01 01:00:00 CET 1970
Object Id:   43347146497327108
Total messages enqueued: 47
Total messages dequeued: 47
Transactional messages enqueued: 0
Transactional messages dequeued: 0
Persistent messages enqueued: 0
Persistent messages dequeued: 0
Current size of queue in messages: 0
Current size of queue in bytes: 0
Total messages enqueued: 24927990185984
Total messages dequeued: 24927990185984
Transactional messages enqueued: 0
Transactional messages dequeued: 0
Persistent messages enqueued: 0
etc.......

Hope this helps

Arnaud


On Thu, 2008-07-31 at 21:57 +0100, mehtar@cs.man.ac.uk wrote:
> Hello Ted/qpid developer,
> 
> Thanks for updating us about changes in the management protocol. 
> 
> Just a quick thing here about "Configuration and Instrumentation Content 
> Messages"
> 
>  +-----+-----+-----+-------+-----------------------+
>  | 'A' | 'M' | '1' |'g/c/i'|          seq          |
>  +-----+-----+-----+-------+-----------------------+--------+
>  |                packageName (str8)                        |
>  +----------------------------------------------------------+
>  |                className (str8)                          |
>  +----------------------------------------------------------+
>  |                class hash (bin128)                       |
>  +-----+-----+-----+-----+-----+-----+-----+-----+----------+
>  | timestamp of current sample (datetime)        |
>  +-----+-----+-----+-----+-----+-----+-----+-----+
>  | time object was created (datetime)            |
>  +-----+-----+-----+-----+-----+-----+-----+-----+
>  | time object was deleted (datetime)            |
>  +-----+-----+-----+-----+-----+-----+-----+-----+
>  | objectId (uint64)                             |
>  +-----+-----+-----+-----+-----+-----+-----+-----+------------------------+
>  | config/inst values (in schema order)                                   |
>  +------------------------------------------------------------------------+
> 
> 
> In this above illustrated structure, 1. what is "config/inst values (in 
> schema order)" 2. how can i access those elements (is this the AMQP map?) 
> are they same as the | propCnt | statCnt | methodCnt | eventCnt | values in 
> the Schema response?
> 
> 
> I am accessing the field values upto objectID (uint64) by the following 
> code, but how would I access the further elements, i dont have clear idea.
> 
> SAMPLE CODE STARTS
> ----------
> ..
> // decode the package name
> String pakagename = decoder.readStr8();
> // decode the class name
> String classname = decoder.readStr8();
> System.out.println("Package Name: " + pakagename);
> System.out.println("Class Name: " + classname);
> // decode the schema hash
> decoder.readBin128();
> // decode the timestamp of current sample
> Date d1 = new Date(decoder.readDatetime());
> System.out.println("Current Sample: " + d1.toString());
> // decode the time object was created
> Date d2 = new Date(decoder.readDatetime());
> System.out.println("Object Created: " + d2.toString());
> // decode the time object was deleted
> Date d3 = new Date(decoder.readDatetime());
> System.out.println("Object Deleted: " + d3.toString());
> // Object Id
> long objectID=decoder.readUint64();
> System.out.println("Object Id:   " + objectID);
> 
> ... (what should be here to access "config/inst values (in schema order)" 
> from the above diagram ) ... ----- SAMPLE CODE ENDS
> 
> 
> 
> Thanks.
> 
> BR,
> rahul
> 


Mime
View raw message