Hi, Trustin I read this "The problem was the SocketChannel.write implementation. Indeed, even if you don't use DirectByteBuffer in your code, SocketChannel.writedoes it for you. This means that every time you call the write method, a new DirectByteBuffer is created. And since there is no real and effective GC on this type of objects, on heavy load, your application simply crash." However, my case seems not under heaving loading.
I guess this problem should happen to most of peoples using Mina. No?? On 7/21/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 7/21/07, mat <[EMAIL PROTECTED]> wrote: > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) > Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing) > Windows 2003 > > So you think it is bug of JVM? I'd suggest you to use heap buffers instead of direct buffers: http://mina.apache.org/faq.html#FAQ-Iget%7B%7BOutOfMemoryError%7D%7Dorresponsetimeoutandconnectionresetunderheavyload . HTH, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
