KTKOFSAA.war file Deployment is failing with the in Tomcat after I clone Uat to Prod
KTKOFSAA.war file Deployment is failing with the below error in Tomcat after I clone Uat to Prod-
"Fail- Application at context path [/KTKOFSAA] could not be started".
In logs we are getting beloow error-
com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextDestroyed WSSERVLET13: JAX-WS context listener destroyed28-Oct-2024 22:25:30.685 WARNING [http-nio-8080-exec-13] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [KTKOFSAA] appears to have started a thread named [Catalina-utility-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:5269)org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1301)org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1305)org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1305)org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1283)java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)java.lang.Thread.run(Thread.java:750)28-Oct-2024 22:25:30.685 WARNING [http-nio-8080-exec-13] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [KTKOFSAA] appears to have started a thread named [Message Logger Daemon Thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:java.lang.Object.wait(Native Method)java.lang.Object.wait(Object.java:502)com.iflex.fic.common.Queue.deQueue(Queue.java:118)com.iflex.fic.common.Log$Logger.pickMsgFromQueueForLog4j(Log.java:658)com.iflex.fic.common.Log$Logger.run(Log.java:622)28-Oct-2024 22:26:03.085 INFO [http-nio-8080-exec-12] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for