Closed GoogleCodeExporter closed 9 years ago
That's how threads work in java. The MemcachedClient IO thread is not a daemon
thread by default. You can make it one if you like, but you risk data loss if
you exit without shutting down and what-not.
It sounds like you have a few workarounds. I don't think it's unreasonable to
ensure that the client has properly finished its work before exiting the VM
altogether.
Original comment by dsalli...@gmail.com
on 20 Mar 2011 at 7:54
After fiddling with it a lot more you are right, although i had to add a
shutdown delay because I was getting shutdown while trying to write error.
I will say that the 2.5.x client we put into production and what was working
fine for months...all of a sudden we were getting tcp/ip port leaks. Everytime
the cache was created, even though the client we created was a singleton with a
single connection...it always created a new connection. We upgraded to 2.6 and
it works great with no connection leaks.
Original comment by benjamin...@gmail.com
on 20 Mar 2011 at 11:55
Original issue reported on code.google.com by
benjamin...@gmail.com
on 16 Mar 2011 at 5:33