30 tcp connections Established for a while and after a few minutes are close Post: 303030264

10 More Discussions You Might Find Interesting

1. Programming

C Prog to close a socket in established state

I have a SUN environment running an WebLogic that communicates w/a 3rd party running IIS. When the IIS site goes down (frequently), I am stuck with sockets in an ESTABLISHED state, and cannot seem to figure out how to avoid this. No exceptions are thrown as I can still open connections to the IIS...

2. UNIX for Dummies Questions & Answers

close tcp port

Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client...

3. Programming

close existing tcp connection in C

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...

4. Red Hat

How to kill all active tcp connections from an IP?

How to kill all active tcp connections from an IP? I am using CentOS

5. Solaris

How to kill the TCP ESTABLISHED connection in netstat

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...

6. Solaris

Established connections causing lag?

I'm not to sure how to go about this questions, so I will just ask it and then get criticized. How many Established connections should a V440 be able to support?

7. Programming

TCP trashing data on application close

I am using c to send data to a socket with the following commands: socket = socket(AF_INET, SOCK_STREAM, ptrp->p_proto); ioctl(socket, FIONBIO, (char *)&on); connect(socket) send(socket,data) shutdown(socket, SHUT_WR); recv(socket) //ready last of data waiting on the port //note this is...

8. IP Networking

How to test max number of tcp connections

Hello, I wanna test max tcp connection value. Please suggest how to do that. Thanks.

9. Solaris

many tcp connection in close-wait

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 ...

10. IP Networking

Need to know reason for connections closed in netstat -p tcp

Hello netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server? 1366888371 data packet headers correctly predicted 1195906 connection requests 5227320 connection accepts 5992919...

LEARN ABOUT DEBIAN

nnsd

nnsd(3tcl)																nnsd(3tcl)

__________________________________________________________________________________________________________________________________________________

NAME

       nnsd - Name service facility, Commandline Server Application

SYNOPSIS

       nnsd ?-localonly flag? ?-port port?

_________________________________________________________________

DESCRIPTION

       Please read Name service facility, introduction first.

       The  application described by this document, nns, is a simple command line server for the nano name service facility provided by the Tcllib
       packages nameserv, and nameserv::server.  Beyond that the application's sources also serve as an example of how to use the  server  package
       nameserv::server.

       This name service facility has nothing to do with the Internet's Domain Name System, otherwise known as DNS. If the reader is looking for a
       package dealing with that please see either of the packages dns and resolv, both found in Tcllib too.

   USE CASES
       nnsd was written with the following main use case in mind.

       [1]    Run a nano name service on some host.

   COMMAND LINE
       nnsd ?-localonly flag? ?-port port?
	      The command configures a server per the specified options and starts it. The command will not exit on its, as it keeps the name ser-
	      vice database wholly in memory. The user has to kill it explicitly, eithre by sending a a signal, or through the job-control facili-
	      ties of the shell in use.

	      The options to configure the name service are explained in section OPTIONS.

   OPTIONS
       This section describes all the options available to the user of the application

       -localonly bool
	      If this option is not specified it defaults to true, i.e.  acceptance of only local connections. The server will accept remote  con-
	      nections, i.e. connections from other hosts, if and only if this option is configured to false.

       -port number
	      If this option is not specified it defaults to 38573. It specifies the TCP port the server has to listen on for requests.

BUGS, IDEAS, FEEDBACK
       This  document,	and  the  application  it describes, will undoubtedly contain bugs and other problems.	Please report such in the category
       nameserv of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883].  Please also report any ideas for enhancements you may
       have for either application and/or documentation.

SEE ALSO

       nameserv::common(3tcl), nameserv::server(3tcl)

KEYWORDS

       application, name service, server

CATEGORY

       Networking

COPYRIGHT

       Copyright (c) 2007-2008 Andreas Kupries <andreas_kupries@users.sourceforge.net>

Name service facility						       1.0.1								nnsd(3tcl)