At least on Windows this particular error is quite unique. Oddly, increasing the maximum heap value *makes it worse.* The key is the "native" part of the message -- it's running out of main OS memory that's getting allocated outside of the JVM.
The overall issue is allocating too many threads. I'm guessing you're using a cached thread pool. If you decrease the MX value, you'll be able to create more threads, but you'll still almost certainly hit the same issue eventually. -Adam On Tue, Feb 2, 2010 at 3:06 AM, JKnight JKnight <beukni...@gmail.com> wrote: > Thank you very much, Mr Jonathan. > > On Mon, Feb 1, 2010 at 11:04 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> >> On Mon, Feb 1, 2010 at 10:03 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> >> I see a lot of CLOSE_WAIT TCP connection. >> >> Also, this sounds like you are not properly pooling client connections >> to casssandra. You should have one connection per user, not one >> connection per operation. >> >> -Jonathan > > > > -- > Best regards, > JKnight > -- Adam Fisk http://www.littleshoot.org | http://adamfisk.wordpress.com | http://twitter.com/adamfisk
