- NLPs
Retrieve Value in Text Element
Capture Dropdown Elements
Unable to Select Radiobutton
Unable to Click Checkbox
Clearing the Session or Cookies
UI Identifier NLP
Drag & Drop NLP
Uploading Files NLP
Use MySQL Addon in NLPs- setup
Server Docker Deployment Errors
Secured Business Application Support
Troubleshooting Restricted Access to Testsigma
Why mobile device not displayed in Testsigma Mobile Test Recorder?
Unable to Create New Test Session
Agent Startup Failure Due to Used Ports
Tests Permanently Queued in Local Executions
Fix Testsigma Agent Registration Failures
Testsigma Agent Cleanup
Need of Apache Tomcat for Testsigma Agent- web apps
URL not accessible
Test Queued for a Long Time
Issues with UI Identifiers
Missing Elements in Recorder
Collecting HAR File
Errors with Browser Session
Page Loading Issues- mobile apps
Failed to Start Mobile Test Recorder
Troubleshooting “Failed to perform action Mobile Test Recorder” error
Why Test Execution State is Queued for a Long Time?
Why Mobile App Keeps Stopping After Successful Launch?
More pre-requisite settings
Why am I not able to start WDA Process on iPhone?
What are the Most Common causes for Click/Tap NLP Failure?
How to Find App Package & Activity in Android?
Cross-environment Compatible ID Locators (Android)
Why Accessibility IDs Over other Locators?
What are Common Android Issues & Proposed Solutions?
How to Find the App Bundle ID for iOS?
Developer Mode (iOS 16 & Above)
How to Handle iOS App Compatibility Issues?
How to Disable Play Protect for SMS Forwarder Installation?
How to Capture Network Logs in an Android Application?
Agent Startup Failure Due to Used Ports
While initiating the Testsigma Agent with the startup script, you might encounter errors related to the Apache Tomcat Server startup. These errors often occur due to conflicts in port.
Here's an error message that looks similar:
SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler
["http-nio-8080"]
java.net.BindException: Address already in useThis is the most common issue when one of your application is already running on the same port that is required by Apache Tomcat (ports 8080, 8005, 8009).
Steps to Resolve
1. Change the port Testsigma Agent uses to avoid conflict with other Apps.
- Shutdown the Testsigma Agent server by running the shutdown.sh (shutdown.bat for Windows) file.
- Navigate to the Apache Tomcat working directory.
- Open the server.xml file and find the port numbers mentioned above.
- Replace those with unused ports. We would suggest replacing those values with 8081,8006, and 8010, respectively.
- Restart the PC/Mac to restart the Apache server processes or services that might be running in the background.
- Restart the Testsigma Agent and use the updated port number.
2. Kill the application that's using the ports (8080, 8005, 8009)
-
For Windows:
- Open CMD with admin privileges (Run as Administrator).
- Find the process that's using the required port. Use the below command to find the processes running on port 8080:
netstat -ano | findstr :8080 - Find the PID for the process and send a kill signal with the following command:
taskkill /PID <typeyourPIDhere> /F - Repeat the same command in step 2 and confirm that the result is empty.
- Repeat the same steps for other ports 8005 and 8009.
-
For Mac:
- Open Terminal
- Find the process that's running on the required port. Use the below command to find the processes using the port 8080:
netstat -anop | grep :8080 - Find the PID for the process and send a process termination signal using pkill:
pkill <typeyourPIDhere> - Repeat the same command in step 2 and confirm that the result is empty. If the process is still present, use the below command to force kill using kill.
kill -SIGKILL <typeyourPIDhere> - Repeat the same steps for other ports, 8005 and 8009.