Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

URLConnection broken on Windows?

0 views
Skip to first unread message

Jeff Messner

unread,
Feb 12, 2001, 7:46:02 PM2/12/01
to
I have an applet that uses the URLConnection to allow it to get data if
the applet is behind a firewall. This applet works on Linux using
either Netscape 4.x or 6.x, and it works on Windows with IE.

It does not work properly with Netscape 4.x (using the Netscape Java VM)
on Windows; however, this is a longtime-known bug.

What surprised me is that it doesn't work at all under Netscape 6 using
Sun's VM! (1.3_01 or whatever it is that comes with NS6)

When you open a URLConnection, you should be able to open an
OutputStream and an InputStream on that connection. For some reason,
when I attempt to open the InputStream, it gets stuck for about a
minute, then finally times out and throws a NullPointerException
somewhere down in the implementation getInputStream().

Anyone else find this bug? I tried searching Bugzilla for it but turned
up nothing. Where should I go to file this bug?

Andy

unread,
Feb 12, 2001, 10:35:03 PM2/12/01
to
Jeff Messner wrote:
>

> When you open a URLConnection, you should be able to open an
> OutputStream and an InputStream on that connection. For some reason,
> when I attempt to open the InputStream, it gets stuck for about a
> minute, then finally times out and throws a NullPointerException
> somewhere down in the implementation getInputStream().
>
> Anyone else find this bug? I tried searching Bugzilla for it but turned
> up nothing. Where should I go to file this bug?

Might be unrelated, but if you get a 1 minute delay, then its often
something screwy in your DNS configuration, i.e. the code can't resolve
a hostname or something. Since each DNS server is tried in turn, if you
have 3 or 4 set 1 minute to time out is to unheard of.

Before you conclude that its a bug, try opening a connection to an IP
address and try to run the code on a machine on a different network,
like dialled up to an ISP or something.

That said, it might be a bug and nothing to do with DNS.

AndyT

0 new messages