Help Center > > FAQs> Pressure Test Project Management> Why Does Transaction Debugging Frequently Fail?

Why Does Transaction Debugging Frequently Fail?

Updated at: May 25, 2020 GMT+08:00

Ensure that the following conditions are met before debugging:

  • The resource group is running.
  • Ports 32001 and 32002 on the management node of the resource group are enabled in the security group.
  • The network between the management node of the resource group and the tested application is normal.
    1. Log in to the Elastic Cloud Server (ECS) management console.
    2. Find the management and execution nodes. Then, log in to the nodes.
    3. Run the curl url command (url is the URL of the tested application) to check whether the network is normal.

After confirming that the preceding conditions are met, debug the transaction and check whether the returned content is correct on the Result tab page.

Figure 1 Debugging results

If the returned content contains error information:

Check whether the entered parameters and configured contents of the packet are correct.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel