After using SkyWalking for my Java service, I encountered a memory leak issue with the SkyWalking context.Please help me. #13520
-
|
The version of the SkyWalking agent we are using is 9.4.0. After analyzing the memory dump of the service, we found that the ThreadLocal of the Tomcat threads contains a large number of non-recyclable org.apache.skywalking.apm.agent.core.context.trace.NoopSpan objects. Please help us identify the root cause of this issue. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
This is something trace spans not finished properly. Could be some plugin bugs. You should have seen errors in agent logs, and would not receive relative traces. |
Beta Was this translation helpful? Give feedback.
-
|
You are right. There are some tomcat errors in agent logs. How can we solve it? |
Beta Was this translation helpful? Give feedback.
-
|
We have identified the issue: it is caused by incompatibility with the tomcat-7.x-8.x plugin in the agent. We attempted to exclude the plugin using the parameter Dskywalking.plugin.exclude_plugins=tomcat-7.x/8.x, but it did not take effect. Why might this be happening? |
Beta Was this translation helpful? Give feedback.
-
|
Can't see your screenshots. They are not uploaded. After exclusion, you should be able to see this plugin doesn't exist in your agent booting logs. |
Beta Was this translation helpful? Give feedback.
-
|
This plugin still exists in my agent booting logs. I suspect whether the plugin name I configured, tomcat-7.x/8.x, is correct. |
Beta Was this translation helpful? Give feedback.
-
|
If you don't want to debug(which I recommend), you could remove that plugin jar from plugins folder. |
Beta Was this translation helpful? Give feedback.
-
|
We have solved the issue. Thank you. |
Beta Was this translation helpful? Give feedback.
This is something trace spans not finished properly. Could be some plugin bugs. You should have seen errors in agent logs, and would not receive relative traces.