Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them.

geoserver-master | 0 14:50:09.815 INFO .ployDirectory Deployment of web application directory has finished in ms geoserver-master | 0 14:50:09.815 INFO .ployDirectory Deploying web application directory geoserver-master | 0 14:50:09.851 INFO .TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. geoserver-master | 0 14:50:09.774 INFO .ployDirectory Deployment of web application directory has finished in ms geoserver-master | 0 14:50:09.774 INFO .ployDirectory Deploying web application directory geoserver-master | 0 14:50:09.814 INFO .TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs.

geoserver-master | 0 14:50:09.735 INFO .ployDirectory Deployment of web application directory has finished in ms geoserver-master | 0 14:50:09.735 INFO .ployDirectory Deploying web application directory geoserver-master | 0 14:50:09.772 INFO .TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. geoserver-master | 0 14:50:09.604 INFO .ployDirectory Deployment of web application directory has finished in ms geoserver-master | 0 14:50:09.604 INFO .ployDirectory Deploying web application directory geoserver-master | 0 14:50:09.710 INFO .TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. geoserver-master | 0 14:50:09.533 INFO .ployDirectory Deployment of web application directory has finished in ms geoserver-master | 0 14:50:09.533 INFO .ployDirectory Deploying web application directory geoserver-master | 0 14:50:09.587 INFO .TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Threads are going to be renewed over time to try and avoid a probable memory leak. geoserver-master | 0 14:50:09.524 SEVERE .WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application created a ThreadLocal with key of type (value ]) and a value of type (value ]) but failed to remove it when the web application was stopped. geoserver-master | 0 14:50:09.513 INFO $1.run Created user preferences directory.

Stack trace of thread: geoserver-master | /.park(Native Method) geoserver-master | /.LockSupport.parkNanos(LockSupport.java:234) geoserver-master | /.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123) geoserver-master | /$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182) geoserver-master | /$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899) geoserver-master | /.getTask(ThreadPoolExecutor.java:1054) geoserver-master | /.runWorker(ThreadPoolExecutor.java:1114) geoserver-master | /$n(ThreadPoolExecutor.java:628) geoserver-master | /(Thread.java:834) geoserver-master | 0 14:50:09.506 SEVERE .WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application created a ThreadLocal with key of type (value ]) and a value of type (value ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak. Threads are going to be renewed over time to try and avoid a probable memory leak.Įxception detail： geoserver-master | 0 14:50:09.289 INFO Cleaned up javabean caches geoserver-master | 0 14:50:09.504 WARNING .WebappClassLoaderBase.clearReferencesThreads The web application appears to have started a thread named but has failed to stop it. WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application created a ThreadLocal with key of type (value ]) and a value of type (value ) but failed to remove it when the web application was stopped. I pass geoserver+minio to set s3 blobstore with gwc-s3-plugin, but when I restart geoserver, it reports the thread could not be killed.

Filewatcher s3