Board index Linux

Socket.setSoTimeout() misbehaves under Linux?

Socket.setSoTimeout() misbehaves under Linux?

Post by Elda » Sat, 13 Dec 1997 04:00:00



Is it just me, or does this function fail under Linux? I've written a
small server (source available upon request, if you feel that would
help - only about 100 lines) that allows multiple clients to connect
to it. If I setSoTimeout to a non-zero value, the client gets
disconnected after the timeout, but also when the next client
connects, even though the timeout has not yet expired! So the server
is actually limited to one client at the time.

Under windows 95, or when the timeout value is set to zero, this does
not happen.

So:

1. Is this problem specific to Linux, or does it affect other unix
systems as well?

2. Is there some kind of workaround? I guess I could always use
_another_ thread for each client, but isn't there a better way?

3. Any idea about whether this problem can or will be fixed in future
versions? (I'm using JDK 1.1.3 which I believe is the latest for java.

Platform independence? Sure, once all virtual machines act in exactly
the same way. But not this millenium.

 
 
 
Top

1. Misbehaving Linux Routers

I have been facing the problem for quite some time. In my private network,
I have 4 routers. The routers have been configured properly  by
setting the IP addr of the interfaces, gateways where ever neccessary and
proper subnet mask. When I boot up the routers, I am unable to ping to
any of the routers. I am unable to ping to the default route also.

What happens next is very strange. I open the network configuration tool,
look up all the setting without modifying any entry. Click on apply and
then type the command 'service network restart'. Once the network is
restarted, if I try to ping to the any router / default router it works.

I have checked the network scripts for the interfaces and all the
neccessary interfaces have 'OnBoot=yes'. I have been checking the log
files also. Everything seems normal. I get one warning message

"xinetd: warning: cant get client address: Transport endpoint is not
connected"

The cables are all connected and are working fine as the green light is
on.

Any help/advice would be greatly appreciate,

Thanks,
Rahul.

2. Xiterm with no pixmap..

3. Sockets sockets and more sockets

4. pppd daemon keeps dying!

5. Socket, Socket, whose got the socket?

6. Moving Linux partition

7. Socket, socket, who's got the socket?

8. $SOCKS_N Environment

9. Sockets sockets and more sockets

10. Making Linux server sockets connect with Borland C++ builder Client Sockets?

11. Socket 7 (K-63) or Socket 370 (intel PPGA) for Linux?

12. MSI KT4AV Socket A (Socket 462) VIA KT400A ATX AMD Motherboard & Linux?

13. Sockets, Socket++1.10 and Linux


All times are UTC
Board index