[jira] Updated: (QPID-1357) QMan events handling

["Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Gazzarini updated QPID-1357:
-----------------------------------

    Attachment: jconsole_showing_qman_events.JPG

Good  news : QMan is handling events!  It's working but the patch is not yet created because I should (must) correct something...

Anyway I attached a screenshot of JConsole that is showing the following scenario :

1) One C++ broker 
2) Three Qman connected with the broker above.

You can see that in this version, the namespace of MBean has changed to handle events. Now the pattern is :

Q-MAN: Q-MAN:brokerID=<brokerID>,type=<Event | Class>,package=<package>,name=<event or class name>,objectID=<objectID>

This is needed in order to correctly separate events and classes. As you can see on the attached screenshot under the Q-MAN domain there are two folders named "Class" and "Event".
Now, look under the Event folder. There are three kind of events : bind, queueDeclare and subscribe. 
The screenshot has been made to show the properties (arguments) of a queueDeclare event.

Last thing : note that QMan (for events only) is inserting two additional information other than arguments : severity level and timestamp (shown as a date)  

Any comments would be appreciated.

Regards,
Andrea





> QMan events handling
> --------------------
>
>                 Key: QPID-1357
>                 URL: https://issues.apache.org/jira/browse/QPID-1357
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: M4
>         Environment: J2SE 5 or higher, any OS that is supporting Java
>            Reporter: Andrea Gazzarini
>            Priority: Minor
>             Fix For: M4
>
>         Attachments: jconsole_showing_qman_events.JPG
>
>
> According to new features of QMF introduced with QPID-1327, QMan will be improved for events handling.
> The improvement will be done without any change on the preexisting features.
> Technically speaking, two new entities will be added on QMan domain :
> 1) QpidEvent : the entity which is encapsulating the event definition (and therefore the collected event instances). This is very similar to preexisting QpidClass entity (for classes).
> 2) EventMessageResponseHandler : message handler responsible to deal with event content messages (opcode = 'e')
> Regards,
> Andrea

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.