Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0, 3.1.0
-
Fix Version/s: 3.39.0
-
Component/s: Metrics, Support Tools
-
Labels:
-
Story Points:2
-
Sprint:NXRM Immortals Sprint 29
-
InvestmentLayer:support-escalated
Description
Nexus 2.x included jetty-jmx.xml so that Jetty related Mbeans are visible when Nexus is accessed over JMX.
Nexus 3 does not have this file so you could call this a regression - you have to know how to create and add the file yourself in nexus-args inside nexus.properties in order to see the jetty mbeans.
Expected
- add jetty-jmx.xml as peer to other jetty xml files and enable it via nexus-args by default OR perform the programmatic equivalent internally by default
- the jetty related mbeans should be visible for local and remote JMX connections
Ref:
https://support.sonatype.com/hc/en-us/articles/213465498-Configuring-Nexus-JVM-to-allow-JMX-connections
https://support.sonatype.com/hc/en-us/articles/218501277-Configuring-Nexus-Repository-Manager-3-To-Allow-JMX-Connections