JMeter: Stoptest.sh/Shutdown.sh doesn't work from Jenkins












0















I am running some performance tests from Jenkins. I do have two Windows machines with JMeter and I can configure from Jenkins which one to use. Everything works as expected here.



My issue: I did create another job for Stop/Shutdown the tests in case something goes wrong and you have a big run time. Whenever I try to summon Stoptest.sh/Shutdown.sh on the Windows machine that run tests, nothing happens.



How can I stop tests remotely? It has anything to do with the listening port? Thank you.



PS: Tests are ran using PSExec from Jenkin's Windows slave so there is no active CMD window on the screen.










share|improve this question



























    0















    I am running some performance tests from Jenkins. I do have two Windows machines with JMeter and I can configure from Jenkins which one to use. Everything works as expected here.



    My issue: I did create another job for Stop/Shutdown the tests in case something goes wrong and you have a big run time. Whenever I try to summon Stoptest.sh/Shutdown.sh on the Windows machine that run tests, nothing happens.



    How can I stop tests remotely? It has anything to do with the listening port? Thank you.



    PS: Tests are ran using PSExec from Jenkin's Windows slave so there is no active CMD window on the screen.










    share|improve this question

























      0












      0








      0








      I am running some performance tests from Jenkins. I do have two Windows machines with JMeter and I can configure from Jenkins which one to use. Everything works as expected here.



      My issue: I did create another job for Stop/Shutdown the tests in case something goes wrong and you have a big run time. Whenever I try to summon Stoptest.sh/Shutdown.sh on the Windows machine that run tests, nothing happens.



      How can I stop tests remotely? It has anything to do with the listening port? Thank you.



      PS: Tests are ran using PSExec from Jenkin's Windows slave so there is no active CMD window on the screen.










      share|improve this question














      I am running some performance tests from Jenkins. I do have two Windows machines with JMeter and I can configure from Jenkins which one to use. Everything works as expected here.



      My issue: I did create another job for Stop/Shutdown the tests in case something goes wrong and you have a big run time. Whenever I try to summon Stoptest.sh/Shutdown.sh on the Windows machine that run tests, nothing happens.



      How can I stop tests remotely? It has anything to do with the listening port? Thank you.



      PS: Tests are ran using PSExec from Jenkin's Windows slave so there is no active CMD window on the screen.







      jenkins jmeter






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 7:51









      bogdanovbogdanov

      367




      367
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead



          There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager



          enter image description here






          share|improve this answer
























          • Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

            – bogdanov
            Nov 23 '18 at 7:16











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407418%2fjmeter-stoptest-sh-shutdown-sh-doesnt-work-from-jenkins%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead



          There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager



          enter image description here






          share|improve this answer
























          • Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

            – bogdanov
            Nov 23 '18 at 7:16
















          1














          Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead



          There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager



          enter image description here






          share|improve this answer
























          • Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

            – bogdanov
            Nov 23 '18 at 7:16














          1












          1








          1







          Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead



          There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager



          enter image description here






          share|improve this answer













          Be aware that .sh is extension for Linux shell scripts, they cannot be executed by Windows command-line interpreter (CMD or Powershell) if you're running JMeter on Windows you need to go for shutdown.cmd or stoptest.cmd instead



          There is also AutoStop Listener plugin which can be used for conditional stopping of JMeter test basing on various criteria, it can be installed using JMeter Plugins Manager



          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 21 '18 at 7:58









          Dmitri TDmitri T

          71.2k33661




          71.2k33661













          • Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

            – bogdanov
            Nov 23 '18 at 7:16



















          • Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

            – bogdanov
            Nov 23 '18 at 7:16

















          Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

          – bogdanov
          Nov 23 '18 at 7:16





          Thanks! It worked. For some reason the port in jmeter.properties was set under 1000 and it did not listen to any. Setting it to 4445 solved the issue.

          – bogdanov
          Nov 23 '18 at 7:16


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407418%2fjmeter-stoptest-sh-shutdown-sh-doesnt-work-from-jenkins%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          How to fix TextFormField cause rebuild widget in Flutter

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith