classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ServerSocket.getLocalPort possible bug...


From: Martin Cordova
Subject: ServerSocket.getLocalPort possible bug...
Date: Wed, 21 Sep 2005 13:20:02 -0400

Hello:

While testing Winstone servlet engine (winstone.sourceforge.net) on
JamVM 1.3.3 with Classpath 0.18, I found a possible bug:

getLocalPort returns -1 when it should return 80. In fact the same
program on the same box, when running with Sun or IBM JVM works fine.
So I suspect it may be a problem in ServerSocket implementation.

Winstone's author explained to me the following:

"I know what this is - it's because socket.getLocalPort() returns -1. I
hit this when I was trying to run winstone on GCJ too, about 12 months
ago, but didn't report it. The listener code does:

       req.setServerPort(socket.getLocalPort());
"

I observed this bug when navigating to http://mylinuxBox from a remote
windows box using IE6, IE complained about no response. I found in the
servlet logs the following:

Headers prepared for writing: [Location: http://192.168.1.1:-1/index.htm

Which means that a redirect from root context to the welcome page was
being sent to the browser, but the "-1" port troubled IE6.

Hope it helps.

Regards,
Martin
--
Dinamica - Open source J2EE framework
Free, easy and powerful
http://www.martincordova.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]