We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
we used TracedExecutorService occur oom when service run long time with high throughput code :
jvm dump analyze :
The text was updated successfully, but these errors were encountered:
Both in TracedCallable and TracedRunnable any scope that gets activated is closed again after the operation.
Could it be that there are places where scopes are not closed properly? Which scope manager do you use?
Sorry, something went wrong.
we used this scopManager: https://github.com/PacktPublishing/Mastering-Distributed-Tracing/blob/master/Chapter11/exercise1/lib/src/main/java/lib/MDCScopeManager.java
we use TracedExecutorService code is : @async("asyncThreadExecutor") public void sendSms(List list) { if (list.isEmpty()) { log.warn("empty list..."); } else { for(String str : list) { try { String response; response = restTemplate.getForObject("http://localhost:8080/test", String.class); log.info("execute call success....{}, {}", str, response); } catch (Exception ex) { ex.printStackTrace(); } } } }
it can reappear oom when execute sendSms many times 。
No branches or pull requests
we used TracedExecutorService occur oom when service run long time with high throughput
code :
jvm dump analyze :
The text was updated successfully, but these errors were encountered: