Sponsored Content
Top Forums UNIX for Advanced & Expert Users 30 tcp connections Established for a while and after a few minutes are close Post 303030264 by Corona688 on Thursday 7th of February 2019 10:35:44 AM
Old 02-07-2019
What is 10.80.1.26 ?
What is 10.81.248.79 ?
What is port 53008 ?
What service is this?
What happens when you try connecting to the server?
 

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... (1 Reply)
Discussion started by: teledelux
1 Replies

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... (1 Reply)
Discussion started by: raidzero
1 Replies

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... (6 Replies)
Discussion started by: raidzero
6 Replies

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 (3 Replies)
Discussion started by: an00p
3 Replies

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... (4 Replies)
Discussion started by: GIC1986
4 Replies

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? (4 Replies)
Discussion started by: adelsin
4 Replies

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... (3 Replies)
Discussion started by: metrix
3 Replies

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. (2 Replies)
Discussion started by: gstoychev
2 Replies

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 ... (2 Replies)
Discussion started by: abcdef
2 Replies

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... (6 Replies)
Discussion started by: Vishal_dba
6 Replies
MONGOCLIENT.CLOSE(3)							 1						      MONGOCLIENT.CLOSE(3)

MongoClient::close - Closes this connection

SYNOPSIS
public bool MongoClient::close ([boolean|string $connection]) DESCRIPTION
The MongoClient.close(3) method forcefully closes a connection to the database, even if persistent connections are being used. You should never have to do this under normal circumstances. PARAMETERS
o $connection - If connection is not given, or FALSE then connection that would be selected for writes would be closed. In a single-node config- uration, that is then the whole connection, but if you are connected to a replica set, close() will only close the connection to the primary server. If connection is TRUE then all connections as known by the connection manager will be closed. This can include connections that are not referenced in the connection string used to create the object that you are calling close on. If connection is a string argument, then it will only close the connection identified by this hash. Hashes are identifiers for a con- nection and can be obtained by calling MongoClient.getConnections(3). RETURN VALUES
Returns if the connection was successfully closed. EXAMPLES
Example #1 MongoClient.close(3) example This example demonstrates how to selectively close all connections for secondaries only. <?php // Connect to a replicaset $a = new MongoClient("mongodb://whisky:13000/?replicaset=seta"); $connections = $a->getConnections(); foreach ( $connections as $con ) { // Loop over all the connections, and when the type is "SECONDARY" // we close the connection if ( $con['connection']['connection_type_desc'] == "SECONDARY" ) { echo "Closing '{$con['hash']}': "; $closed = $a->close( $con['hash'] ); echo $closed ? "ok" : "failed", " "; } } ?> The above example will output: Closing 'whisky:13001;X;4948': ok CHANGELOG
+--------+---------------------------------------------------+ |Version | | | | | | | Description | | | | +--------+---------------------------------------------------+ | 1.3.0 | | | | | | | The $connection parameter to this function was | | | added in 1.3.0. Before that, only the write con- | | | nection would be closed by this method. | | | | | 1.2.0 | | | | | | | Before version 1.2.0 the driver would not use | | | persistent connections by default, and all con- | | | nections would be closed as soon as a MongoDB | | | connection went out if scope. Since version 1.2.0 | | | this is no longer the case and it is a bad idea | | | to call close as you might end up overloading the | | | server with connections under high load. | | | | +--------+---------------------------------------------------+ SEE ALSO
MongoClient.getConnections(3). PHP Documentation Group MONGOCLIENT.CLOSE(3)
All times are GMT -4. The time now is 12:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy