2020-09-01 00:19:32,623 WARN clearConfigHistory start

2020-09-01 08:52:16,382 ERROR clearConfigHistory error : org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30763768ms.

2020-09-01 08:52:21,976 WARN HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=11h7m39s600ms367µs).

2020-09-01 08:52:48,291 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@7e7ad953 (Communications link failure

The last packet successfully received from the server was 24,232 milliseconds ago.  The last packet sent successfully to the server was 24,233 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:52:49,287 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@5726154a (Communications link failure

The last packet successfully received from the server was 25,216 milliseconds ago.  The last packet sent successfully to the server was 25,216 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:52:51,295 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@2272f2b4 (Communications link failure

The last packet successfully received from the server was 27,204 milliseconds ago.  The last packet sent successfully to the server was 27,205 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:08,192 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@1146a0d5 (Communications link failure

The last packet successfully received from the server was 44,084 milliseconds ago.  The last packet sent successfully to the server was 44,085 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:17,236 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@6094aad8 (Communications link failure

The last packet successfully received from the server was 53,119 milliseconds ago.  The last packet sent successfully to the server was 53,120 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:20,202 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@7660a1b7 (Communications link failure

The last packet successfully received from the server was 56,074 milliseconds ago.  The last packet sent successfully to the server was 56,075 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:27,099 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@79d9c819 (Communications link failure

The last packet successfully received from the server was 62,956 milliseconds ago.  The last packet sent successfully to the server was 62,957 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:46,005 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@3a565526 (Communications link failure

The last packet successfully received from the server was 81,852 milliseconds ago.  The last packet sent successfully to the server was 81,853 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:46,145 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@6efa9c85 (Communications link failure

The last packet successfully received from the server was 81,981 milliseconds ago.  The last packet sent successfully to the server was 81,982 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:53:49,107 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@148f403c (Communications link failure

The last packet successfully received from the server was 84,930 milliseconds ago.  The last packet sent successfully to the server was 84,931 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:04,911 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@4f977fdb (Communications link failure

The last packet successfully received from the server was 100,726 milliseconds ago.  The last packet sent successfully to the server was 100,726 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:15,059 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@2fa7c67 (Communications link failure

The last packet successfully received from the server was 110,863 milliseconds ago.  The last packet sent successfully to the server was 110,864 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:18,016 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@7179e98b (Communications link failure

The last packet successfully received from the server was 113,806 milliseconds ago.  The last packet sent successfully to the server was 113,807 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:23,823 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@492d410a (Communications link failure

The last packet successfully received from the server was 119,603 milliseconds ago.  The last packet sent successfully to the server was 119,603 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:42,738 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@af0af1a (Communications link failure

The last packet successfully received from the server was 138,506 milliseconds ago.  The last packet sent successfully to the server was 138,506 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:43,979 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@dd8a23f (Communications link failure

The last packet successfully received from the server was 139,734 milliseconds ago.  The last packet sent successfully to the server was 139,735 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:54:46,925 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@34d81b79 (Communications link failure

The last packet successfully received from the server was 142,672 milliseconds ago.  The last packet sent successfully to the server was 142,672 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:55:01,651 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@3e208b4a (Communications link failure

The last packet successfully received from the server was 157,386 milliseconds ago.  The last packet sent successfully to the server was 157,386 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:55:12,897 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@48050723 (Communications link failure

The last packet successfully received from the server was 168,620 milliseconds ago.  The last packet sent successfully to the server was 168,621 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 08:55:15,836 WARN HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@5ced6887 (Communications link failure

The last packet successfully received from the server was 171,550 milliseconds ago.  The last packet sent successfully to the server was 171,550 milliseconds ago.). Possibly consider using a shorter maxLifetime value.

2020-09-01 09:01:54,374 INFO Starting Nacos v1.3.2 on LAPTOP-88I27LA9 with PID 8232 (D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\target\nacos-server.jar started by qb in D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\bin)

2020-09-01 09:01:54,375 INFO The following profiles are active: standalone

2020-09-01 09:01:58,453 INFO Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$784ef282] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:01:58,552 INFO Bean 'objectPostProcessor' of type [org.springframework.security.config.annotation.configuration.AutowireBeanFactoryObjectPostProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:01:58,557 INFO Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@1ae8bcbc' of type [org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:01:58,558 INFO Bean 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$9d239534] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:01:58,563 INFO Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:01:59,178 INFO Tomcat initialized with port(s): 8848 (http)

2020-09-01 09:01:59,207 INFO Starting service [Tomcat]

2020-09-01 09:01:59,207 INFO Starting Servlet Engine: Apache Tomcat/9.0.13

2020-09-01 09:01:59,227 INFO The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Java\jdk1.8.0_251\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;D:\developerUtil\app\a_maven\apache-maven-3.6.3-bin\apache-maven-3.6.3\bin;D:\developerUtil\app\a_git\Git\cmd;D:\developerUtil\app\a_node\;D:\developerUtil\app\a_node\node_global;D:\developerUtil\app\a_svn\bin;D:\dataBase\app\a_mysql\mysql-5.7.30-winx64\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\Java\jdk1.8.0_251\bin;C:\Program Files\Java\jdk1.8.0_251\jre\bin;C:\Users\qb\.windows-build-tools\python27\;C:\Users\qb\AppData\Local\Microsoft\WindowsApps;;D:\developerUtil\app\visualCode\Microsoft VS Code\bin;C:\Users\qb\AppData\Roaming\npm;D:\developerUtil\app\idea\IntelliJ IDEA 2019.3.5\bin;;.]

2020-09-01 09:01:59,357 INFO Initializing Spring embedded WebApplicationContext

2020-09-01 09:01:59,357 INFO Root WebApplicationContext: initialization completed in 4898 ms

2020-09-01 09:01:59,712 INFO HikariPool-1 - Starting...

2020-09-01 09:01:59,915 INFO HikariPool-1 - Start completed.

2020-09-01 09:02:00,813 INFO Nacos-related cluster resource initialization

2020-09-01 09:02:00,838 INFO The cluster resource is initialized

2020-09-01 09:02:01,852 INFO Reflections took 222 ms to scan 1 urls, producing 6 keys and 24 values 

2020-09-01 09:02:01,935 INFO Reflections took 5 ms to scan 1 urls, producing 2 keys and 12 values 

2020-09-01 09:02:01,949 INFO Reflections took 8 ms to scan 1 urls, producing 3 keys and 15 values 

2020-09-01 09:02:03,575 INFO Initializing ExecutorService 'applicationTaskExecutor'

2020-09-01 09:02:03,813 INFO Adding welcome page: class path resource [static/index.html]

2020-09-01 09:02:04,371 INFO Creating filter chain: Ant [pattern='/**'], []

2020-09-01 09:02:04,421 INFO Creating filter chain: any request, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@5990e6c5, org.springframework.security.web.context.SecurityContextPersistenceFilter@5471388b, org.springframework.security.web.header.HeaderWriterFilter@4c36250e, org.springframework.security.web.csrf.CsrfFilter@a486d78, org.springframework.security.web.authentication.logout.LogoutFilter@142eef62, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@1601e47, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@50687efb, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@56e07a08, org.springframework.security.web.session.SessionManagementFilter@49f5c307, org.springframework.security.web.access.ExceptionTranslationFilter@7ef2d7a6]

2020-09-01 09:02:04,577 INFO Exposing 2 endpoint(s) beneath base path '/actuator'

2020-09-01 09:02:04,607 INFO Initializing ExecutorService 'taskScheduler'

2020-09-01 09:02:04,872 ERROR Failed to start component [Connector[HTTP/1.1-8848]]

org.apache.catalina.LifecycleException: Protocol handler start failed
	at org.apache.catalina.connector.Connector.startInternal(Connector.java:1001)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.core.StandardService.addConnector(StandardService.java:225)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.addPreviouslyRemovedConnectors(TomcatWebServer.java:259)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:197)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.startWebServer(ServletWebServerApplicationContext.java:311)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:164)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
	at com.alibaba.nacos.Nacos.main(Nacos.java:35)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:109)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:466)
Caused by: java.net.BindException: Address already in use: bind
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:236)
	at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:210)
	at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1067)
	at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:1149)
	at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:561)
	at org.apache.catalina.connector.Connector.startInternal(Connector.java:998)
	... 22 common frames omitted
2020-09-01 09:02:04,909 INFO Stopping service [Tomcat]

2020-09-01 09:02:04,922 WARN The web application [nacos] appears to have started a thread named [HikariPool-1 housekeeper] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,923 WARN The web application [nacos] appears to have started a thread named [MySQL Statement Cancellation Timer] 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.util.TimerThread.mainLoop(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)

2020-09-01 09:02:04,923 WARN The web application [nacos] appears to have started a thread named [HikariPool-1 connection adder] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,924 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.config.server.timer.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,924 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.config.server.timer.-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,924 WARN The web application [nacos] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:340)
 org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:194)
 org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,925 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,925 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,926 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,926 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,927 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,927 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,928 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,928 WARN The web application [nacos] appears to have started a thread named [I/O dispatcher 8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:255)
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,928 WARN The web application [nacos] appears to have started a thread named [nacos.publisher-com.alibaba.nacos.core.cluster.MembersChangeEvent] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
 com.alibaba.nacos.common.notify.DefaultPublisher.openEventHandler(DefaultPublisher.java:116)
 com.alibaba.nacos.common.notify.DefaultPublisher.run(DefaultPublisher.java:94)

2020-09-01 09:02:04,929 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.raft.notifier.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
 com.alibaba.nacos.naming.consistency.persistent.raft.RaftCore$Notifier.run(RaftCore.java:1052)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,929 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,930 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,930 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,930 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,931 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.data.syncer.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,931 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,932 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,932 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,932 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,933 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,933 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,934 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,934 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher.-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:102)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,935 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,935 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.notifier.0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
 com.alibaba.nacos.naming.consistency.ephemeral.distro.DistroConsistencyServiceImpl$Notifier.run(DistroConsistencyServiceImpl.java:416)
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 java.util.concurrent.FutureTask.run(FutureTask.java:266)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,936 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,936 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,937 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-7] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,937 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,938 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-9] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,938 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-10] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,939 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-11] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,939 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-12] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,940 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-14] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,940 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer.-15] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)

2020-09-01 09:02:04,955 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\logs

2020-09-01 09:02:04,958 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\conf

2020-09-01 09:02:04,959 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\data

2020-09-01 09:02:04,963 ERROR Startup errors : {}

org.springframework.boot.web.embedded.tomcat.ConnectorStartFailedException: Connector configured to listen on port 8848 failed to start
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.checkConnectorHasStarted(TomcatWebServer.java:232)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.checkThatConnectorsHaveStarted(TomcatWebServer.java:224)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:202)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.startWebServer(ServletWebServerApplicationContext.java:311)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:164)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
	at com.alibaba.nacos.Nacos.main(Nacos.java:35)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:109)
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:466)
2020-09-01 09:02:04,964 WARN [HttpClientManager] Start destroying HttpClient

2020-09-01 09:02:04,967 WARN [HttpClientManager] Destruction of the end

2020-09-01 09:02:16,382 WARN clearConfigHistory start

2020-09-01 09:04:53,934 INFO Starting Nacos v1.3.2 on LAPTOP-88I27LA9 with PID 3256 (D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\target\nacos-server.jar started by qb in D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\bin)

2020-09-01 09:04:53,935 INFO The following profiles are active: standalone

2020-09-01 09:04:57,840 INFO Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$c232bc6f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:04:57,939 INFO Bean 'objectPostProcessor' of type [org.springframework.security.config.annotation.configuration.AutowireBeanFactoryObjectPostProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:04:57,944 INFO Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@1f75a668' of type [org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:04:57,948 INFO Bean 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$e7075f21] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:04:57,953 INFO Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

2020-09-01 09:04:58,584 INFO Tomcat initialized with port(s): 8848 (http)

2020-09-01 09:04:58,617 INFO Starting service [Tomcat]

2020-09-01 09:04:58,618 INFO Starting Servlet Engine: Apache Tomcat/9.0.13

2020-09-01 09:04:58,639 INFO The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Java\jdk1.8.0_251\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;D:\developerUtil\app\a_maven\apache-maven-3.6.3-bin\apache-maven-3.6.3\bin;D:\developerUtil\app\a_git\Git\cmd;D:\developerUtil\app\a_node\;D:\developerUtil\app\a_node\node_global;D:\developerUtil\app\a_svn\bin;D:\dataBase\app\a_mysql\mysql-5.7.30-winx64\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\Java\jdk1.8.0_251\bin;C:\Program Files\Java\jdk1.8.0_251\jre\bin;C:\Users\qb\.windows-build-tools\python27\;C:\Users\qb\AppData\Local\Microsoft\WindowsApps;;D:\developerUtil\app\visualCode\Microsoft VS Code\bin;C:\Users\qb\AppData\Roaming\npm;D:\developerUtil\app\idea\IntelliJ IDEA 2019.3.5\bin;;.]

2020-09-01 09:04:58,791 INFO Initializing Spring embedded WebApplicationContext

2020-09-01 09:04:58,791 INFO Root WebApplicationContext: initialization completed in 4756 ms

2020-09-01 09:04:59,154 INFO HikariPool-1 - Starting...

2020-09-01 09:04:59,378 INFO HikariPool-1 - Start completed.

2020-09-01 09:05:00,059 INFO Nacos-related cluster resource initialization

2020-09-01 09:05:00,068 INFO The cluster resource is initialized

2020-09-01 09:05:00,548 INFO Reflections took 49 ms to scan 1 urls, producing 6 keys and 24 values 

2020-09-01 09:05:00,592 INFO Reflections took 5 ms to scan 1 urls, producing 2 keys and 12 values 

2020-09-01 09:05:00,602 INFO Reflections took 5 ms to scan 1 urls, producing 3 keys and 15 values 

2020-09-01 09:05:01,569 INFO Initializing ExecutorService 'applicationTaskExecutor'

2020-09-01 09:05:01,760 INFO Adding welcome page: class path resource [static/index.html]

2020-09-01 09:05:02,279 INFO Creating filter chain: Ant [pattern='/**'], []

2020-09-01 09:05:02,345 INFO Creating filter chain: any request, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@2c715e84, org.springframework.security.web.context.SecurityContextPersistenceFilter@f415a95, org.springframework.security.web.header.HeaderWriterFilter@1950e8a6, org.springframework.security.web.csrf.CsrfFilter@4a9cc6cb, org.springframework.security.web.authentication.logout.LogoutFilter@46074492, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@724f138e, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@c9413d8, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@47428937, org.springframework.security.web.session.SessionManagementFilter@12cd9150, org.springframework.security.web.access.ExceptionTranslationFilter@56e07a08]

2020-09-01 09:05:02,504 INFO Exposing 2 endpoint(s) beneath base path '/actuator'

2020-09-01 09:05:02,533 INFO Initializing ExecutorService 'taskScheduler'

2020-09-01 09:05:02,853 INFO Tomcat started on port(s): 8848 (http) with context path '/nacos'

2020-09-01 09:05:02,859 INFO Started Nacos in 10.217 seconds (JVM running for 11.037)

2020-09-01 09:05:02,859 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\logs

2020-09-01 09:05:02,863 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\conf

2020-09-01 09:05:02,864 INFO Nacos Log files: D:\developerUtil\code\mycode\mall_cloud\mall-cloud-alibaba\nacos\data

2020-09-01 09:05:02,865 INFO Nacos started successfully in stand alone mode. use external storage

2020-09-01 09:07:09,625 INFO Initializing Spring DispatcherServlet 'dispatcherServlet'

2020-09-01 09:07:09,625 INFO Initializing Servlet 'dispatcherServlet'

2020-09-01 09:07:09,637 INFO Completed initialization in 12 ms

2020-09-01 09:15:00,871 INFO [capacityManagement] start correct usage

2020-09-01 09:15:00,894 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 09:15:01,014 WARN clearConfigHistory start

2020-09-01 09:25:00,897 INFO [capacityManagement] start correct usage

2020-09-01 09:25:00,910 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 09:25:01,023 WARN clearConfigHistory start

2020-09-01 09:35:00,912 INFO [capacityManagement] start correct usage

2020-09-01 09:35:00,922 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 09:35:01,025 WARN clearConfigHistory start

2020-09-01 09:45:00,923 INFO [capacityManagement] start correct usage

2020-09-01 09:45:00,931 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 09:45:01,029 WARN clearConfigHistory start

2020-09-01 09:55:00,932 INFO [capacityManagement] start correct usage

2020-09-01 09:55:00,940 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 09:55:01,033 WARN clearConfigHistory start

2020-09-01 10:05:00,943 INFO [capacityManagement] start correct usage

2020-09-01 10:05:00,951 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:05:01,036 WARN clearConfigHistory start

2020-09-01 10:15:00,953 INFO [capacityManagement] start correct usage

2020-09-01 10:15:00,961 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:15:01,039 WARN clearConfigHistory start

2020-09-01 10:25:00,962 INFO [capacityManagement] start correct usage

2020-09-01 10:25:00,969 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:25:01,043 WARN clearConfigHistory start

2020-09-01 10:35:00,971 INFO [capacityManagement] start correct usage

2020-09-01 10:35:00,979 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:35:01,047 WARN clearConfigHistory start

2020-09-01 10:45:00,998 INFO [capacityManagement] start correct usage

2020-09-01 10:45:01,008 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:45:01,054 WARN clearConfigHistory start

2020-09-01 10:55:01,008 INFO [capacityManagement] start correct usage

2020-09-01 10:55:01,016 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 10:55:01,059 WARN clearConfigHistory start

2020-09-01 11:05:01,018 INFO [capacityManagement] start correct usage

2020-09-01 11:05:01,023 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:05:01,061 WARN clearConfigHistory start

2020-09-01 11:15:01,024 INFO [capacityManagement] start correct usage

2020-09-01 11:15:01,031 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:15:01,068 WARN clearConfigHistory start

2020-09-01 11:25:01,032 INFO [capacityManagement] start correct usage

2020-09-01 11:25:01,035 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:25:01,104 WARN clearConfigHistory start

2020-09-01 11:35:01,037 INFO [capacityManagement] start correct usage

2020-09-01 11:35:01,044 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:35:01,107 WARN clearConfigHistory start

2020-09-01 11:45:01,046 INFO [capacityManagement] start correct usage

2020-09-01 11:45:01,052 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:45:01,112 WARN clearConfigHistory start

2020-09-01 11:55:01,055 INFO [capacityManagement] start correct usage

2020-09-01 11:55:01,062 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 11:55:01,118 WARN clearConfigHistory start

2020-09-01 12:05:01,063 INFO [capacityManagement] start correct usage

2020-09-01 12:05:01,069 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:05:01,122 WARN clearConfigHistory start

2020-09-01 12:15:01,071 INFO [capacityManagement] start correct usage

2020-09-01 12:15:01,076 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:15:01,127 WARN clearConfigHistory start

2020-09-01 12:25:01,076 INFO [capacityManagement] start correct usage

2020-09-01 12:25:01,085 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:25:01,132 WARN clearConfigHistory start

2020-09-01 12:35:01,086 INFO [capacityManagement] start correct usage

2020-09-01 12:35:01,091 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:35:01,136 WARN clearConfigHistory start

2020-09-01 12:45:01,093 INFO [capacityManagement] start correct usage

2020-09-01 12:45:01,098 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:45:01,140 WARN clearConfigHistory start

2020-09-01 12:55:01,099 INFO [capacityManagement] start correct usage

2020-09-01 12:55:01,105 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 12:55:01,145 WARN clearConfigHistory start

2020-09-01 13:05:01,106 INFO [capacityManagement] start correct usage

2020-09-01 13:05:01,112 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:05:01,150 WARN clearConfigHistory start

2020-09-01 13:15:01,114 INFO [capacityManagement] start correct usage

2020-09-01 13:15:01,123 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:15:01,156 WARN clearConfigHistory start

2020-09-01 13:25:01,124 INFO [capacityManagement] start correct usage

2020-09-01 13:25:01,133 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:25:01,162 WARN clearConfigHistory start

2020-09-01 13:35:01,133 INFO [capacityManagement] start correct usage

2020-09-01 13:35:01,138 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:35:01,164 WARN clearConfigHistory start

2020-09-01 13:45:01,141 INFO [capacityManagement] start correct usage

2020-09-01 13:45:01,147 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:45:01,169 WARN clearConfigHistory start

2020-09-01 13:55:01,149 INFO [capacityManagement] start correct usage

2020-09-01 13:55:01,155 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 13:55:01,174 WARN clearConfigHistory start

2020-09-01 14:05:01,155 INFO [capacityManagement] start correct usage

2020-09-01 14:05:01,163 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:05:01,182 WARN clearConfigHistory start

2020-09-01 14:15:01,164 INFO [capacityManagement] start correct usage

2020-09-01 14:15:01,172 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:15:01,186 WARN clearConfigHistory start

2020-09-01 14:25:01,174 INFO [capacityManagement] start correct usage

2020-09-01 14:25:01,182 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:25:01,199 WARN clearConfigHistory start

2020-09-01 14:35:01,183 INFO [capacityManagement] start correct usage

2020-09-01 14:35:01,205 WARN clearConfigHistory start

2020-09-01 14:35:01,219 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:45:01,220 INFO [capacityManagement] start correct usage

2020-09-01 14:45:01,224 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:45:01,232 WARN clearConfigHistory start

2020-09-01 14:55:01,225 INFO [capacityManagement] start correct usage

2020-09-01 14:55:01,230 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 14:55:01,240 WARN clearConfigHistory start

2020-09-01 15:05:01,232 INFO [capacityManagement] start correct usage

2020-09-01 15:05:01,241 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 15:05:01,246 WARN clearConfigHistory start

2020-09-01 15:15:01,243 INFO [capacityManagement] start correct usage

2020-09-01 15:15:01,250 WARN clearConfigHistory start

2020-09-01 15:15:01,254 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 15:25:01,256 INFO [capacityManagement] start correct usage

2020-09-01 15:25:01,256 WARN clearConfigHistory start

2020-09-01 15:25:01,262 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 15:35:01,262 WARN clearConfigHistory start

2020-09-01 15:35:01,264 INFO [capacityManagement] start correct usage

2020-09-01 15:35:01,273 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 15:45:01,272 WARN clearConfigHistory start

2020-09-01 15:45:01,275 INFO [capacityManagement] start correct usage

2020-09-01 15:45:01,287 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 15:55:01,281 WARN clearConfigHistory start

2020-09-01 15:55:01,288 INFO [capacityManagement] start correct usage

2020-09-01 15:55:01,291 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 16:05:01,286 WARN clearConfigHistory start

2020-09-01 16:05:01,292 INFO [capacityManagement] start correct usage

2020-09-01 16:05:01,295 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 16:15:01,290 WARN clearConfigHistory start

2020-09-01 16:15:01,295 INFO [capacityManagement] start correct usage

2020-09-01 16:15:01,300 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 16:25:01,296 WARN clearConfigHistory start

2020-09-01 16:25:01,301 INFO [capacityManagement] start correct usage

2020-09-01 16:25:01,310 INFO [capacityManagement] end correct usage, cost: 0s

2020-09-01 16:35:01,304 WARN clearConfigHistory start

2020-09-01 16:35:01,312 INFO [capacityManagement] start correct usage

2020-09-01 16:35:01,323 INFO [capacityManagement] end correct usage, cost: 0s

