THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Object MBean attributes can be classifiled under two categories :
- Properties : typed members of object (that is, of its class definition) which represent a configurable attribute of the class. In general, properties don't change frequently or may not change at all;
- Statistics : typed members of object(that is, of its class definition) which represents an instrumentation attribute of the class. Statistics are always read-only in nature and tend to change rapidly.
The JMX interface of an object MBean lets you retrieve attributes metadata using the standard JMX API. The following example is showing that.
...
Argument Name | Description | Type | Nullable | Note | |||
|---|---|---|---|---|---|---|---|
objectName | The object name of the target object MBean | javax.management.ObjectName | No | N.A. | |||
operationName | This is the operation to be invoked on the target MBean | java.lang.String | No | N.A. | |||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="811dbccc-9785-40e1-80a0-96aefa2421be"><ac:plain-text-body><![CDATA[ | parameters | These are the input parameters of the operation | java.lang.Object[] | No | N.A. | ]]></ac:plain-text-body></ac:structured-macro> | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fce16107-e620-4531-b9f8-703890897b1a"><ac:plain-text-body><![CDATA[ |
signature | The operation signature | java.lang.String [] | No | N.A. ]]></ac:plain-text-body></ac:structured-macro> |
While mostly the interface follows the same rules of javax.management.MBeanServer.invoke() the only difference resides on return type.
The mentioned JMX interface generally returns java.lang.Object. While this is the type that the management client see, the underlying object that is returned as result of an operation invocation on QMan is ALWAYS one of the following :
...