8

I am trying to use jmeter on the command line using:

./jmeter.sh -n -t testplan.jmx -l log.jtl

It works 8/10 times but some times it gets stuck on the message: waiting for possible shutdown message... I am using CentOS 6 and JMeter version 2.9 r1437961. My test plan has two thread groups which are configured to run consecutively from the GUI. Any suggestions as to what the problem might be?

Uwe Keim
  • 39,551
  • 56
  • 175
  • 291
previouslyactualname
  • 703
  • 2
  • 11
  • 25
  • 1
    Have you looked in Jmeter logs? The answer can be there. – Viktor Malyi May 13 '15 at 07:49
  • 1
    Adding to that, JMeter doesn't necessarily output anything after the `waiting for possibleshutdown message...`. It usually only outputs once every 30-60 seconds or so. – mhlz May 13 '15 at 10:06
  • Did you find the solution to this issue? I'm having the same problem in Linux only. It's all good in windows – xbmono Aug 20 '18 at 02:04
  • It's just bad UX design. By the time you notice the message, the indicated "waiting" phase has most likely already completed (unfortunately, with no immediate indication). If nothing else is being displayed, it is probably stuck on something it hasn't bothered to tell you about. I would recommend running without `-n` (to use the GUI mode), but that doesn't seem to be any more informative (as of version 4.0). As noted in the answers, the problem is most likely a failed connection within your tests and, if so, adding timeouts will likely make that obvious. – Brent Bradburn May 28 '19 at 23:30

3 Answers3

1

Did you set timeouts to your HTTP requests ? If not , then jmeter will wait infinitely for a response from server which can lead to such issue.

So fix is to set a timeout on connect and read in HTTP Request Defaults.

Also you shoud upgrade to JMeter 2.13.

UBIK LOAD PACK
  • 33,980
  • 5
  • 71
  • 116
0

To further breakdown UBIK LOAD PACK's comments,

  • Navigate to Testplan level and Add--> config Element --> HTTP Request Defaults.

  • Set the protocol, server Name and port (Not sure if you really need it, but worked for me)

  • Navigate to advanced tab and add timeout periods(milliseconds) to Connect and response timeouts( I set as 10000)

MvpPrasad
  • 1
  • 1
0

I started seeing this error when I mistakenly disabled my Test Suite in JMeter UI. I kept on running the jmeter command in terminal and was getting this error. Re-enabling it fixed the error. It was a dumb mistake but worth mentioning

Nish
  • 695
  • 1
  • 7
  • 14