On Jul 21, 2007, at 10:41 AM, Mark Webb wrote:
This is a difficult problem and I wish I had a good suggestion.
The best I
can give you is to profile your application and pass along
information you
find so that we can help you.
I second this.
Enable http://blogs.sun.com/alanb/entry/
heapd
This is a difficult problem and I wish I had a good suggestion. The best I
can give you is to profile your application and pass along information you
find so that we can help you.
On 7/21/07, Raman Gupta <[EMAIL PROTECTED]> wrote:
Trustin Lee wrote:
> On 7/21/07, mat <[EMAIL PROTECTED]> wrote
Trustin Lee wrote:
> On 7/21/07, mat <[EMAIL PROTECTED]> wrote:
>> 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 th
I have not experienced this OOM problem, but if you could provide a running
sample program that reproduces the problem, we would be able to help you out
better.
Thanks.
On 7/21/07, mat <[EMAIL PROTECTED]> wrote:
On 7/21/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
>
> On 7/21/07, mat <[EMAIL PR
On 7/21/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 7/21/07, mat <[EMAIL PROTECTED]> wrote:
> 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 tha
On 7/21/07, mat <[EMAIL PROTECTED]> wrote:
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
DirectByteBuffe
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
I already used heap buffers and disable direct buffers.
ByteBuffer.setUseDirectBuffers(false); // Direct buffers perform bad.
ByteBuffer.setAllocator(new SimpleByteBufferAllocator()); // Disables
pooling.
On 7/21/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 7/21/07, mat <[EMAIL PROTECTED]>
Normally the OOM happens randomly. However it happens more often recently. I
will deploy 2 servers with 1.5 and 1.6. See what will happen. Thanks.
On 7/21/07, 向秦贤 <[EMAIL PROTECTED]> wrote:
No, I dont think it is a bug of vm.
Running in jdk6, just try to expect jdk6 maybe smart enough to handle
