Expose custom jmx port for connector metrics #7645
-
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You cannot expose any custom ports. However, it is not really clear to me why would you need it in this case ... Is that really how JMX works? That there are multiple different "JMX" subsystems? One for Connect and one for Connector? I'm not really JMX expert ... but I have a some doubts about it. I always assumed the JMX subsystem is JVM-wide. At the end, it is not the application which exposes the JMX. It is the JVM. If it would be the case that you need a separate port, how would the JMX be actually exposed on the "new" port? Can you share some examples of how would the commands to start Connect look like with multiple JMX listeners? |
Beta Was this translation helpful? Give feedback.
You cannot expose any custom ports. However, it is not really clear to me why would you need it in this case ...
Is that really how JMX works? That there are multiple different "JMX" subsystems? One for Connect and one for Connector? I'm not really JMX expert ... but I have a some doubts about it. I always assumed the JMX subsystem is JVM-wide. At the end, it is not the application which exposes the JMX. It is the JVM.
If it would be the case that you need a separate port, how would the JMX be actually exposed on the "new" port? Can you share some examples of how would the commands to start Connect look like with multiple JMX listeners?