Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins 2.134
      mqtt-notification-plugin 1.7
    • Similar Issues:

      Description

      We observed unexplainable OutOfMemoryExceptions in arbitratry places around Jenkins. After some investigation with Jconsole, we noticed, what seems to be a memory leak. The thread overview shows a very high number of unclosed MQTT related threads. We therefore assume MQTT threads are created but never closed?

        Attachments

          Activity

          Hide
          up_lange Urs Lange added a comment - - edited

          After investigating the source code:

          The mqtt client must be closed in a finally block in both: the perform() method and the doTestConnection() method. Doing this resolves the problem in our local environment.

          With the next release MqttClient will implement AutoClosable, which should help resolve this even cleaner.
          https://github.com/eclipse/paho.mqtt.java/pull/448

          Show
          up_lange Urs Lange added a comment - - edited After investigating the source code: The mqtt client must be closed in a finally block in both: the perform() method and the doTestConnection() method. Doing this resolves the problem in our local environment. With the next release MqttClient will implement AutoClosable, which should help resolve this even cleaner. https://github.com/eclipse/paho.mqtt.java/pull/448

            People

            • Assignee:
              Unassigned
              Reporter:
              up_lange Urs Lange
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: