ActiveMQ
  1. ActiveMQ
  2. AMQ-2368

it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0, 5.3.0
    • Fix Version/s: 5.3.0
    • Component/s: JMX
    • Labels:
      None
    • Patch Info:
      Patch Available

      Description

      it doesn't make any sense for activemq-admin to load the SUNJMX env var from /etc/activemq.conf since if activemq-admin is run on the same system that the broker runs on in many cases the com.sun.management.jmxremote.port system property will be set in there. Since the activemq-admin script now tries to use the same port that the broker is already using the script now fails to run.

      You could argue that there is no point for the activemq-script to even use the SUNJMX variable at all, since there is little point in enabling a JMX connector for the script.

      However in the attached patch all I've done is to reset the SUNJMX var so that it doesn't use what is set in /etc/activemq.conf.

        Activity

          People

          • Assignee:
            Dejan Bosanac
            Reporter:
            Mats Henrikson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development