Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2025-03-24 15:36:06 24-Mar-2025 20:36:06.964 INFO [http-nio-8080-exec-58] 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.
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.289 SEVERE [http-nio-8080-exec-58] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.290 SEVERE [http-nio-8080-exec-58] org.apache.catalina.core.StandardContext.startInternal Context [/lantern-powermonitor-service-2.0.0-DEV] startup failed due to previous errors
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.292 WARNING [http-nio-8080-exec-58] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [lantern-powermonitor-service-2.0.0-DEV] appears to have started a thread named [Catalina-utility-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- 2025-03-24 15:36:37 org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:4849)
- 2025-03-24 15:36:37 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1172)
- 2025-03-24 15:36:37 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1176)
- 2025-03-24 15:36:37 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1176)
- 2025-03-24 15:36:37 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1154)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
- 2025-03-24 15:36:37 org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
- 2025-03-24 15:36:37 [email protected]/java.lang.Thread.run(Thread.java:840)
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.293 WARNING [http-nio-8080-exec-58] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [lantern-powermonitor-service-2.0.0-DEV] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- 2025-03-24 15:36:37 [email protected]/java.lang.Object.wait(Native Method)
- 2025-03-24 15:36:37 [email protected]/java.lang.Object.wait(Object.java:338)
- 2025-03-24 15:36:37 [email protected]/java.util.TimerThread.mainLoop(Timer.java:537)
- 2025-03-24 15:36:37 [email protected]/java.util.TimerThread.run(Timer.java:516)
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.293 WARNING [http-nio-8080-exec-58] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [lantern-powermonitor-service-2.0.0-DEV] appears to have started a thread named [BufferPoolPruner-1-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- 2025-03-24 15:36:37 [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1679)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
- 2025-03-24 15:36:37 [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
- 2025-03-24 15:36:37 [email protected]/java.lang.Thread.run(Thread.java:840)
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.294 WARNING [http-nio-8080-exec-58] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [lantern-powermonitor-service-2.0.0-DEV] appears to have started a thread named [cluster-ClusterId{value='67e1c237c33bae0559d3ba1a', description='null'}-lanternsoftware.com:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- 2025-03-24 15:36:37 [email protected]/sun.nio.ch.Net.poll(Native Method)
- 2025-03-24 15:36:37 [email protected]/sun.nio.ch.NioSocketImpl.park(NioSocketImpl.java:186)
- 2025-03-24 15:36:37 [email protected]/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:553)
- 2025-03-24 15:36:37 [email protected]/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
- 2025-03-24 15:36:37 [email protected]/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
- 2025-03-24 15:36:37 [email protected]/java.net.Socket.connect(Socket.java:633)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:76)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:104)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.SocketStream.open(SocketStream.java:78)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:211)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:196)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:156)
- 2025-03-24 15:36:37 [email protected]/java.lang.Thread.run(Thread.java:840)
- 2025-03-24 15:36:37 24-Mar-2025 20:36:37.294 WARNING [http-nio-8080-exec-58] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [lantern-powermonitor-service-2.0.0-DEV] appears to have started a thread named [cluster-rtt-ClusterId{value='67e1c237c33bae0559d3ba1a', description='null'}-lanternsoftware.com:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- 2025-03-24 15:36:37 [email protected]/java.lang.Thread.sleep(Native Method)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.DefaultServerMonitor.waitForNext(DefaultServerMonitor.java:442)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.DefaultServerMonitor.access$1500(DefaultServerMonitor.java:68)
- 2025-03-24 15:36:37 com.mongodb.internal.connection.DefaultServerMonitor$RoundTripTimeRunnable.run(DefaultServerMonitor.java:413)
- 2025-03-24 15:36:37 [email protected]/java.lang.Thread.run(Thread.java:840)
- 2025-03-24 15:37:07 24-Mar-2025 20:37:07.200 INFO [BufferPoolPruner-1-thread-1] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [com.mongodb.internal.connection.PowerOfTwoBufferPool$IdleTrackingByteBuffer]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
- 2025-03-24 15:37:07 java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [com.mongodb.internal.connection.PowerOfTwoBufferPool$IdleTrackingByteBuffer]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
- 2025-03-24 15:37:07 at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1373)
- 2025-03-24 15:37:07 at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1361)
- 2025-03-24 15:37:07 at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1195)
- 2025-03-24 15:37:07 at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1162)
- 2025-03-24 15:37:07 at com.mongodb.internal.connection.PowerOfTwoBufferPool$BufferPool.prune(PowerOfTwoBufferPool.java:199)
- 2025-03-24 15:37:07 at java.base/java.util.HashMap$Values.forEach(HashMap.java:1065)
- 2025-03-24 15:37:07 at com.mongodb.internal.connection.PowerOfTwoBufferPool.prune(PowerOfTwoBufferPool.java:142)
- 2025-03-24 15:37:07 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
- 2025-03-24 15:37:07 at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
- 2025-03-24 15:37:07 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
- 2025-03-24 15:37:07 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
- 2025-03-24 15:37:07 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
- 2025-03-24 15:37:07 at java.base/java.lang.Thread.run(Thread.java:840)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement