Home Explore Help
Register Sign In
wangfan
/
weichi-crm-server
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 40e9c757f2
Branches Tags
weichi-crm-serv...
/
docker
/
log
/
nacos
/
nacos.log

nacos.log 67 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787 
  1. 2025-01-14 17:32:08,157 INFO Starting Nacos v1.2.1 on 35b64930e042 with PID 50 (/home/nacos/target/nacos-server.jar started by root in /home/nacos)
    2. 

  2. 

  3. 2025-01-14 17:32:08,160 INFO The following profiles are active: standalone
    4. 

  4. 

  5. 2025-01-14 17:32:09,823 INFO Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$67a503f8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    6. 

  6. 

  7. 2025-01-14 17:32:09,954 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)
    8. 

  8. 

  9. 2025-01-14 17:32:09,961 INFO Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@4bdeaabb' 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)
    10. 

  10. 

  11. 2025-01-14 17:32:09,963 INFO Bean 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$8c79a6aa] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    12. 

  12. 

  13. 2025-01-14 17:32:09,968 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)
    14. 

  14. 

  15. 2025-01-14 17:32:10,541 INFO Tomcat initialized with port(s): 8848 (http)
    16. 

  16. 

  17. 2025-01-14 17:32:10,575 INFO Starting service [Tomcat]
    18. 

  18. 

  19. 2025-01-14 17:32:10,576 INFO Starting Servlet Engine: Apache Tomcat/9.0.13
    20. 

  20. 

  21. 2025-01-14 17:32:10,598 INFO The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
    22. 

  22. 

  23. 2025-01-14 17:32:10,711 INFO Initializing Spring embedded WebApplicationContext
    24. 

  24. 

  25. 2025-01-14 17:32:10,712 INFO Root WebApplicationContext: initialization completed in 2498 ms
    26. 

  26. 

  27. 2025-01-14 17:32:10,984 INFO Use Mysql as the driver
    28. 

  28. 

  29. 2025-01-14 17:32:19,667 INFO Reflections took 29 ms to scan 1 urls, producing 6 keys and 24 values 
    30. 

  30. 

  31. 2025-01-14 17:32:19,690 INFO Reflections took 2 ms to scan 1 urls, producing 2 keys and 12 values 
    32. 

  32. 

  33. 2025-01-14 17:32:19,695 INFO Reflections took 2 ms to scan 1 urls, producing 3 keys and 15 values 
    34. 

  34. 

  35. 2025-01-14 17:32:20,064 WARN Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'opsController' defined in URL [jar:file:/home/nacos/target/nacos-server.jar!/BOOT-INF/lib/nacos-config-1.2.1.jar!/com/alibaba/nacos/config/server/controller/OpsController.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dumpService': Invocation of init method failed; nested exception is java.lang.RuntimeException: Nacos Server did not start because dumpservice bean construction failure :
    36. 

  36. No DataSource set
    37. 

  37. 

  38. 2025-01-14 17:32:20,069 INFO Stopping service [Tomcat]
    39. 

  39. 

  40. 2025-01-14 17:32:20,072 WARN The web application [nacos] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    41. 

  41.  java.lang.Object.wait(Native Method)
    42. 

  42.  java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
    43. 

  43.  com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)
    44. 

  44. 

  45. 2025-01-14 17:32:20,072 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.server.Timer-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    46. 

  46.  sun.misc.Unsafe.park(Native Method)
    47. 

  47.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    48. 

  48.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    49. 

  49.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    50. 

  50.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    51. 

  51.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    52. 

  52.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    53. 

  53.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    54. 

  54.  java.lang.Thread.run(Thread.java:748)
    55. 

  55. 

  56. 2025-01-14 17:32:20,073 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.server.Timer-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    57. 

  57.  sun.misc.Unsafe.park(Native Method)
    58. 

  58.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    59. 

  59.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    60. 

  60.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    61. 

  61.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    62. 

  62.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    63. 

  63.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    64. 

  64.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    65. 

  65.  java.lang.Thread.run(Thread.java:748)
    66. 

  66. 

  67. 2025-01-14 17:32:20,074 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    68. 

  68.  sun.misc.Unsafe.park(Native Method)
    69. 

  69.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    70. 

  70.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    71. 

  71.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    72. 

  72.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    73. 

  73.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    74. 

  74.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    75. 

  75.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    76. 

  76.  java.lang.Thread.run(Thread.java:748)
    77. 

  77. 

  78. 2025-01-14 17:32:20,074 WARN The web application [nacos] appears to have started a thread named [nacos.naming.status.worker] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    79. 

  79.  sun.misc.Unsafe.park(Native Method)
    80. 

  80.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    81. 

  81.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    82. 

  82.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    83. 

  83.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    84. 

  84.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    85. 

  85.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    86. 

  86.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    87. 

  87.  java.lang.Thread.run(Thread.java:748)
    88. 

  88. 

  89. 2025-01-14 17:32:20,075 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.raft.notifier] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    90. 

  90.  sun.misc.Unsafe.park(Native Method)
    91. 

  91.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    92. 

  92.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    93. 

  93.  java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
    94. 

  94.  com.alibaba.nacos.naming.consistency.persistent.raft.RaftCore$Notifier.run(RaftCore.java:942)
    95. 

  95.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    96. 

  96.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    97. 

  97.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    98. 

  98.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    99. 

  99.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    100. 

  100.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    101. 

  101.  java.lang.Thread.run(Thread.java:748)
    102. 

  102. 

  103. 2025-01-14 17:32:20,075 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    104. 

  104.  sun.misc.Unsafe.park(Native Method)
    105. 

  105.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    106. 

  106.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    107. 

  107.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    108. 

  108.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    109. 

  109.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    110. 

  110.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    111. 

  111.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    112. 

  112.  java.lang.Thread.run(Thread.java:748)
    113. 

  113. 

  114. 2025-01-14 17:32:20,076 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    115. 

  115.  sun.misc.Unsafe.park(Native Method)
    116. 

  116.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    117. 

  117.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    118. 

  118.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    119. 

  119.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    120. 

  120.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    121. 

  121.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    122. 

  122.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    123. 

  123.  java.lang.Thread.run(Thread.java:748)
    124. 

  124. 

  125. 2025-01-14 17:32:20,076 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    126. 

  126.  sun.misc.Unsafe.park(Native Method)
    127. 

  127.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    128. 

  128.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    129. 

  129.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    130. 

  130.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    131. 

  131.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    132. 

  132.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    133. 

  133.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    134. 

  134.  java.lang.Thread.run(Thread.java:748)
    135. 

  135. 

  136. 2025-01-14 17:32:20,076 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    137. 

  137.  sun.misc.Unsafe.park(Native Method)
    138. 

  138.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    139. 

  139.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    140. 

  140.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    141. 

  141.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    142. 

  142.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    143. 

  143.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    144. 

  144.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    145. 

  145.  java.lang.Thread.run(Thread.java:748)
    146. 

  146. 

  147. 2025-01-14 17:32:20,077 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.server.list.notifier] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    148. 

  148.  sun.misc.Unsafe.park(Native Method)
    149. 

  149.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    150. 

  150.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    151. 

  151.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081)
    152. 

  152.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    153. 

  153.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    154. 

  154.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    155. 

  155.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    156. 

  156.  java.lang.Thread.run(Thread.java:748)
    157. 

  157. 

  158. 2025-01-14 17:32:20,077 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    159. 

  159.  sun.misc.Unsafe.park(Native Method)
    160. 

  160.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    161. 

  161.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    162. 

  162.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    163. 

  163.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    164. 

  164.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    165. 

  165.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    166. 

  166.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    167. 

  167.  java.lang.Thread.run(Thread.java:748)
    168. 

  168. 

  169. 2025-01-14 17:32:20,078 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.data.syncer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    170. 

  170.  sun.misc.Unsafe.park(Native Method)
    171. 

  171.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    172. 

  172.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    173. 

  173.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    174. 

  174.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    175. 

  175.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    176. 

  176.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    177. 

  177.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    178. 

  178.  java.lang.Thread.run(Thread.java:748)
    179. 

  179. 

  180. 2025-01-14 17:32:20,078 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    181. 

  181.  sun.misc.Unsafe.park(Native Method)
    182. 

  182.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    183. 

  183.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    184. 

  184.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    185. 

  185.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    186. 

  186.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    187. 

  187.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    188. 

  188.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    189. 

  189.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    190. 

  190.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    191. 

  191.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    192. 

  192.  java.lang.Thread.run(Thread.java:748)
    193. 

  193. 

  194. 2025-01-14 17:32:20,079 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    195. 

  195.  sun.misc.Unsafe.park(Native Method)
    196. 

  196.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    197. 

  197.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    198. 

  198.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    199. 

  199.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    200. 

  200.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    201. 

  201.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    202. 

  202.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    203. 

  203.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    204. 

  204.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    205. 

  205.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    206. 

  206.  java.lang.Thread.run(Thread.java:748)
    207. 

  207. 

  208. 2025-01-14 17:32:20,079 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    209. 

  209.  sun.misc.Unsafe.park(Native Method)
    210. 

  210.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    211. 

  211.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    212. 

  212.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    213. 

  213.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    214. 

  214.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    215. 

  215.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    216. 

  216.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    217. 

  217.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    218. 

  218.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    219. 

  219.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    220. 

  220.  java.lang.Thread.run(Thread.java:748)
    221. 

  221. 

  222. 2025-01-14 17:32:20,080 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    223. 

  223.  sun.misc.Unsafe.park(Native Method)
    224. 

  224.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    225. 

  225.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    226. 

  226.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    227. 

  227.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    228. 

  228.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    229. 

  229.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    230. 

  230.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    231. 

  231.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    232. 

  232.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    233. 

  233.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    234. 

  234.  java.lang.Thread.run(Thread.java:748)
    235. 

  235. 

  236. 2025-01-14 17:32:20,080 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    237. 

  237.  sun.misc.Unsafe.park(Native Method)
    238. 

  238.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    239. 

  239.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    240. 

  240.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    241. 

  241.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    242. 

  242.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    243. 

  243.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    244. 

  244.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    245. 

  245.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    246. 

  246.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    247. 

  247.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    248. 

  248.  java.lang.Thread.run(Thread.java:748)
    249. 

  249. 

  250. 2025-01-14 17:32:20,081 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    251. 

  251.  sun.misc.Unsafe.park(Native Method)
    252. 

  252.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    253. 

  253.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    254. 

  254.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    255. 

  255.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    256. 

  256.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    257. 

  257.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    258. 

  258.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    259. 

  259.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    260. 

  260.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    261. 

  261.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    262. 

  262.  java.lang.Thread.run(Thread.java:748)
    263. 

  263. 

  264. 2025-01-14 17:32:20,081 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    265. 

  265.  sun.misc.Unsafe.park(Native Method)
    266. 

  266.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    267. 

  267.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    268. 

  268.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    269. 

  269.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    270. 

  270.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    271. 

  271.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    272. 

  272.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    273. 

  273.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    274. 

  274.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    275. 

  275.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    276. 

  276.  java.lang.Thread.run(Thread.java:748)
    277. 

  277. 

  278. 2025-01-14 17:32:20,081 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    279. 

  279.  sun.misc.Unsafe.park(Native Method)
    280. 

  280.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    281. 

  281.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    282. 

  282.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    283. 

  283.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    284. 

  284.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    285. 

  285.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    286. 

  286.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    287. 

  287.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    288. 

  288.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    289. 

  289.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    290. 

  290.  java.lang.Thread.run(Thread.java:748)
    291. 

  291. 

  292. 2025-01-14 17:32:20,082 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    293. 

  293.  sun.misc.Unsafe.park(Native Method)
    294. 

  294.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    295. 

  295.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    296. 

  296.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    297. 

  297.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    298. 

  298.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    299. 

  299.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    300. 

  300.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    301. 

  301.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    302. 

  302.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    303. 

  303.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    304. 

  304.  java.lang.Thread.run(Thread.java:748)
    305. 

  305. 

  306. 2025-01-14 17:32:20,082 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    307. 

  307.  sun.misc.Unsafe.park(Native Method)
    308. 

  308.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    309. 

  309.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    310. 

  310.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    311. 

  311.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    312. 

  312.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    313. 

  313.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    314. 

  314.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    315. 

  315.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    316. 

  316.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    317. 

  317.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    318. 

  318.  java.lang.Thread.run(Thread.java:748)
    319. 

  319. 

  320. 2025-01-14 17:32:20,083 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    321. 

  321.  sun.misc.Unsafe.park(Native Method)
    322. 

  322.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    323. 

  323.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    324. 

  324.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    325. 

  325.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    326. 

  326.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    327. 

  327.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    328. 

  328.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    329. 

  329.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    330. 

  330.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    331. 

  331.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    332. 

  332.  java.lang.Thread.run(Thread.java:748)
    333. 

  333. 

  334. 2025-01-14 17:32:20,083 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    335. 

  335.  sun.misc.Unsafe.park(Native Method)
    336. 

  336.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    337. 

  337.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    338. 

  338.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    339. 

  339.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    340. 

  340.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    341. 

  341.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    342. 

  342.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    343. 

  343.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    344. 

  344.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    345. 

  345.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    346. 

  346.  java.lang.Thread.run(Thread.java:748)
    347. 

  347. 

  348. 2025-01-14 17:32:20,084 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    349. 

  349.  sun.misc.Unsafe.park(Native Method)
    350. 

  350.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    351. 

  351.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    352. 

  352.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    353. 

  353.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    354. 

  354.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    355. 

  355.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    356. 

  356.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    357. 

  357.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    358. 

  358.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    359. 

  359.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    360. 

  360.  java.lang.Thread.run(Thread.java:748)
    361. 

  361. 

  362. 2025-01-14 17:32:20,084 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    363. 

  363.  sun.misc.Unsafe.park(Native Method)
    364. 

  364.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    365. 

  365.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    366. 

  366.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    367. 

  367.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    368. 

  368.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    369. 

  369.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    370. 

  370.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    371. 

  371.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    372. 

  372.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    373. 

  373.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    374. 

  374.  java.lang.Thread.run(Thread.java:748)
    375. 

  375. 

  376. 2025-01-14 17:32:20,085 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    377. 

  377.  sun.misc.Unsafe.park(Native Method)
    378. 

  378.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    379. 

  379.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    380. 

  380.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    381. 

  381.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    382. 

  382.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    383. 

  383.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    384. 

  384.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    385. 

  385.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    386. 

  386.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    387. 

  387.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    388. 

  388.  java.lang.Thread.run(Thread.java:748)
    389. 

  389. 

  390. 2025-01-14 17:32:20,085 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    391. 

  391.  sun.misc.Unsafe.park(Native Method)
    392. 

  392.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    393. 

  393.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    394. 

  394.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    395. 

  395.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    396. 

  396.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    397. 

  397.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    398. 

  398.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    399. 

  399.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    400. 

  400.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    401. 

  401.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    402. 

  402.  java.lang.Thread.run(Thread.java:748)
    403. 

  403. 

  404. 2025-01-14 17:32:20,086 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    405. 

  405.  sun.misc.Unsafe.park(Native Method)
    406. 

  406.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    407. 

  407.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    408. 

  408.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    409. 

  409.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    410. 

  410.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    411. 

  411.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    412. 

  412.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    413. 

  413.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    414. 

  414.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    415. 

  415.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    416. 

  416.  java.lang.Thread.run(Thread.java:748)
    417. 

  417. 

  418. 2025-01-14 17:32:20,086 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    419. 

  419.  sun.misc.Unsafe.park(Native Method)
    420. 

  420.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    421. 

  421.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    422. 

  422.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    423. 

  423.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    424. 

  424.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    425. 

  425.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    426. 

  426.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    427. 

  427.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    428. 

  428.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    429. 

  429.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    430. 

  430.  java.lang.Thread.run(Thread.java:748)
    431. 

  431. 

  432. 2025-01-14 17:32:20,087 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    433. 

  433.  sun.misc.Unsafe.park(Native Method)
    434. 

  434.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    435. 

  435.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    436. 

  436.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    437. 

  437.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    438. 

  438.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    439. 

  439.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    440. 

  440.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    441. 

  441.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    442. 

  442.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    443. 

  443.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    444. 

  444.  java.lang.Thread.run(Thread.java:748)
    445. 

  445. 

  446. 2025-01-14 17:32:20,087 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    447. 

  447.  sun.misc.Unsafe.park(Native Method)
    448. 

  448.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    449. 

  449.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    450. 

  450.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    451. 

  451.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    452. 

  452.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    453. 

  453.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    454. 

  454.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    455. 

  455.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    456. 

  456.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    457. 

  457.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    458. 

  458.  java.lang.Thread.run(Thread.java:748)
    459. 

  459. 

  460. 2025-01-14 17:32:20,088 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    461. 

  461.  sun.misc.Unsafe.park(Native Method)
    462. 

  462.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    463. 

  463.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    464. 

  464.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    465. 

  465.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    466. 

  466.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    467. 

  467.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    468. 

  468.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    469. 

  469.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    470. 

  470.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    471. 

  471.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    472. 

  472.  java.lang.Thread.run(Thread.java:748)
    473. 

  473. 

  474. 2025-01-14 17:32:20,088 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    475. 

  475.  sun.misc.Unsafe.park(Native Method)
    476. 

  476.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    477. 

  477.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    478. 

  478.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    479. 

  479.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    480. 

  480.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    481. 

  481.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    482. 

  482.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    483. 

  483.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    484. 

  484.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    485. 

  485.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    486. 

  486.  java.lang.Thread.run(Thread.java:748)
    487. 

  487. 

  488. 2025-01-14 17:32:20,089 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    489. 

  489.  sun.misc.Unsafe.park(Native Method)
    490. 

  490.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    491. 

  491.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    492. 

  492.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    493. 

  493.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    494. 

  494.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    495. 

  495.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    496. 

  496.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    497. 

  497.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    498. 

  498.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    499. 

  499.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    500. 

  500.  java.lang.Thread.run(Thread.java:748)
    501. 

  501. 

  502. 2025-01-14 17:32:20,089 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    503. 

  503.  sun.misc.Unsafe.park(Native Method)
    504. 

  504.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    505. 

  505.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    506. 

  506.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    507. 

  507.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    508. 

  508.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    509. 

  509.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    510. 

  510.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    511. 

  511.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    512. 

  512.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    513. 

  513.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    514. 

  514.  java.lang.Thread.run(Thread.java:748)
    515. 

  515. 

  516. 2025-01-14 17:32:20,089 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    517. 

  517.  sun.misc.Unsafe.park(Native Method)
    518. 

  518.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    519. 

  519.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    520. 

  520.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    521. 

  521.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    522. 

  522.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    523. 

  523.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    524. 

  524.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    525. 

  525.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    526. 

  526.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    527. 

  527.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    528. 

  528.  java.lang.Thread.run(Thread.java:748)
    529. 

  529. 

  530. 2025-01-14 17:32:20,090 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    531. 

  531.  sun.misc.Unsafe.park(Native Method)
    532. 

  532.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    533. 

  533.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    534. 

  534.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    535. 

  535.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    536. 

  536.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    537. 

  537.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    538. 

  538.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    539. 

  539.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    540. 

  540.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    541. 

  541.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    542. 

  542.  java.lang.Thread.run(Thread.java:748)
    543. 

  543. 

  544. 2025-01-14 17:32:20,090 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    545. 

  545.  sun.misc.Unsafe.park(Native Method)
    546. 

  546.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    547. 

  547.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    548. 

  548.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    549. 

  549.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    550. 

  550.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    551. 

  551.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    552. 

  552.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    553. 

  553.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    554. 

  554.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    555. 

  555.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    556. 

  556.  java.lang.Thread.run(Thread.java:748)
    557. 

  557. 

  558. 2025-01-14 17:32:20,091 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.task.dispatcher] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    559. 

  559.  sun.misc.Unsafe.park(Native Method)
    560. 

  560.  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    561. 

  561.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    562. 

  562.  java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
    563. 

  563.  com.alibaba.nacos.naming.consistency.ephemeral.distro.TaskDispatcher$TaskScheduler.run(TaskDispatcher.java:94)
    564. 

  564.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    565. 

  565.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    566. 

  566.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    567. 

  567.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    568. 

  568.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    569. 

  569.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    570. 

  570.  java.lang.Thread.run(Thread.java:748)
    571. 

  571. 

  572. 2025-01-14 17:32:20,091 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    573. 

  573.  sun.misc.Unsafe.park(Native Method)
    574. 

  574.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    575. 

  575.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    576. 

  576.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    577. 

  577.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    578. 

  578.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    579. 

  579.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    580. 

  580.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    581. 

  581.  java.lang.Thread.run(Thread.java:748)
    582. 

  582. 

  583. 2025-01-14 17:32:20,092 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.distro.notifier] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    584. 

  584.  sun.misc.Unsafe.park(Native Method)
    585. 

  585.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    586. 

  586.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    587. 

  587.  java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
    588. 

  588.  com.alibaba.nacos.naming.consistency.ephemeral.distro.DistroConsistencyServiceImpl$Notifier.run(DistroConsistencyServiceImpl.java:380)
    589. 

  589.  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    590. 

  590.  java.util.concurrent.FutureTask.run(FutureTask.java:266)
    591. 

  591.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    592. 

  592.  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    593. 

  593.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    594. 

  594.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    595. 

  595.  java.lang.Thread.run(Thread.java:748)
    596. 

  596. 

  597. 2025-01-14 17:32:20,092 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    598. 

  598.  sun.misc.Unsafe.park(Native Method)
    599. 

  599.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    600. 

  600.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    601. 

  601.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    602. 

  602.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    603. 

  603.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    604. 

  604.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    605. 

  605.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    606. 

  606.  java.lang.Thread.run(Thread.java:748)
    607. 

  607. 

  608. 2025-01-14 17:32:20,093 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    609. 

  609.  sun.misc.Unsafe.park(Native Method)
    610. 

  610.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    611. 

  611.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    612. 

  612.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    613. 

  613.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    614. 

  614.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    615. 

  615.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    616. 

  616.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    617. 

  617.  java.lang.Thread.run(Thread.java:748)
    618. 

  618. 

  619. 2025-01-14 17:32:20,094 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    620. 

  620.  sun.misc.Unsafe.park(Native Method)
    621. 

  621.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    622. 

  622.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    623. 

  623.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    624. 

  624.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    625. 

  625.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    626. 

  626.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    627. 

  627.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    628. 

  628.  java.lang.Thread.run(Thread.java:748)
    629. 

  629. 

  630. 2025-01-14 17:32:20,095 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.naming.timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    631. 

  631.  sun.misc.Unsafe.park(Native Method)
    632. 

  632.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    633. 

  633.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    634. 

  634.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    635. 

  635.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    636. 

  636.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    637. 

  637.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    638. 

  638.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    639. 

  639.  java.lang.Thread.run(Thread.java:748)
    640. 

  640. 

  641. 2025-01-14 17:32:20,095 WARN The web application [nacos] appears to have started a thread named [com.alibaba.nacos.server.Timer-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    642. 

  642.  sun.misc.Unsafe.park(Native Method)
    643. 

  643.  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    644. 

  644.  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    645. 

  645.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    646. 

  646.  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    647. 

  647.  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    648. 

  648.  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    649. 

  649.  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    650. 

  650.  java.lang.Thread.run(Thread.java:748)
    651. 

  651. 

  652. 2025-01-14 17:32:20,100 INFO Nacos logs files: /home/nacos/logs/
    653. 

  653. 

  654. 2025-01-14 17:32:20,101 INFO Nacos conf files: /home/nacos/conf/
    655. 

  655. 

  656. 2025-01-14 17:32:20,101 INFO Nacos data files: /home/nacos/data/
    657. 

  657. 

  658. 2025-01-14 17:32:20,101 ERROR Nacos failed to start, please see /home/nacos/logs/nacos.log for more details.
    659. 

  659. 

  660. 2025-01-14 17:32:20,107 INFO 
    661. 

  661. 

  662. Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
    663. 

  663. 

  664. 2025-01-14 17:32:20,110 ERROR Application run failed
    665. 

  665. 

  666. org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'opsController' defined in URL [jar:file:/home/nacos/target/nacos-server.jar!/BOOT-INF/lib/nacos-config-1.2.1.jar!/com/alibaba/nacos/config/server/controller/OpsController.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dumpService': Invocation of init method failed; nested exception is java.lang.RuntimeException: Nacos Server did not start because dumpservice bean construction failure :
    667. 

  667. No DataSource set
    668. 

  668. 	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:769)
    669. 

  669. 	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:218)
    670. 

  670. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1308)
    671. 

  671. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1154)
    672. 

  672. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:538)
    673. 

  673. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
    674. 

  674. 	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
    675. 

  675. 	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
    676. 

  676. 	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
    677. 

  677. 	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
    678. 

  678. 	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:846)
    679. 

  679. 	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:863)
    680. 

  680. 	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
    681. 

  681. 	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
    682. 

  682. 	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
    683. 

  683. 	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
    684. 

  684. 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
    685. 

  685. 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
    686. 

  686. 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
    687. 

  687. 	at com.alibaba.nacos.Nacos.main(Nacos.java:35)
    688. 

  688. 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    689. 

  689. 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    690. 

  690. 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    691. 

  691. 	at java.lang.reflect.Method.invoke(Method.java:498)
    692. 

  692. 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
    693. 

  693. 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
    694. 

  694. 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
    695. 

  695. 	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:593)
    696. 

  696. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dumpService': Invocation of init method failed; nested exception is java.lang.RuntimeException: Nacos Server did not start because dumpservice bean construction failure :
    697. 

  697. No DataSource set
    698. 

  698. 	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:139)
    699. 

  699. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:419)
    700. 

  700. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1737)
    701. 

  701. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:576)
    702. 

  702. 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498)
    703. 

  703. 	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
    704. 

  704. 	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
    705. 

  705. 	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
    706. 

  706. 	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
    707. 

  707. 	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:273)
    708. 

  708. 	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1237)
    709. 

  709. 	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1164)
    710. 

  710. 	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:857)
    711. 

  711. 	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:760)
    712. 

  712. 	... 27 common frames omitted
    713. 

  713. Caused by: java.lang.RuntimeException: Nacos Server did not start because dumpservice bean construction failure :
    714. 

  714. No DataSource set
    715. 

  715. 	at com.alibaba.nacos.config.server.service.dump.DumpService.init(DumpService.java:142)
    716. 

  716. 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    717. 

  717. 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    718. 

  718. 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    719. 

  719. 	at java.lang.reflect.Method.invoke(Method.java:498)
    720. 

  720. 	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:363)
    721. 

  721. 	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:307)
    722. 

  722. 	at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
    723. 

  723. 	... 40 common frames omitted
    724. 

  724. 2025-01-14 17:33:51,947 INFO Starting Nacos v1.2.1 on e9cbfdbd1a32 with PID 50 (/home/nacos/target/nacos-server.jar started by root in /home/nacos)
    725. 

  725. 

  726. 2025-01-14 17:33:51,949 INFO The following profiles are active: standalone
    727. 

  727. 

  728. 2025-01-14 17:33:53,391 INFO Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$43dbdb21] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    729. 

  729. 

  730. 2025-01-14 17:33:53,477 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)
    731. 

  731. 

  732. 2025-01-14 17:33:53,480 INFO Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@5965d37' 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)
    733. 

  733. 

  734. 2025-01-14 17:33:53,481 INFO Bean 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$68b07dd3] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    735. 

  735. 

  736. 2025-01-14 17:33:53,487 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)
    737. 

  737. 

  738. 2025-01-14 17:33:53,978 INFO Tomcat initialized with port(s): 8848 (http)
    739. 

  739. 

  740. 2025-01-14 17:33:54,005 INFO Starting service [Tomcat]
    741. 

  741. 

  742. 2025-01-14 17:33:54,005 INFO Starting Servlet Engine: Apache Tomcat/9.0.13
    743. 

  743. 

  744. 2025-01-14 17:33:54,018 INFO The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
    745. 

  745. 

  746. 2025-01-14 17:33:54,079 INFO Initializing Spring embedded WebApplicationContext
    747. 

  747. 

  748. 2025-01-14 17:33:54,079 INFO Root WebApplicationContext: initialization completed in 2091 ms
    749. 

  749. 

  750. 2025-01-14 17:33:54,343 INFO Use Mysql as the driver
    751. 

  751. 

  752. 2025-01-14 17:33:55,085 INFO Reflections took 27 ms to scan 1 urls, producing 6 keys and 24 values 
    753. 

  753. 

  754. 2025-01-14 17:33:55,108 INFO Reflections took 2 ms to scan 1 urls, producing 2 keys and 12 values 
    755. 

  755. 

  756. 2025-01-14 17:33:55,114 INFO Reflections took 2 ms to scan 1 urls, producing 3 keys and 15 values 
    757. 

  757. 

  758. 2025-01-14 17:33:55,736 INFO Initializing ExecutorService 'applicationTaskExecutor'
    759. 

  759. 

  760. 2025-01-14 17:33:55,879 INFO Adding welcome page: class path resource [static/index.html]
    761. 

  761. 

  762. 2025-01-14 17:33:56,077 INFO Creating filter chain: Ant [pattern='/**'], []
    763. 

  763. 

  764. 2025-01-14 17:33:56,098 INFO Creating filter chain: any request, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@79145d5a, org.springframework.security.web.context.SecurityContextPersistenceFilter@b78a709, org.springframework.security.web.header.HeaderWriterFilter@183e8023, org.springframework.security.web.csrf.CsrfFilter@63b1d4fa, org.springframework.security.web.authentication.logout.LogoutFilter@a776e, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@2a3c96e3, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@cb191ca, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@1f2f9244, org.springframework.security.web.session.SessionManagementFilter@3e5499cc, org.springframework.security.web.access.ExceptionTranslationFilter@201b6b6f]
    765. 

  765. 

  766. 2025-01-14 17:33:56,152 INFO Exposing 2 endpoint(s) beneath base path '/actuator'
    767. 

  767. 

  768. 2025-01-14 17:33:56,178 INFO Initializing ExecutorService 'taskScheduler'
    769. 

  769. 

  770. 2025-01-14 17:33:56,339 INFO Tomcat started on port(s): 8848 (http) with context path '/nacos'
    771. 

  771. 

  772. 2025-01-14 17:33:56,344 INFO Started Nacos in 5.181 seconds (JVM running for 5.737)
    773. 

  773. 

  774. 2025-01-14 17:33:56,345 INFO Nacos logs files: /home/nacos/logs/
    775. 

  775. 

  776. 2025-01-14 17:33:56,345 INFO Nacos conf files: /home/nacos/conf/
    777. 

  777. 

  778. 2025-01-14 17:33:56,345 INFO Nacos data files: /home/nacos/data/
    779. 

  779. 

  780. 2025-01-14 17:33:56,346 INFO Nacos started successfully in stand alone mode.
    781. 

  781. 

  782. 2025-01-14 17:33:56,479 INFO Initializing Spring DispatcherServlet 'dispatcherServlet'
    783. 

  783. 

  784. 2025-01-14 17:33:56,480 INFO Initializing Servlet 'dispatcherServlet'
    785. 

  785. 

  786. 2025-01-14 17:33:56,485 INFO Completed initialization in 5 ms
    787. 

  787.