FULL PRODUCT VERSION :
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
A DESCRIPTION OF THE PROBLEM :
Regarding bugs 5092063 and 6215885.
In 5092063, you suggest to set the default ProxySelector to null to avoid the problem with the slow socket connection. Fine. But, if we set the default ProxySelector to null, then we see what's reported on 6215885, a NPE on URLConnection.openConnection. And what's ironic here is that the solution for this (6215885) is "dont't set the ProxySelector to null". But then we're back to 5092063.....
Both of these bugs appear as "closed", but they are still alive even in the latest versions of the VM.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please see bugs 5092063 and 6215885.
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
A DESCRIPTION OF THE PROBLEM :
Regarding bugs 5092063 and 6215885.
In 5092063, you suggest to set the default ProxySelector to null to avoid the problem with the slow socket connection. Fine. But, if we set the default ProxySelector to null, then we see what's reported on 6215885, a NPE on URLConnection.openConnection. And what's ironic here is that the solution for this (6215885) is "dont't set the ProxySelector to null". But then we're back to 5092063.....
Both of these bugs appear as "closed", but they are still alive even in the latest versions of the VM.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please see bugs 5092063 and 6215885.
REPRODUCIBILITY :
This bug can be reproduced always.
- duplicates
-
JDK-6215885 URLConnection.openConnection NPE if ProxySelector.setDefault is set to null
-
- Resolved
-