Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60456

MessagingException message: IOException while sending message

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • email-ext-plugin
    • None

      There was excaltly similar case which was closed:

      https://issues.jenkins-ci.org/browse/JENKINS-56855

      But this still happens with versions mentioned that issue.. Only way to resolve this was to restart the jenkins and the emails started to work again..  It might take up to 1-2 months before facing this again.

      With debug logs I only see these:

      Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

       

       

       

          [JENKINS-60456] MessagingException message: IOException while sending message

          Petri Panula created issue -
          Petri Panula made changes -
          Description Original: There was excaltly similar case which was closed:

          https://issues.jenkins-ci.org/browse/JENKINS-56855

          But this still happens with versions mentioned that issue.. Only way to resolve this was to restart the jenkins and the emails started to work again..  It might take up to 1-2 months before facing this again.

           

           

           
          New: There was excaltly similar case which was closed:

          https://issues.jenkins-ci.org/browse/JENKINS-56855

          But this still happens with versions mentioned that issue.. Only way to resolve this was to restart the jenkins and the emails started to work again..  It might take up to 1-2 months before facing this again.

          With debug logs I only see these:

          Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

          Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

           

           

           
          Petri Panula made changes -
          Description Original: There was excaltly similar case which was closed:

          https://issues.jenkins-ci.org/browse/JENKINS-56855

          But this still happens with versions mentioned that issue.. Only way to resolve this was to restart the jenkins and the emails started to work again..  It might take up to 1-2 months before facing this again.

          With debug logs I only see these:

          Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

          Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

           

           

           
          New: There was excaltly similar case which was closed:

          https://issues.jenkins-ci.org/browse/JENKINS-56855

          But this still happens with versions mentioned that issue.. Only way to resolve this was to restart the jenkins and the emails started to work again..  It might take up to 1-2 months before facing this again.

          With debug logs I only see these:

          Analyzing: ext-xxxx.yyyyyy@xxxx.fiAnalyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Analyzing: ext-xxxx.yyyyyy@xxxx.fiLooking for: ext-xxxx.yyyyyy@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ext-xxxx.yyyyyy@xxxx.fi => found type: 0Adding recipients from trigger recipient listAnalyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Analyzing: jenkins@xxxx.fiLooking for: jenkins@xxxx.fi starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: jenkins@xxxx.fi => found type: 0Setting In-Reply-To since last build was not successfulSuccessfully created MimeMessageSending email to: ext-xxxx.yyyyyy@xxxx.fiMessagingException message: IOException while sending messageFinished: FAILURE

           

           

           
          Petri Panula made changes -
          Environment Original: Jenkins Version: 2.164.2
          email-ext-plugin version: 2.66
          New: Jenkins Version: 2.164.2
          email-ext-plugin version: 2.66

          java -version
          java version "1.8.0_131"
          Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
          Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
          Alex Earl made changes -
          Assignee Original: Alex Earl [ slide_o_mix ]

            Unassigned Unassigned
            pete123 Petri Panula
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: