WinSW: Automatically terminate runaway processes in Windows services

This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      In Jenkins projects we have many users complaining that the slave/agent is "already connected", because they have a runaway slave/agent process. It happens when WinSW gets terminated without executing the process shutdown logic (force kill) or when WinSW fails to terminate the process.

      As a part of WinSW 2.0, it would be great to create a logic, which...

      • records PID of the created process to the disc
      • performs status check of the previously spawned process upon restart
      • terminates the runaway process if required

      It can be done via WinSW 2 "plugin"
      Issue: https://github.com/kohsuke/winsw/issues/125

        1. Slave errors
          2 kB

            Assignee:
            Oleg Nenashev
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: