We had this problem and got around it by seting up this series within the loop
0053: RESULT=protocolLogging("","ON",10)
----:
0067:
RESULT=initServerSocket(SERVER.IP.ADDRESS,SOCKET.PORT,BACKLOG,SOCKETHANDLE2)
----:
0070: RESULT=getSocketInformation(SOCKETHANDLE2,SERFLAG,SOCKETINFO)
----:
0083:
RESULT=acceptConnection(SOCKETHANDLE2,MODE,TIMEOUT,INADDR,INNAME,SOCKETHANDLE3)
----:
0096:
RESULT=readSocket(SOCKETHANDLE3,CLDATA,CDATLEN,TIMEOUT,MODE,ACTSIZ)
----:
0130:
RESULT=writeSocket(SOCKETHANDLE3,SRDATA,WRITETIMEOUT,MODE,SDATLEN)
----:
0156: RESULT=closeSocket(SOCKETHANDLE2)
Works great and handles thousands of transactions a day
Bob
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David Wolverton
Sent: 03 April 2006 05:25
To: 'u2 users group'
Subject: RE: [U2] Socket Error Question...
Building on my last question...
It appears that if I close the acceptor and open a new acceptor after each
SocketRead it all works well - it just seems like this is not how it should
work -- or is it?
DW
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Wolverton
Sent: Sunday, April 02, 2006 10:00 PM
To: 'u2 users group'
Subject: [U2] Socket Error Question...
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
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
