Re: Echoing

["Phil Wang" <pywang@nortelnetworks.com>]

Christos,

I check with the old code and compare it with your modification. It's
likely your modification is wrong. Why do you need to bind to the socket
with local port 7? Usually user-end applications are not allowed to bind
a port number less than 1024.

Try to restore the old code and make a test.

Phil
> 
> Phil,
> 
> I received your email about ANTS and that is why I switched to JDK 1.1.7. Concerning the echo examples, I "made" under JDK 1.1.7, which is the same -I suppose- as making a javac at each file respectively, and it still does not work.
> 
> Regards
> Christos
> 
> Phil Wang wrote:
> 
> > Did you get my last email regarding the ANTS?
> >
> > Your this problem is caused by the same reason that the JDK versions are
> > different for ORE and your modified example. There is actually some
> > incompatibility beteen JDK 1.1.7 and 1.2.2. To solve it, try to
> > recompile your example using JDK 1.1.7.
> >
> > Phil
> >
> > christos Tsarouchis wrote:
> > >
> > > Hello Phil,
> > >
> > > While awaiting for your ANTS reply, I tried something else. I directly connected 2 PCs running Red Hat Linux 6.2, and tried to use your echo paradigm.(I switched to JDK 1.1.7) Results: A PC can only echo itself, and that with a slight code modification: In EchoImpl.java L80:
> > > final DatagramSocket socket = new DatagramSocket(7);
> > >
> > > When I tried to echo the other PC however, a java.io.IOException was thrown alongside with the messages: Connection refused and Received packet null.
> > > With JDK 1.2.2 this exception becomes a socket exception and the socket closes.
> > > Both PCs were running the echo and echocli oplets.  The server seems to capture the packet(LED is on) but the client's socket becomes instantly closed.
> > > What do you think?
> > >
> > > Many thanks
> > > Christos