06-24-2011
Yes! That's it. The problem was that there appeared SIGPIPE during second communicate() invocation. It was killing the program (SIGPIPE default action is to terminate process).
But there is still one strange thing. On the client side, during server breakdown, first send_request does not return any error, only the second one (I have checked, it get SIGPIPE, so I can handle it properly). Why? What is about this first execution that it does not fail? Neither send nor recv get SIGPIPE.
Last edited by Shang; 06-24-2011 at 12:31 PM..
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 NETBSD
sendmsg
SEND(2) BSD System Calls Manual SEND(2)
NAME
send, sendto, sendmsg -- send a message from a socket
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/socket.h>
ssize_t
send(int s, const void *msg, size_t len, int flags);
ssize_t
sendto(int s, const void *msg, size_t len, int flags, const struct sockaddr *to, socklen_t tolen);
ssize_t
sendmsg(int s, const struct msghdr *msg, int flags);
DESCRIPTION
send(), sendto(), and sendmsg() are used to transmit a message to another socket. send() may be used only when the socket is in a connected
state, while sendto() and sendmsg() may be used at any time.
The address of the target is given by to with tolen specifying its size. The length of the message is given by len. If the message is too
long to pass atomically through the underlying protocol, the error EMSGSIZE is returned, and the message is not transmitted.
No indication of failure to deliver is implicit in a send(). Locally detected errors are indicated by a return value of -1.
If no messages space is available at the socket to hold the message to be transmitted, then send() normally blocks, unless the socket has
been placed in non-blocking I/O mode. The select(2) or poll(2) call may be used to determine when it is possible to send more data.
The flags parameter may include one or more of the following:
#define MSG_OOB 0x0001 /* process out-of-band data */
#define MSG_PEEK 0x0002 /* peek at incoming message */
#define MSG_DONTROUTE 0x0004 /* bypass routing, use direct interface */
#define MSG_EOR 0x0008 /* data completes record */
#define MSG_NOSIGNAL 0x0400 /* do not generate SIGPIPE on EOF */
The flag MSG_OOB is used to send ``out-of-band'' data on sockets that support this notion (e.g. SOCK_STREAM); the underlying protocol must
also support ``out-of-band'' data. MSG_EOR is used to indicate a record mark for protocols which support the concept. MSG_DONTROUTE is usu-
ally used only by diagnostic or routing programs.
See recv(2) for a description of the msghdr structure. MSG_NOSIGNAL is used to prevent SIGPIPE generation when writing a socket that may be
closed.
RETURN VALUES
The call returns the number of characters sent, or -1 if an error occurred.
ERRORS
send(), sendto(), and sendmsg() fail if:
[EBADF] An invalid descriptor was specified.
[ENOTSOCK] The argument s is not a socket.
[EFAULT] An invalid user space address was specified for a parameter.
[EMSGSIZE] The socket requires that message be sent atomically, and the size of the message to be sent made this impossible.
[EPIPE] In a connected socket the connection has been broken.
[EDSTADDRREQ] In a non-connected socket a destination address has not been specified.
[EAGAIN|EWOULDBLOCK]
The socket is marked non-blocking and the requested operation would block.
[ENOBUFS] The system was unable to allocate an internal buffer. The operation may succeed when buffers become available.
[ENOBUFS] The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but
may be caused by transient congestion.
[EACCES] The SO_BROADCAST option is not set on the socket, and a broadcast address was given as the destination.
[EHOSTUNREACH] The destination for the message is unreachable.
[EHOSTDOWN] The destination is a host on the local subnet and does not respond to arp(4).
[EINVAL] The total length of the I/O is more than can be expressed by the ssize_t return value.
[EAFNOSUPPORT] Addresses in the specified address family cannot be used with this socket.
sendto() will also fail if:
[EISCONN] A destination address was specified and the socket is already connected.
sendmsg() will also fail if:
[EMSGSIZE] The msg_iovlen member of the msg structure is less than or equal to 0 or is greater than {IOV_MAX}.
SEE ALSO
fcntl(2), getsockopt(2), recv(2), select(2), socket(2), write(2)
HISTORY
The send() function call appeared in 4.2BSD.
BSD
May 9, 2008 BSD