Yeah, I'm helping you because I have been in your shoes where legacy code
cannot be just deleted, I'll guess you are the new guy that can't change
things drastically...
The problem you are facing is complex and simple at the same time, you have
Tomcat as container and Spring as DI so
I am using spray client i.e. akka within a Tomcat webApp.
While I do properly destroy the actor system on tomcat shutdown via spring,
i'm nevertheless still facing this threading issue.
I found that this issue was already reported few years ago Tomcat
complaints when re-deploying servlet
I'm going to guess you don't find solutions because this is about the point of
discovery that most people dump these mixed environments. Probably not what you
want to hear, but not saying anything is just as bad.
It's death by a thousand cuts. It all works in the large, but the cost of these
