请稍等 ...

AHAS整合问题

大目老师好，我在整合ahas的时候遇到了问题，引入了ahas依赖后项目启动报错。

    <dependency>
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter-alibaba-sentinel</artifactId>
        <exclusions>
            <exclusion>
                <groupId>com.alibaba.csp</groupId>
                <artifactId>sentinel-transport-simple-http</artifactId>
            </exclusion>
        </exclusions>
    </dependency>

    <dependency>
        <groupId>com.alibaba.csp</groupId>
        <artifactId>spring-boot-starter-ahas-sentinel-client</artifactId>
        <version>1.10.1</version>
    </dependency>

报错日志如下：

2021-12-06 15:40:48.203 INFO 12216 — [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2021-12-06 15:40:48.206 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [logback-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 $C o n d i t i o n O b j e c t . a w a i t N a n o s (A b s t r a c t Q u e u e d S y n c h r o n i z e r . j a v a : 2078) j a v a . u t i l . c o n c u r r e n t . S c h e d u l e d T h r e a d P o o l E x e c u t o r$ DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
java.util.concurrent.ScheduledThreadPoolExecutor $D e l a y e d W o r k Q u e u e . t a k e (S c h e d u l e d T h r e a d P o o l E x e c u t o r . j a v a : 809) j a v a . u t i l . c o n c u r r e n t . T h r e a d P o o l E x e c u t o r . g e t T a s k (T h r e a d P o o l E x e c u t o r . j a v a : 1074) j a v a . u t i l . c o n c u r r e n t . T h r e a d P o o l E x e c u t o r . r u n W o r k e r (T h r e a d P o o l E x e c u t o r . j a v a : 1134) j a v a . u t i l . c o n c u r r e n t . T h r e a d P o o l E x e c u t o r$ Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
2021-12-06 15:40:48.206 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [Timer-0] 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)
2021-12-06 15:40:48.206 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [com.alibaba.nacos.naming.client.listener] 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 $C o n d i t i o n O b j e c t . a w a i t N a n o s (A b s t r a c t Q u e u e d S y n c h r o n i z e r . j a v a : 2078) j a v a . u t i l . c o n c u r r e n t . L i n k e d B l o c k i n g Q u e u e . p o l l (L i n k e d B l o c k i n g Q u e u e . j a v a : 467) c o m . a l i b a b a . n a c o s . c l i e n t . n a m i n g . c o r e . E v e n t D i s p a t c h e r$ Notifier.run(EventDispatcher.java:114)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor $W o r k e r . r u n (T h r e a d P o o l E x e c u t o r . j a v a : 624) j a v a . l a n g . T h r e a d . r u n (T h r e a d . j a v a : 748) 2021 - 12 - 0615 : 40 : 48.207 W A R N 12216 - - - [m a i n] o . a . c . l o a d e r . W e b a p p C l a s s L o a d e r B a s e : T h e w e b a p p l i c a t i o n [R O O T] a p p e a r s t o h a v e s t a r t e d a t h r e a d n a m e d [c o m . a l i b a b a . n a c o s . n a m i n g . b e a t . s e n d e r] b u t h a s f a i l e d t o s t o p i t . T h i s i s v e r y l i k e l y t o c r e a t e a m e m o r y l e a k . S t a c k t r a c e o f t h r e a d : s u n . m i s c . U n s a f e . p a r k (N a t i v e M e t h o d) j a v a . u t i l . c o n c u r r e n t . l o c k s . L o c k S u p p o r t . p a r k N a n o s (L o c k S u p p o r t . j a v a : 215) j a v a . u t i l . c o n c u r r e n t . l o c k s . A b s t r a c t Q u e u e d S y n c h r o n i z e r$ ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
java.util.concurrent.ScheduledThreadPoolExecutor $D e l a y e d W o r k Q u e u e . t a k e (S c h e d u l e d T h r e a d P o o l E x e c u t o r . j a v a : 1093) j a v a . u t i l . c o n c u r r e n t . S c h e d u l e d T h r e a d P o o l E x e c u t o r$ 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)
2021-12-06 15:40:48.207 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [com.alibaba.nacos.naming.beat.sender] 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)

2021-12-06 15:40:48.207 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [com.alibaba.nacos.naming.failover] 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)

2021-12-06 15:40:48.208 WARN 12216 — [ main] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [com.alibaba.nacos.naming.push.receiver] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2021-12-06 15:40:48.219 INFO 12216 — [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled.
2021-12-06 15:40:48.224 ERROR 12216 — [ main] o.s.b.d.LoggingFailureAnalysisReporter :

APPLICATION FAILED TO START

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

com.alibaba.csp.ahas.sentinel.SentinelAnnotationAutoConfiguration.sentinelResourceAspect(SentinelAnnotationAutoConfiguration.java:44)

The following method did not exist:

com.alibaba.csp.sentinel.annotation.aspectj.SentinelResourceAspect.<init>(Lcom/alibaba/csp/sentinel/annotation/aspectj/SentinelAnnotationGlobalFallback;)V

The method’s class, com.alibaba.csp.sentinel.annotation.aspectj.SentinelResourceAspect, is available from the following locations:

jar:file:/G:/gradle-repository/com/alibaba/csp/sentinel-annotation-aspectj/1.5.2/sentinel-annotation-aspectj-1.5.2.jar!/com/alibaba/csp/sentinel/annotation/aspectj/SentinelResourceAspect.class
jar:file:/G:/gradle-repository/com/alibaba/csp/ahas-sentinel-client/1.10.1/ahas-sentinel-client-1.10.1.jar!/com/alibaba/csp/sentinel/annotation/aspectj/SentinelResourceAspect.class

It was loaded from the following location:

file:/G:/gradle-repository/com/alibaba/csp/sentinel-annotation-aspectj/1.5.2/sentinel-annotation-aspectj-1.5.2.jar

Action:

Correct the classpath of your application so that it contains a single, compatible version of com.alibaba.csp.sentinel.annotation.aspectj.SentinelResourceAspect

夏洛爱的不是秋雅 2021-12-06 15:48:01

源自：4-4 Spring Cloud Alibaba使用场景

602

收起

提交取消

1回答

大目 2021-12-08 11:39:03

问题的原因：

sentinel-annotation-aspectj 和 ahas-sentinel-client 这两个jar包中都存在SentinelResourceAspect这个类

参考Ahas文档：https://help.aliyun.com/document_detail/110599.htm

在新版本的Ahas中，可以直接把<artifactId>spring-cloud-starter-alibaba-sentinel</artifactId> 删除试试。

0 回复有任何疑惑可以回复我~

收起回答

提问者夏洛爱的不是秋雅 #1

谢谢老师，已解决，当初有这个删除依赖困扰是因为担心sentinel整合restTemplate问题，测试发现整合了AHAS不用再去restTemplate使用@SentinelRestTemplate整合了。

回复有任何疑惑可以回复我~ 2021-12-08 12:38:04

大目回复提问者夏洛爱的不是秋雅 #2
```
是的哈
```
回复有任何疑惑可以回复我~ 2021-12-13 16:43:08

相似问题

AHAS不生效

前端和后端怎么整合到一起

整合ahas

AHAS问题

AHAS降级之后自己fallback和block逻辑不生效

登录后可查看更多问答，登录/注册

Spring Cloud Alibaba微服务从入门到进阶

参与学习 3056 人
提交作业 193 份
解答问题 1322 个

面向未来微服务:熟练掌握Spring Cloud Alibaba

了解课程

本课精华内容

问答作业

第一次发送半消息报错，第二次以后就正常，重启也是一样，求原因？

533 4

0.9.1版本开始，Spring Cloud Alibaba要改包名了。。

2.0k 1

Spring Cloud Alibaba与Spring Cloud的联系与区别是？

2.6k 2

请问报Mybatis Invalid bound statement (not found)异常，如何解决？

1.6k 3

Sentinel Dashboard实时监控、链点链路信息为空的问题

3.6k 13

查看更多本课问答

意见反馈帮助中心 APP下载

官方微信

AHAS整合问题

正在回答回答被采纳积分+3

1回答

相似问题

请选择置顶位置

本课精华内容

第一次发送半消息报错，第二次以后就正常，重启也是一样，求原因？

0.9.1版本开始，Spring Cloud Alibaba要改包名了。。

Spring Cloud Alibaba与Spring Cloud的联系与区别是？

请问报Mybatis Invalid bound statement (not found)异常，如何解决？

Sentinel Dashboard实时监控、链点链路信息为空的问题

关于Sentinel Dashboard

关于Nacos

Spring Cloud Alibaba使用场景

熔断&降级

如何保证应用的高可用性？

热搜

最近搜索清空

AHAS整合问题

正在回答 回答被采纳积分+3

1回答

相似问题

请选择置顶位置

本课精华内容

第一次发送半消息报错，第二次以后就正常，重启也是一样，求原因？

0.9.1版本开始，Spring Cloud Alibaba要改包名了。。

Spring Cloud Alibaba与Spring Cloud的联系与区别是？

请问报Mybatis Invalid bound statement (not found)异常，如何解决？

Sentinel Dashboard实时监控、链点链路信息为空的问题

关于Sentinel Dashboard

关于Nacos

Spring Cloud Alibaba使用场景

熔断&降级

如何保证应用的高可用性？

正在回答回答被采纳积分+3