AW: [En-Nut-Discussion] TCP Socket closed after with third TCP Request
Joachim Skale
joachim.skale at tele2.at
Mon Dec 19 10:21:25 CET 2005
i didn't want to use a workaround now.
i want to know why the socket is closed.
after the second request i can wait until the End of Days, when i call the Socket Info the Socket will be shown as ESTABLISHED.
if my source will help anyone, please call.
Joachim
-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de]Im Auftrag von Lokanath
Penukonda
Gesendet: Montag, 19. Dezember 2005 10:11
An: 'Ethernut User Chat (English)'
Betreff: RE: [En-Nut-Discussion] TCP Socket closed after with third TCP
Request
Check is any processes which have dependecy to that server...i guess u can
use shutdown() in the client with option 2..
-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de]On Behalf Of Joachim Skale
Sent: Monday, December 19, 2005 2:36 PM
To: En-Nut Discussion
Subject: [En-Nut-Discussion] TCP Socket closed after with third TCP
Request
hi all,
i've got the following problem.
I use the Ethernut Board as TCP Client which validates Cards via TCP Request
on an server.
Within the Third Request the Socket State changed from ESTABLISHED to
CLOSED.
When i debug into the Sources of the TCP, i saw that
/*
* Wait until any data arrived, a timeout occurs
* or the connection terminates.
*/
while (sock->so_rx_cnt - sock->so_rd_cnt == 0) {
if (sock->so_state != TCPS_ESTABLISHED) {
sock->so_last_error = ENOTCONN;
return -1;
}
if (NutEventWait(&sock->so_rx_tq, sock->so_read_to))
return 0;
}
in this code segment the socket state is changed to closed.
My Server didn't close the Connection.
Any hints??
Joachim
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
To report this email as spam click
https://www.mailcontrol.com/sr/PcrqosDHDxNtBuG3RKQ2piO2+LErDM3CmuU6beUpK3ouV
jTnNOjxXtsjYe+UA++t94qyr3sZ4!8JM!+FQzOrnCUZAOb4BO5xJ7CrpjZzTWKVwsvB2pZQP7BUv
SVR0DEG0cn1vhzLuQXJzRHW42lSpVBSAydT9jXObLzMluGArFZLJFfH3!5L6tAdZhgYqQdK41EOw
WEm8kzfRPbqiQJ4OrPmgUSJxQ9e .
**********************************************************************
The information contained in this email and any attachments
is likely to be confidential and legally privileged, and is for the
intended recipient named above only. Any copying,
dissemination, disclosure of or use of this email or its
attachments unless authorised by us is prohibited, except
that you may forward this email and/or attachments to a third
party on a strict "need to know" basis.
If you have received this email in error, please notify us
immediately by replying to the email or by calling
+91-80-26492700. Please then delete this email and any full
or partial copies of it.
You as the intended recipient must be aware and accept
that emailis not a totally secure communications medium.
Although we have taken all reasonable steps to make
sure this email and any attachments are free from viruses,
we do not (to the extent permitted by law) accept any liability
whatsoever for any virus infection and/or compromise of
security caused by this email and any attachment.
No contract may be formed or documents served by you
on or with us by this email or any attachments unless
expressly agreed otherwise by us.
Any views expressed in this email or attachments by
an individual are not necessarily those of UbiNetics
India (Private) Limited.
**********************************************************************
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
More information about the En-Nut-Discussion
mailing list