Unable to generate Load Test Report in XLT 5.6.0

Hey Hi @Team
Recently I have Upgraded the Framework to XLT 5.6.0 from XLT 5.5.0 I was running a sample Load test, the test is running successfully but the report is generating. Further reference attaching a screenshot below:

Could you please let me know the issue is with the Framework or do I need to do any changes?

Thanks in advance.

What are the start parameters you used?

mastercontroller.cmd -auto -embedded –report

On checking the log file getting the below exception:
Is that something causing Issues in generating a report?

[2021/09/08-18:41:31,439] ERROR [main] com.xceptance.xlt.mastercontroller.MasterController - Agentcontroller is not alive: Agent Controller ac001 https://localhost:8500
[2021/09/08-18:41:53,289] ERROR [AC-communication-default-pool0] com.xceptance.xlt.mastercontroller.MasterController - Failed to ping agent controller: Agent Controller ac001 https://localhost:8500
com.caucho.hessian.client.HessianRuntimeException: java.net.ConnectException: Connection refused: connect
at com.caucho.hessian.client.HessianProxy.sendRequest(HessianProxy.java:288)
at com.caucho.hessian.client.HessianProxy.invoke(HessianProxy.java:171)
at com.sun.proxy.$Proxy3.ping(Unknown Source)
at com.xceptance.xlt.agentcontroller.AgentControllerProxy.ping(AgentControllerProxy.java:328)
at com.xceptance.xlt.mastercontroller.MasterController$1.run(MasterController.java:415)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: java.net.ConnectException: Connection refused: connect
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:574)
at java.base/sun.nio.ch.Net.connect(Net.java:563)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333)
at java.base/java.net.Socket.connect(Socket.java:648)
at java.base/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:290)
at java.base/sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:182)
at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:474)
at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:569)
at java.base/sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:265)
at java.base/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:372)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:189)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1194)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1082)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:175)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1375)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1350)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:220)
at com.caucho.hessian.client.HessianURLConnection.getOutputStream(HessianURLConnection.java:97)
at com.caucho.hessian.client.HessianProxy.sendRequest(HessianProxy.java:286)
… 7 more

Hi vishnu3948,

I just retested running a load test the way you did and it worked (i.e. report was generated) so it looks there is no general issue with XLT 5.6.0.

Regarding the log entry: According to the stack trace, this error happened when the master controller was run in interactive mode, not in auto mode. Do you recall triggering the Ping command from the master controller menu? Does the timestamp of the error entry fall into the load testing period? Are there any other errors in the log?

Thanks for your input!

Hey, @jwerner Thanks for your quick response.

Do you recall triggering the Ping command from the master controller menu? - Yes
Does the timestamp of the error entry fall into the load testing period? - Yes

Are there any other errors in the log? - Yes
Log File path: xlt-5.6.0\results\Time-stamp\embedded_00\agent-stderr
Note: This exception occured while running in the auto mode

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.xbill.DNS.ResolverConfig (file:/C:/Users/eetgadmin/Desktop/ShopLoadTest/xlt-5.6.0/lib/dnsjava-2.1.9.jar) to method sun.net.dns.ResolverConfiguration.open()

WARNING: Please consider reporting this to the maintainers of org.xbill.DNS.ResolverConfig
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Hm, looks like the errors in the mastercontroller.log file are unrelated to the load test run in the screenshot. According to the timestamps, they happened after that load test has completed.

Also, please ignore the “WARNING: An illegal reflective access operation has occurred” and similar log entries. They are just warnings.

Is the issue of the report not being created automatically reproducable? I mean
could you please run mastercontroller.cmd -auto -embedded -report once more and see how that goes?

Thank you!

Thanks, @jwerner for your time and quick response.
I did not make any changes, just run the same Test-suit, as you asked to run, wondering like I have generated the report. :slightly_smiling_face: