Oh, I see. Thanks for your advice.
On Mon, Jun 9, 2008 at 5:45 PM, Quintin Beukes <[EMAIL PROTECTED]> wrote:
> Even if there is such a problem, the JVM should never crash. The JVM
> crashing means tomcat did something the triggered a bug in the JVM.
> Even overwritting/reading on buffers should be
Even if there is such a problem, the JVM should never crash. The JVM
crashing means tomcat did something the triggered a bug in the JVM.
Even overwritting/reading on buffers should be safe, since the JVM
should catch it and throw an exception.
On Mon, Jun 9, 2008 at 9:43 AM, Edward J. Yoon <[EMAIL
Ooops, sorry for my mistakes.
I use the jdk1.5.0_06, And it seems really JVM bug. :)
Thanks.
On Mon, Jun 9, 2008 at 4:48 PM, Edward J. Yoon <[EMAIL PROTECTED]> wrote:
>> Are you running a beta JVM -> 1.5.0_06-b05?
>
> Oh, Java version is a 1.4.2.
>
> Thanks, Edward
>
> On Mon, Jun 9, 2008 at 4:43
> Are you running a beta JVM -> 1.5.0_06-b05?
Oh, Java version is a 1.4.2.
Thanks, Edward
On Mon, Jun 9, 2008 at 4:43 PM, Edward J. Yoon <[EMAIL PROTECTED]> wrote:
> Thank you very much for your nice advice.
> Then, Is there no related with the reduction of tomcat number?
>
> Thanks,
> Edward.
>
Thank you very much for your nice advice.
Then, Is there no related with the reduction of tomcat number?
Thanks,
Edward.
On Mon, Jun 9, 2008 at 4:31 PM, Quintin Beukes <[EMAIL PROTECTED]> wrote:
> Ouch. Rub it, will let the pain go away quicker.
>
> It's copying a too large byte string into a too
Ouch. Rub it, will let the pain go away quicker.
It's copying a too large byte string into a too small buffer.
> # C [libc.so.6+0x68de6] strcpy+0x26
This is definitely a JVM bug. Are you running a beta JVM ->
1.5.0_06-b05? I might be mistaken, but I've never noticed the b at the
b05 at the end
