Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8024614

Option to bind agent to specific interface.

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: P2
    • Resolution: Duplicate
    • Affects Version/s: 7u40
    • Fix Version/s: tbd_minor
    • Component/s: core-svc
    • Labels:

      Description

      One commonly requested feature over the years have been to be able to bind the management agent to a specific interface. Today I got an e-mail from a customer requesting it yet again:

      ---
      Hi Marcus,

      Congratulation with the MissionControl release, we are lookng forward to start using it.

      I hope that you at some point get the time to help me with my problem:

      We have experienced when starting the JMX agent starts to listen 0.0.0.0:7091 and thus blocks the start of other JVMs on the same server node. Which setting should I use to restrict a JMX agent to only listen on a specific IP. My goal it to have multiple JMX agents (one for each JVM) running on port 7091 on a server node, e.g.:
      JMX agent for JVM1: IP1:7091
      JMX agent for JVM2: IP2:7091
      etc.
      ---

      It shouldn't be that hard to support this. Add another command line option and hack the RMI server socket factories.

      (On a historic note, the old RMP management server in JRockit 1.4 and before supported this.)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                hirt Marcus Hirt
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: