Mule
  1. Mule
  2. MULE-259

JMX hot-redeployment dumps a number of errors to stdout

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.1
    • Component/s: Core: Containers
    • Labels:
      None
    • Similar Issues:
      MULE-282JMXAgent is not fully disposed of
      MULE-8401Error shown when connecting through JMX
      MULE-7713Instead of logging throughout the wrapper, mule should only send to stdout important information.
      MULE-349Extract common JMX code
      MULE-7166Memory Leak when using JMX
      MULE-8596JMX connection error when using JConsole
      MULE-870Unable to restart an Oracle AQ endpoint via JMX
      MULE-253JMX domain for MBeans should be configurable.
      MULE-2067Auto-increment port numbers
      MULE-3195MuleConfiguration API changes have broken JMX style-sheet compilation

      Description

      While hot-redeploying the mule in a container, a javax.management.InstanceAlreadyExistsException is thrown and dumped to the standard output. This does not seem to hurt the system at first, but litters the server log with irrelevant errors. In addition, no logger is being used, but a printStackTrace() call.

        Activity

        Atlassian Bamboo View RSS feed

          People

          • Assignee:
            Ross Mason
            Reporter:
            Andrew Perepelytsya
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development