On Sep 28, 7:30 am, Nigel Wade <n...@ion.le.ac.uk> wrote:
ILPTAB wrote:
Update:
Well I finally got around to trying Nigel's suggestion of calling the
flush() method after the ObjectOutputStream is opened. Unfortunately
this did not resolve the problem.
Can anybody think of a reason why this problem would occur on some
computers and not on others? I know that Roedy suggested that there
may be an issue with the version of a class that has been cached into
the windows browser but the code I posted above was compiled and
published to our web server exactly one time. How could there be a
version conflict with that? That being said I will start adding the
version info to code just in case.
I just find it so darn perplexing that the site works for some people
and not for others.
Is there anything in common with the clients which fail? Windows patch level,
JRE version, browser etc. I'd go with Roedy's suggestion and use Wireshark to
look at the packets on the wire to see what's being sent between the applet
the server.
Could this be a FIREWALL issue?
I doubt it, unless it's a badly broken firewall. I don't see how a properly
functioning firewall could result in that scenario.
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : n...@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555- Hide quoted text -
- Show quoted text -
I have been trying to find that commonality but have not been able to
put my finger on it yet. Here is something that we did find however"
After conferring with a technician in the field, we have some
additional information that we think may help resolve this issue.
Apparently there is a message line in the Java console that reads
"Network: Connecting socket://www.ptab.illinois.gov:554 with
proxy=DIRECT." This is significant because it indicates that the
Servlet and or applet is forcing a direct connection and is trying to
circumvent their firewall. The technician tells me that this is why
the applet is hanging and he believes that it's occurring as a result
of the way the java application is coded. Unfortunately, I do not
know how to code this so that it doesn't try to do a direct connect
instead of going through the proxy. Do you have any idea why this is
occuring? You can refer to the code I provided above to see how I am
setting up the socket connection on both sides.
Thank you.
Sorry, no idea. Proxy configuration is not something I know anything about. You
required.