JMX Notifications generated by the server
The table below shows a list of Mbeans that generate JMX Notifications along with the conditions in which these notifications are generated.
Notification Condition | MBean's Object Name |
---|---|
Pubsub Notifications | |
Topic Creation and Deletion | Fiorano.jmx.notifications:ServiceType=EventManager,Name=TopicEventManager |
Opening, Closing and Setting of client ID on a Topic Connection | Fiorano.jmx.notifications:ServiceType=EventManager,Name=TopicConnectionEventManager |
Creation and Deletion of Topic Connection Factory | Fiorano.jmx.notifications:ServiceType=EventManager,Name=TCFEventManager |
Opening and Closing of a Topic Subscriber | Fiorano.jmx.notifications:ServiceType=EventManager,Name=SubscriberEventManager |
Opening and Closing of a Topic Publisher | Fiorano.jmx.notifications:ServiceType=EventManager,Name=PublishEventManager |
Ptp Notifications | |
Opening and Closing of a Queue Sender | Fiorano.jmx.notifications:ServiceType=EventManager,Name=SenderEventManager |
Opening and Closing of a Queue Receiver | Fiorano.jmx.notifications:ServiceType=EventManager,Name=ReceiverEventManager |
Queue Creation and Deletion | Fiorano.jmx.notifications:ServiceType=EventManager,Name=QueueEventManager |
Opening, Closing and setting of client ID on a Queue Connection | Fiorano.jmx.notifications:ServiceType=EventManager,Name=QueueConnectionEventManager |
Creation and Deletion of a Queue Connection Factory | Fiorano.jmx.notifications:ServiceType=EventManager,Name=QCFEventManager |
Number of messages in a queue exceeding the threshold defined at queue level | Fiorano.jmx.notifications:ServiceType=EventManager,Name=QueueEventManager |
Enabling and Disabling Notifications
By default all events are enabled. However, it is possible to turn on or off selective events in the server.
The server requires an instance of EventManager (which Is an implementation of NotificationBroadCaster) for each type of event. These event managers are passed to QueuingSubSystem and TopicSubSystem as dependencies. If an Event Manager dependency is left unresolved the event corresponding to that dependency is turned off.
The figure above shows all dependencies of Queuing Sub System in FioranoMQ. To turn off Queue Events set QueueEventManager to null. Similarly, to turn off Topic Connection Events set TCFEventManager to null.
Notification Classes
The FioranoMQ Server, when generating an event, creates an instance of a class depending on the event being generated. The FioranoMQ Server then inserts the required information within this instance raises the event. The diagram below shows various Notification classes and the relationships between them.
The diagram, below, shows the event ID (in blue) set by the server when generating the event. This ID can be used by any application to specify a filter when receiving events.