06-23-2011
You haven't put an print statements in for recv() so we don't know how many bytes it received, if any.
Hmm... Perhaps you're off by one communication? As in, there's data sitting in the buffer that wasn't read last time? There's no guarantee you're going to get it all in one recv(), after all, you have to know how much is coming (or use a delimiter) to know when to stop.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower.
What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
3. UNIX for Advanced & Expert Users
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies
4. Shell Programming and Scripting
Hello,
I am trying to write a script in Perl which will send some data from a UNIX Box to a windows box. I am planning to create a TCP/IP communication port for the same. How do I go about this? Kindly help.
Regards,
Garric (50 Replies)
Discussion started by: garric
50 Replies
5. Programming
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies
6. Solaris
Hello,
Actually there are some bugs in application which does not close the TCP connection to other server though CORBA.
We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED
Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies
7. UNIX for Dummies Questions & Answers
Dear experts,
I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers.
How can I pin point what connection failed and what are the ports involved?
Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"?
... (2 Replies)
Discussion started by: cache51
2 Replies
8. IP Networking
Why this happens?
How to solve this?
$netstat -na |grep 9325
tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED
When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds.
... (1 Reply)
Discussion started by: johnbach
1 Replies
9. Solaris
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies
10. UNIX for Dummies Questions & Answers
I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
LEARN ABOUT ULTRIX
recvmsg
recv(2) System Calls Manual recv(2)
Name
recv, recvfrom, recvmsg - receive a message from a socket
Syntax
#include <sys/types.h>
#include <sys/socket.h>
cc = recv(s, buf, len, flags)
int cc, s;
char *buf;
int len, flags;
cc = recvfrom(s, buf, len, flags, from, fromlen)
int cc, s;
char *buf;
int len, flags;
struct sockaddr *from;
int *fromlen;
cc = recvmsg(s, msg, flags)
int cc, s;
struct msghdr msg[];
int flags;
Description
The and system calls are used to receive messages from a socket.
The call can be used only on a connected socket. The and calls can be used to receive data on a socket, whether or not it is in a connected
state. For further information, see
If from is nonzero, the source address of the message is filled in. The fromlen is a value-result parameter, initialized to the size of
the buffer associated with from, and modified on return to indicate the actual size of the address stored there. The length of the message
is returned in If a message is too long to fit in the supplied buffer, excess bytes can be discarded, depending on the type of socket the
message is received from. For further information, see
If no messages are available at the socket, the receive call waits for a message to arrive, unless the socket is nonblocking. If the
socket is nonblocking, a of -1 is returned, and the external variable errno is set to EWOULDBLOCK. For further information, see
The call can be used to determine when more data arrives.
The flags argument to a send call is formed by ORing one or more of the values following values:
#define MSG_OOB 0x1 /* process out-of-band data */
#define MSG_PEEK 0x2 /* peek at incoming message */
The call uses a msghdr structure to minimize the number of directly supplied parameters. This structure has the following form, as defined
in <sys/socket.h>:
struct msghdr {
caddr_t msg_name; /* optional address */
int msg_namelen; /* size of address */
struct iov *msg_iov; /* scatter/gather array */
int msg_iovlen; /* # elements in msg_iov */
caddr_t msg_accrights; /* access rights sent/received */
int msg_accrightslen;
};
Here, msg_name and msg_namelen specify the destination address if the socket is unconnected; msg_name can be given as a null pointer if no
names are desired or required. The msg_iov and msg_iovlen describe the scatter gather locations, as described in Access rights to be sent
along with the message are specified in msg_accrights , which has length msg_accrightslen .
Return Values
These calls return the number of bytes received, or -1 if an error occurred.
Diagnostics
The call fails under the following conditions:
[EBADF] The argument s is an invalid descriptor.
[EINVAL] The argument length of the message is less than 0.
[EMSGSIZE] The message sent on the socket was larger than the internal message buffer.
[ENOTCONN] A call was made to from an unconnected stream socket.
[ENOTSOCK] The argument s is not a socket.
[EWOULDBLOCK] The socket is marked nonblocking and the receive operation would block.
[EINTR] The receive was interrupted by delivery of a signal before any data was available for the receive.
[EFAULT] The data was specified to be received into a nonexistent or protected part of the process address space. The argument
fromlen points outside the process address space.
See Also
read(2), send(2), socket(2)
recv(2)