as usual with OOME, you can fix it by giving the jvm a larger max heap. in this case, you can also mitigate it by reducing the per-thread stack to the minimum with -Xss. I believe that in 1.6 the minimum is 64k on 32bit jvm and 2x that for 64bit.
-Jonathan On Mon, Feb 1, 2010 at 9:56 AM, JKnight JKnight <beukni...@gmail.com> wrote: > Dear all, > > When working with large amount of user, we have an error: > > ERROR [main] 2010-02-01 17:12:37,354 CassandraDaemon.java (line 71) Fatal > exception in thread Thread[main,5,main] > > java.lang.OutOfMemoryError: unable to create new native thread > > at java.lang.Thread.start0(Native Method) > > at java.lang.Thread.start(Thread.java:597) > > at > java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(ThreadPoolExecutor.java:727) > > at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:657) > > at > org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:186) > > at > org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:143) > > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:180) > > I see a lot of CLOSE_WAIT TCP connection. > And when I use Java Monitor and Management Console, I see the thread > increase very fast. > > Could you help me? > Thank a lot for support. > > -- > Best regards, > JKnight >
