Hello Ramayan,
by common convention deprecated features eventually get removed
after a deprecation period. I don't know exactly when JMX was
first deprecated but in 6.0.x we stepped up the deprecation level
by removing the documentation and the JMX ports from the default
configuration. However, the actual code was not removed until
6.1.x. So, if you must you can still use it in 6.0.4.
I let someone else comment on the strategic decision for its
removal.
Kind regards,
Lorenz
On 23/08/16 05:03, Ramayan Tiwari wrote:
Found the JIRA for removing JMX
https://issues.apache.org/jira/browse/QPID-6915
Although, I couldn't find the reason why JMX is being removed. Could you
point out the reasons why JMX is no longer supported?
Thanks
Ramayan
On Mon, Aug 22, 2016 at 5:05 PM, Ramayan Tiwari <[email protected]>
wrote:
Hi all,
We (at Salesforce) are currently using Qpid java 0.32 broker and in the
process of moving to 6.0.4. We rely heavily on JMX to perform various kind
of broker monitoring and management.
There is no mention of JMX Management in the documentation of broker 6.0.4
[1]. The documentation of 6.0.0 has the following:
"*Important *
For new development work, the reader is directed towards the strategic Web
Management Console and the REST API. Use the Web/REST interfaces in
preference to JMX whenever possible. The JMX interface will be withdrawn in
a future release."
Our understanding was that JMX support will be deprecated and not
withdrawn, and we would very much prefer that way. It will require a huge
amount of work for us to move completely out of JMX. If it is going away,
could you let us know the timeline on this?
Thanks
Ramayan
[1]. https://qpid.apache.org/releases/qpid-java-6.0.4/java-
broker/book/Java-Broker-Management-Channel.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
