Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop > Automation > Execute > Run execute.xml Ant script

0

Hi team,

I am encountering two errors in the "Execute all tests cases" phase. I'm not sure if these errors are related, but could you please help me with the solution?

While I have checked other Re:POST threads about similar errors, the suggested solutions did not resolve my current issue. (I initially thought it wouldn't apply since I'm already using v10.x.x, but I tried it anyway just to be sure) https://repost.aws/questions/QUEO1mQjRSR5afMPLkruEvsQ/aws-blu-age-l3-workshop-automation-step-error

◆Version Information

Transform Engine: 4.2

Tomcat: 10.0.18

◆Console Output Enter image description here

◆Error #1: catalina.log

05-Mar-2025 04:48:03.575 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [1.2.31] using APR version [1.7.0]. 05-Mar-2025 04:48:03.576 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true]. 05-Mar-2025 04:48:03.586 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1l 24 Aug 2021] 05-Mar-2025 04:48:04.155 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"] 05-Mar-2025 04:48:04.211 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1036] milliseconds 05-Mar-2025 04:48:04.389 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina] 05-Mar-2025 04:48:04.390 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.0.18] 05-Mar-2025 04:48:04.436 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\webapps\bac.war] 05-Mar-2025 04:48:05.257 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 05-Mar-2025 04:48:05.388 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\webapps\bac.war] has finished in [952] ms 05-Mar-2025 04:48:05.391 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\webapps\carddemo-service-1.0.0.war] 05-Mar-2025 04:48:05.398 INFO [main] org.apache.catalina.startup.ExpandWar.expand An expanded directory [D:\PhotonUser\Workshop\workspace\carddemo-automation\tomcat\webapps\carddemo-service-1.0.0] was found with a last modified time that did not match the associated WAR. It will be deleted. 05-Mar-2025 04:48:06.487 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 05-Mar-2025 04:48:06.490 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 05-Mar-2025 04:48:06.494 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/carddemo-service-1.0.0] startup failed due to previous errors 05-Mar-2025 04:48:06.502 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesObjectStreamClassCaches Failed to clear soft references from ObjectStreamClass$Caches for web application [carddemo-service-1.0.0] java.lang.ClassCastException: class java.io.ObjectStreamClass$Caches$1 cannot be cast to class java.util.Map (java.io.ObjectStreamClass$Caches$1 and java.util.Map are in module java.base of loader 'bootstrap') at org.apache.catalina.loader.WebappClassLoaderBase.clearCache(WebappClassLoaderBase.java:2369) at org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesObjectStreamClassCaches(WebappClassLoaderBase.java:2344) at org.apache.catalina.loader.WebappClassLoaderBase.clearReferences(WebappClassLoaderBase.java:1706) at org.apache.catalina.loader.WebappClassLoaderBase.stop(WebappClassLoaderBase.java:1634) at org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:429)

◆Error #2:localhost.log

05-Mar-2025 04:48:06.490 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class [ch.qos.logback.classic.selector.servlet.ContextDetachingSCL] java.lang.ClassNotFoundException: ch.qos.logback.classic.selector.servlet.ContextDetachingSCL at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1444) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1252) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:535) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:516) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4640) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5179) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698)

Topics
Migration & Modernization
Tags
AWS Blu Age
Language
English

asked a year ago245 views

2 Answers
1

The errors you're encountering during the "Execute all tests cases" phase of the AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop appear to be related to class loading and dependency issues. Here are some suggestions to address these problems:

  1. For Error #1 (catalina.log): The error suggests a problem with the deployment of the carddemo-service-1.0.0 web application. The context failed to start due to listener issues. This could be caused by missing dependencies or incompatible library versions.

  2. For Error #2 (localhost.log): The ClassNotFoundException for ch.qos.logback.classic.selector.servlet.ContextDetachingSCL indicates that the Logback library is missing from your classpath or there's a version mismatch.

To resolve these issues:

  1. Ensure all required dependencies are present in the WEB-INF/lib directory of your carddemo-service-1.0.0.war file. Pay special attention to the Logback library.

  2. Check for version compatibility between your application's dependencies and the Tomcat version you're using (10.0.18).

  3. Review the carddemo-service-1.0.0 web application's configuration, particularly the web.xml file, to make sure all specified listeners and their dependencies are available.

  4. If you're using Maven or Gradle for dependency management, verify that all necessary dependencies are correctly declared in your project's build file.

  5. Try clearing Tomcat's work directory to ensure no stale compiled classes are interfering with the deployment.

  6. If the issue persists, you may need to downgrade Tomcat to an earlier version that's known to be compatible with your application and its dependencies.

If these steps don't resolve the issue, you may need to review the full Tomcat logs for more detailed error messages or consult the AWS Blu Age documentation for specific troubleshooting steps related to this workshop.
Sources
AWS Blu Age Level 3 Self-Paced Troubleshooting Workshop - Codebase transformation - Transform Error | AWS re:Post

answered a year ago

EXPERT

reviewed a year ago

0

After rechecking the settings and script configurations, I found incorrect modifications in both the common.loader and Groovy script settings. I haven't been able to determine whether Error #2 was caused by common.loader alone, or whether Error #1 was caused by either Groovy alone or a combination of both Groovy and common.loader issues. I'm letting you know that the issue has been resolved for now.

answered a year ago

  • Gauri
    a year ago

    I am getting the same error/issue. Can you please help elaborate the resolution steps.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content