|
This is one application: due to constraints with how our customers use it, we cannot have multiple processes running. We have to use threads or we open ourselves up to much larger problems.
At this point if I could kill the thread it is worth a try. It may not work, but that is why we have a QA lab: to test this and document what happens under what circumstances. Unfortunately we cannot even use Thread.stop() as the inherent problem is the thread does not behave in the first place. Hopefully the hardware vendor can fix their Java driver, but that will take time, and like most vendors, they write perfect code and the problem is in the host application.
So I am back to my first question: is there some other way to kill this thread, even if I need to change how I manage its creation and use? E.g. using a different ThreadGroup or Executor? Even if I need native code to do it, there has to be a way. Maybe a third-party library that allows greater control?
|