L3 Workshop - Getting connection refused error executing the few batches job.
[echo] Run batch job: [CREASTMT] [echo] ------------------------------------------------------------------------------------------------------------------------------------------------ [get] Getting: http://localhost:8080/gapwalk-application/script/CREASTMT [get] To: D:\PhotonUser\Workshop\workspace\carddemo-automation\CREASTMT.log [echo] { "exitCode": 0, "stepName": "STEP040", "program": "CBSTM03A", "status": "Succeeded" } [delete] Deleting: D:\PhotonUser\Workshop\workspace\carddemo-automation\CREASTMT.log [echo] ------------------------------------------------------------------------------------------------------------------------------------------------ [echo] Dump JaCoCo test case execution trace [01-batches] [echo] ------------------------------------------------------------------------------------------------------------------------------------------------ [jacoco:dump] Connecting to localhost/127.0.0.1:6300 [jacoco:dump] Dumping execution data to D:\PhotonUser\Workshop\workspace\carddemo-automation\tests-cases\01-batches\code-coverage\jacoco.exec [echo] ------------------------------------------------------------------------------------------------------------------------------------------------ [echo] Stop Tomcat from [D:\PhotonUser\Workshop\workspace\carddemo-automation/tomcat] [echo] ------------------------------------------------------------------------------------------------------------------------------------------------ [exec] Using CATALINA_BASE: "D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat" [exec] Using CATALINA_HOME: "D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat" [exec] Using CATALINA_TMPDIR: "D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\temp" [exec] Using JRE_HOME: "C:\Work\Programs\jdk17.0.10_7" [exec] Using CLASSPATH: "D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\bin\bootstrap.jar;D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\bin\tomcat-juli.jar" [exec] Using CATALINA_OPTS: " -Dlogback.ContextSelector=JNDI -javaagent:C:\Work\Programs\jacoco\lib\jacocoagent.jar=output=tcpserver,append=false,includes=aws.bluage.l3.workshop.*" [exec] NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED 2025-10-17 05:54:23.750 - Checking for http://localhost:8080 - exception occurred : Connection refused: connect 2025-10-17 05:54:23.750 - Checking for http://localhost:8080 - return code : 500 / expected : 500 ==> ok ! [exec] Process on port 8080 killed 2025-10-17 05:54:24.028 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:26.032 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:28.037 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:30.040 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:32.042 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:34.045 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:36.047 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information 2025-10-17 05:54:38.051 - Checking for http://localhost:8080 - exception occurred : Connection refused: no further information
- Newest
- Most votes
- Most comments
The "Connection refused" errors you're seeing are expected behavior in this part of the AWS Blu Age L3 Workshop. These messages are appearing because the automation script is intentionally stopping the Tomcat server after successfully executing the batch jobs.
Looking at your log, I can see:
- The CREASTMT job executed successfully with exit code 0
- The JaCoCo test case execution trace was dumped
- The script then proceeded to stop Tomcat (as indicated by the "Stop Tomcat" message)
- After stopping Tomcat, the script is checking for the availability of the server at http://localhost:8080
- Since Tomcat has been stopped, these connection attempts are failing with "Connection refused" errors
This is normal behavior as part of the workshop's automation process. The script first runs the batch jobs, collects code coverage data, and then shuts down the server. The connection refused messages are simply confirming that the server has been successfully stopped.
If you need to continue with other parts of the workshop, you'll need to restart the Tomcat server. The workshop may have specific instructions for this in the next sections.
Sources
AWS Blu Age L3 Workshop - Error on Automation - Execute | AWS re:Post
AWS Blu Age L3 Certification - Test - Batch Execution Fails at step 5. Execute COMBTRAN job | AWS re:Post
