Can you show me your test code that does this?
My tests all complete and exit fine and I do hit every exceptional
state I can think of. If I'm missing one, I'd like to get it added to
my tests to make sure it doesn't happen in a shipping version.
2.1 allows you to specify daemon state for the io thread. That can
potentially be dangerous, but less so than exit.
--
Dustin Sallings (mobile)
On May 14, 2008, at 6:21, Alexander Zaitsev <[EMAIL PROTECTED]
> wrote:
I am not shutting down the client, though I tried that as well --
does not help.
Only System.exit() helps reliably, return from main or unhandled
exception make the Java to stuck as I described.
--
Alexander Zaitsev
AMG Lab Sarl
Dustin Sallings wrote:
On May 12, 2008, at 5:52, Alexander Zaitsev wrote:
When I switched from Danga to spymemcached, the program stopped to
quite normally. The main() finishes, but Java process does not
exit. I have added explicit System.exit() call and it seemed to
help, but not always. Sometimes JVM still fails to exist and waits
on unknown condition. Below is the thread dump.
Are you shutting down the client before attempting to exit?
Perhaps a small code example would be good.
2.1 allows you to run the IO thread as a daemon thread. It's a
little dangerous as you can issue a bunch of async commands and
then kill it before it has time to process them all, but it's there.
BTW, there's a list here: http://groups.google.com/group/spymemcached
(people asked for it).
--
Dustin Sallings
