I
Imran
Hi All,
Thanks in advance for your help. I am curious if anyone has ever
encountered a situation where a receive call on a UDP client socket
waits for ever, despite having a soTimeout of 3 seconds.
The application contains many sender threads which each create a
socket, send a request and wait for a response. Mostly these threads
send and receive as expected, but over time they wait indefinitely on
DatagramSocket.receive for a response, eventually exhausting the entire
thread pool.
Sending a random packet to the client port of these blocking sockets
wakes them up and they continue to process as expected.
Just curious if anybody has encountered this behavior in their
applications!
Thx,
Imran
Thanks in advance for your help. I am curious if anyone has ever
encountered a situation where a receive call on a UDP client socket
waits for ever, despite having a soTimeout of 3 seconds.
The application contains many sender threads which each create a
socket, send a request and wait for a response. Mostly these threads
send and receive as expected, but over time they wait indefinitely on
DatagramSocket.receive for a response, eventually exhausting the entire
thread pool.
Sending a random packet to the client port of these blocking sockets
wakes them up and they continue to process as expected.
Just curious if anybody has encountered this behavior in their
applications!
Thx,
Imran