I am having a blocking socket server that close immediately after receiving a second 'read' request.
Why would that be happening? Here is the Protocol Log -- after the first read and the correct 56 characters show, I inserted a GetSocketInfo and it looks good. But on the 2nd read, I get back an error "14" - Socket Closed. 04/02/2006 20:45:02 [ 5948 6052 ] readSocket ... socket=localhost,max=0,timeout=50000,mode=0 04/02/2006 20:45:07 [ 5948 6052 ] Socket dc788: 56 chars read 04/02/2006 20:45:07 [ 5948 6052 ] getSocketInformation ... socket=localhost 04/02/2006 20:45:08 [ 5948 6052 ] readSocket ... socket=localhost,max=0,timeout=50000,mode=0 04/02/2006 20:45:08 [ 5948 6052 ] Socket dc788 closed: 0(No error) 0(No error) 04/02/2006 20:45:08 [ 5948 6052 ] readSocket 2: The socket has been shut down. I would have thought that since the socket was defined as blocking, it should just sit and wait for the next data set to roll in... Is there something I am missing? David Wolverton ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
