You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have implemented till register and login functionality.
2023-07-28T00:34:37.293+05:30 INFO 4104 --- [on(2)-127.0.0.1] inMXBeanRegistrar$SpringApplicationAdmin : Application shutdown requested.
2023-07-28T00:34:37.306+05:30 INFO 4104 --- [on(2)-127.0.0.1] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2023-07-28T00:34:37.317+05:30 WARN 4104 --- [on(2)-127.0.0.1] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] 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:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
2023-07-28T00:34:37.318+05:30 WARN 4104 --- [on(2)-127.0.0.1] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [cluster-ClusterId{value='64c2bfbb45a85669df77c7d5', description='null'}-localhost:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/sun.nio.ch.Net.poll(Native Method)
[email protected]/sun.nio.ch.NioSocketImpl.park(NioSocketImpl.java:181)
[email protected]/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:285)
[email protected]/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)
[email protected]/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350)
[email protected]/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803)
[email protected]/java.net.Socket$SocketInputStream.read(Socket.java:966)
app//com.mongodb.internal.connection.SocketStream.read(SocketStream.java:113)
app//com.mongodb.internal.connection.SocketStream.read(SocketStream.java:138)
app//com.mongodb.internal.connection.InternalStreamConnection.receiveResponseBuffers(InternalStreamConnection.java:735)
app//com.mongodb.internal.connection.InternalStreamConnection.receiveMessageWithAdditionalTimeout(InternalStreamConnection.java:596)
app//com.mongodb.internal.connection.InternalStreamConnection.receiveCommandMessageResponse(InternalStreamConnection.java:440)
app//com.mongodb.internal.connection.InternalStreamConnection.receive(InternalStreamConnection.java:397)
app//com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:227)
app//com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:159)
[email protected]/java.lang.Thread.run(Thread.java:833)
2023-07-28T00:34:37.318+05:30 WARN 4104 --- [on(2)-127.0.0.1] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [cluster-rtt-ClusterId{value='64c2bfbb45a85669df77c7d5', description='null'}-localhost:27017] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/java.lang.Thread.sleep(Native Method)
app//com.mongodb.internal.connection.DefaultServerMonitor.waitForNext(DefaultServerMonitor.java:452)
app//com.mongodb.internal.connection.DefaultServerMonitor.access$1500(DefaultServerMonitor.java:66)
app//com.mongodb.internal.connection.DefaultServerMonitor$RoundTripTimeRunnable.run(DefaultServerMonitor.java:424)
[email protected]/java.lang.Thread.run(Thread.java:833)
2023-07-28T00:34:37.319+05:30 WARN 4104 --- [on(2)-127.0.0.1] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [MaintenanceTimer-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
[email protected]/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
The text was updated successfully, but these errors were encountered:
Neelesh-Janga
changed the title
Memory leak exceptions.
Please help me with the Memory leak exceptions.
Jul 27, 2023
Neelesh-Janga
changed the title
Please help me with the Memory leak exceptions.
Please help me with the Memory Leak Exceptions.
Jul 27, 2023
My Repo: https://github.com/Neelesh-Janga/JWT
I have implemented till register and login functionality.
The text was updated successfully, but these errors were encountered: