- Newest
- Most votes
- Most comments
The error you're encountering during the automation process is related to a connection issue. The system is unable to access the URL http://localhost:8080/gapwalk-application/script/TRANBKP, resulting in a FileNotFoundException.
This could be due to several reasons:
-
The Tomcat server may not be running correctly or is not accessible on port 8080, despite the initial check showing a successful connection.
-
The gapwalk-application may not be deployed correctly on the server.
-
There might be a firewall or network issue preventing access to localhost.
-
The TRANBKP script may not exist at the specified location within the application.
To resolve this issue, try the following steps:
-
Verify that the Tomcat server is still running and accessible on port 8080 when the TRANBKP job is initiated.
-
Double-check that the gapwalk-application is correctly deployed on your Tomcat server.
-
Ensure you can access http://localhost:8080/gapwalk-application in a web browser on the same machine.
-
Review your application's configuration files to ensure all paths and URLs are correct, especially for the TRANBKP script.
-
Check the Tomcat logs for any errors related to the deployment or runtime of the application, particularly around the time when the TRANBKP job is supposed to run.
-
Verify that the TRANBKP script exists in the correct location within the gapwalk-application on the server.
-
If possible, try to access the TRANBKP script URL directly in a browser to see if it's reachable.
If the problem persists after trying these steps, you may need to review your project setup and deployment process to ensure all components are correctly configured and accessible. It might also be helpful to enable more detailed logging in your Tomcat server and application to gather more information about what's happening when the TRANBKP job is initiated.
Sources
getting the error while running excecute.xml of automation | AWS re:Post
answered a year ago
Relevant content
- AWS OFFICIALUpdated 8 months ago

Hey any update on the fix for this?