Smack create too much threads with newCachedThreadPool

Smack Smack Support
22

2024-10-29 17:49:51,397 [ DialogHandler.java:Smack Cached Executor:605] - thread stopped successfully…
2024-10-29 17:49:51,397 [ DialogHandler.java:Smack Cached Executor:605] - thread stopped successfully…
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:607] - 7419000000010000000004DB5950600A>> Pulse Thread Stopped
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:607] - 7419000000010000000004DB5950600A>> Pulse Thread Stopped
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:608] - 7419000000010000000004DB5950600A>> Clearing the MAPs…
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:608] - 7419000000010000000004DB5950600A>> Clearing the MAPs…
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:622] - 7419000000010000000004DB5950600A>> MAPs are cleared.
2024-10-29 17:49:51,398 [ DialogHandler.java:Smack Cached Executor:622] - 7419000000010000000004DB5950600A>> MAPs are cleared.

23

smack cached Executor executing twice in above logs

24

can any one assist for above issue

25

Like @Flow suggested, getting full stack traces for all running threads would be a good thing to have, to base any diagnostics on. You have provided a list of thread names, but not the stack traces for each thread. There are a couple of ways of getting thread dumps. I suggest that you use Google to find something that works best for you.