search

ali-bouali / spring-boot-3-jwt-security

Sample project on how to implement JWT security based using Spring boot 3 and Spring security 6
https://aliboucoding.com/p/securing-your-spring-boot-3-0-applications-with-json-web-tokens-jwt
Apache License 2.0
1.86k stars 870 forks source link

Memory leak issue, please help me fix #51

Closed nandhakumar2611 closed 2 months ago

nandhakumar2611 commented 1 year ago

I have implemented till register and login functionality.

T00: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: java.base@17.0.4.1/jdk.internal.misc.Unsafe.park(Native Method) java.base@17.0.4.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252) java.base@17.0.4.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672) java.base@17.0.4.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182) java.base@17.0.4.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) java.base@17.0.4.1/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: java.base@17.0.4.1/sun.nio.ch.Net.poll(Native Method) java.base@17.0.4.1/sun.nio.ch.NioSocketImpl.park(NioSocketImpl.java:181) java.base@17.0.4.1/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:285) java.base@17.0.4.1/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309) java.base@17.0.4.1/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350) java.base@17.0.4.1/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803) java.base@17.0.4.1/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) java.base@17.0.4.1/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: java.base@17.0.4.1/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) java.base@17.0.4.1/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: java.base@17.0.4.1/jdk.internal.misc.Unsafe.park(Native Method) java.base@17.0.4.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252) java.base@17.0.4.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672) java.base@17.0.4.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182) java.base@17.0.4.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122) java.base@17.0.4.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) java.base@17.0.4.1/java.lang.Thread.run(Thread.java:833)