Replies: 4 comments 4 replies
-
It doesn't seem so. More likely you have spring devtool or similar things to duplicate change codes, to trigger skywalking kernel conflicts. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Okay, thank you for the author's reply. May I ask if removing the hot deployment in devtools can solve the problem |
Beta Was this translation helpful? Give feedback.
2 replies
-
Still the same error, probably due to what the author said and other similar things like copying and changing code |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After Java joined Skywalking, the agent reported an error:main SkyWalkingAgent : Enhance class org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor error,Then the connected application reported an error:[main] [empty#0 on NoUser] ERROR org.springframework.boot.SpringApplication:821 - Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.annotation.internalConfigurationAnnotationProcessor': Instantiation of bean failed; nested exception is java.lang.ClassFormatError: Duplicate field name "cachedValue 𝑠 𝑤 swho7p9v2$7stfck1" with signature "Ljava.lang.reflect.Method;" in class file org/springframework/beans/BeanWrapperImpl。
The possible issue is that when the SkyWalking Agent attempts to enhance the BeanWrapperImpl class, the additional field names it generates overlap with the existing field names within the class, resulting in ClassFormatError. This is usually caused by the incompatibility between SkyWalking's dynamic bytecode injection mechanism and certain internal details of the Spring framework.
Beta Was this translation helpful? Give feedback.
All reactions