Skip to content

thread blocked at jdk.internal.loader.URLClassPath.getLoader after use javaagent #11949

Answered by laurit
huange7 asked this question in Q&A
Discussion options

You must be logged in to vote

We could ignore com.alibaba.fastjson.util.ASMClassLoader #11954 that should resolve the issue. Though if new instances of ASMClassLoader are being created it could also very well be a bug in your application (are you creating new SerializeConfig instances?) or something completely different.

Replies: 1 comment 9 replies

Comment options

You must be logged in to vote
9 replies
@huange7
Comment options

@laurit
Comment options

@huange7
Comment options

@laurit
Comment options

Answer selected by huange7
@huange7
Comment options

@huange7
Comment options

@laurit
Comment options

@huange7
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants