Ingo Brunberg wrote:
To work around a bug in the Java VM in this manner seems a bad idea to
me.
When making applications that work on more than one platform and more
than one JDK, working around specific implementation bugs is a very
common problem. I just remeber the drag and drop and threading
I agree that working around JVM bugs is annoying, but in most cases
there's really not much else you can do. However, it's not acceptable
to allow a runtime exception to kill code that should otherwise work.
The bug so far has only been reported with Windows (but that could be
because there's
To work around a bug in the Java VM in this manner seems a bad idea to
me. As I have never seen this myself, I guess only Windows platforms
are affected?
What are the Sun engineers saying?
Regards,
Ingo
> Hi all,
>
> Under some exceptional circumstances, reading from a SocketInputStream
> can
Hi all,
Under some exceptional circumstances, reading from a SocketInputStream
can cause an ArrayIndexOutOfBoundsException. We have seen this occur
in many other places (non HttpClient related), and since including
HttpClient a few bugs have been reported with it as well. The exact
cause
