That's odd.
Not sure what we can do about that, maybe you should contact the Spring
guys (or check their code) to see why this is happening.
I took a quick look at the Spring DM code for RunnableTimedExecution and
I see that they do call Thread.stop() on a locally created thread if
some timeout, but since the thread is created by them it doesn't make
sense that we see the exception on the event delivery thread.
Further, this was for version 1.0 and is no longer the case for
1.2...which version are you using?
-> richard
On 11/18/09 13:11, Patrick Forhan wrote:
On Tue, Nov 17, 2009 at 3:46 PM, Karl Pauls<[email protected]> wrote:
Can you get us a stacktrace of that exception and a threaddump of the
framework after it happens?
I've attached the file. How it works in brief:
JMS listener receives a command to shutdown. In that thread, we send
"shutdown" to the shell service. That same thread is the one that is
killed... not sure who is calling Thread.stop(), I need to look into
that a bit. It may be Spring as it shuts down the JMS listeners,
maybe?
Pat.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
