To verify missing requests are sent from JMeter server, you can follow these steps:
Verify the configuration of the load balancer and the application servers to make sure they are configured correctly.
Use the Apache JMeter logging feature to see if the requests are sent from the JMeter server. You can configure the log level in the log4j2.xml file located in the /bin folder of your JMeter installation.
Use a network sniffer like tcpdump or Wireshark to monitor the network traffic and see if the requests are actually being sent from the JMeter server to the load balancer. You can also use tools like tcpdump or Wireshark to capture the packets on the load balancer and application server to verify the requests are received by the load balancer and being sent to the application servers.
You can also use Apache JMeter PerfMon Plugin to monitor the resource usage of the JMeter server and the application servers to see if there are any resource constraints causing the issue.
Here are a few reference links for more information:
One way to verify missing requests sent from a JMeter server is to use a tool such as tcpdump.
Here's an example of how you can use tcpdump to capture network traffic and check if your requests are being sent:
- Install tcpdump on the machine running the JMeter server:
- For Windows, you can use WinDump (https://windump.gitlab.io/), a port of tcpdump for Windows.
- For Linux, you can install tcpdump using the package manager (e.g. apt-get install tcpdump on Ubuntu).
- Start tcpdump and capture network traffic:
sudo tcpdump -s 0 -i -w <capture_file>.pcap 'port
- Replace with the name of the network interface you want to capture traffic from (e.g. eth0).
- Replace <port_number> with the port number used by your application (e.g. 443 for HTTPS).
- Replace <capture_file> with the name of the file where you want to save the capture.
Run your JMeter test and wait for it to finish.
Stop tcpdump by pressing Ctrl+C.
Use a tool such as Wireshark (https://www.wireshark.org/) to inspect the captured traffic and check if your requests are present in the capture file.
Note: tcpdump captures all network traffic, so it's a good idea to limit the capture to only the traffic related to your application using a filter (e.g. port <port_number> in the example above). This will make it easier to find the requests you're interested in when inspecting the capture file.