Re: Getting null pointer exception while running .jmx file in server 123

Raju Sarkar wrote:
> Hello sir/mam,
>
> I'm performing load testing with 500 threads and 1800 ms timing with 4 sec
> of ram-up timing in server. When I was ran it for 1st time it was all good,
> afterward I'm not able to do it just because I'm getting nullpointer
> exception while running any .jmx files. Please look after it and help me
> fixing this issue. I'm getting the issue which is mentioned below.../
>
> "WARN StatusConsoleListener The use of package scanning to locate plugins
> is deprecated and will be removed in a future release
>
> WARN StatusConsoleListener The use of package scanning to locate plugins is
> deprecated and will be removed in a future release
>
> WARN StatusConsoleListener The use of package scanning to locate plugins is
> deprecated and will be removed in a future release
>
> WARN StatusConsoleListener The use of package scanning to locate plugins is
> deprecated and will be removed in a future release
>
> Creating summariser <summary>
>
> Created the tree successfully using /opt/federalStaging.jmx
>
> Starting standalone test @ 2024 May 20 09:37:18 IST (1716178038973)
>
> Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on
> port 4445
>
> Warning: Nashorn engine is planned to be removed from a future JDK release
>
> summary =      0 in 00:00:00 = ******/s Avg:     0 Min: 9223372036854775807
> Max: -9223372036854775808 Err:     0 (0.00%)
>
> Tidying up ...    @ 2024 May 20 09:37:23 IST (1716178043466)
>
> Error generating the report: java.lang.NullPointerException
>
> ... end of run"
>
  * You're getting the NPE because you're trying to generate HTML
    Reporting Dashboard from a non-existing .jtl results file.
  * The .jtl results file
    <https://cwiki.apache.org/confluence/display/JMETER/JtlFiles> isn't
    getting generated because your test fails somewhere somehow

Take a look atjmeter.log file 
<https://jmeter.apache.org/usermanual/get-started.html#logging>, the 
reason for the test failure should be there. If it's not there or it's 
not obvious - enable JMeter debug logging 
<https://www.blazemeter.com/blog/jmeter-logging>