jakartaee / messaging

Jakarta Messaging

https://eclipse.org/ee4j/messaging

Other

39 stars 33 forks source link

Standard set of server JMX MBeans #18

Closed glassfishrobot closed 3 years ago

glassfishrobot commented 13 years ago

A JMS implementation typically consists of one or more server processes.

As a monitoring client I would like to connect to these processes and discover a standard set of statistics (connections, queues, subscriptions, durables...) and for it to expose a standard set of administrative operations. such as JMS_SPEC_14,15,16 and 17.

Affected Versions

[1.1]

glassfishrobot commented 6 years ago

Issue Imported From: https://github.com/javaee/jms-spec/issues/18
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To: Unassigned

glassfishrobot commented 13 years ago

@glassfishrobot Commented Reported by colincrist

glassfishrobot commented 12 years ago

@glassfishrobot Commented @nigeldeakin said: This will be evaluated by the expert group for possible inclusion in the JMS 2.0 public draft. Tagging accordingly.

glassfishrobot commented 12 years ago

@glassfishrobot Commented @nigeldeakin said:

14 is a durable subscription browser

15 is a way to return queue depth

16 is a way to return durable subscription depth

17 is a way to find out the names/clientIDs of all durable subscriptions

glassfishrobot commented 13 years ago

@glassfishrobot Commented Issue-Links: is duplicated by JMS_SPEC-15 JMS_SPEC-16 JMS_SPEC-17

glassfishrobot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA JMS_SPEC-18

m-reza-rahman commented 3 years ago

Is this relevant any more, especially in terms of JMX? I would close this to reduce clutter.