Why Does Transaction Debugging Frequently Fail?
Ensure that the following conditions are met before debugging:
- The resource group is running.
- The network between the debugging node of the resource group and the tested application is normal.
- Log in to the Elastic Cloud Server (ECS) management console.
- Find the debugging and execution nodes. Then, log in to the nodes.
- Run the curl url command (url is the URL of the tested application) to check whether the network is normal.
If the preceding conditions are met, debug the transaction. Click View Log to check whether the returned content is correct.
If the returned content contains error information, check that the entered parameters and configured contents of the packet are correct.
Pressure Test Project Management FAQs
- What Are the Differences Between Think Time and Duration in CodeArtsPerfTest?
- What Is the Number of Concurrent Users?
- How Do I Fill in Packets?
- Why Does Transaction Debugging Frequently Fail?
- Which Headers Are Mandatory in an HTTP-based Packet Request?
- Why Is the CPU Usage of the Execution Node Used for the Pressure Test Constantly High?
- What Are the Differences Between Global Variables and Variables Extracted from Responses?
- What Is the Impact of the Bandwidth Applied for CodeArtsPerfTest on the Test?
- How Do I Perform Concurrent Tests?
- What Are the Differences Between a JMeter Test Project and a PerfTest Project?
- How Do I Check If the Global Variable Values Are Read Sequentially in a Test Task?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore