The fourth column is the "Local Address" (local machine) - in the case, a machine-name (vs IP address) and the port value (such as 51186) the machine is listening on. Of course, the machine-name will resolve to an IP address, so in some netstat output, you might see tcp 0 0 10.240.100.20:51186 10.240.100.55:1526 ESTABLISHED - or possibly - tcp 0 0 0.0.0.0:51186 10.240.100.55:1526 ESTABLISHED - or possibly - tcp 0 0 127.0.0.1:51186 10.240.100.55:1526 ESTABLISHED
This Local Address is the address to which the socket in question is bound to and which it receives connections on. The fifth column is the "Foreign Address" (destination machine), sometimes shown with its port# (as is the case here) and a connection is established. On Tue, Jan 10, 2017 at 5:06 PM, Joleen Barker <oldenuf2no...@gmail.com> wrote: > Hi Andre - I played around a little more and ran the command netstat -a | > grep 1526 which is the port number and received information that looks like > 11 connections are open at this time. Do you know what the number is that > follows the machine name in the forth column for example the 51186? > > netstat -a | grep 1526 > > tcp 0 0 cpmfttapt21.51186 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.51198 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.51211 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.55213 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.55214 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.55215 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.57493 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.57495 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.35153 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.35154 cpmfttdbt01-vip..1526 > ESTABLISHED > > tcp 0 0 cpmfttapt21.35157 cpmfttdbt01-vip..1526 > ESTABLISHED > > On Tue, Jan 10, 2017 at 11:59 AM, Joleen Barker <oldenuf2no...@gmail.com> > wrote: > > > Hello Filippo - I do not have JConsole available and the proposed idea is > > past my knowledge level. > > > > Hello André - This was an interesting idea but it didn't work for me. I > > only have the ksh available and could only use netstat -p tcp but the > > output didn't make sense to me. > > > > On Tue, Jan 10, 2017 at 11:24 AM, André Warnier (tomcat) <a...@ice-sa.com> > > wrote: > > > >> On 10.01.2017 17:10, Joleen Barker wrote: > >> > >>> Hello All, > >>> > >>> Details: > >>> Tomcat Version: 7.0.64.0 > >>> Java Version: 1.8.0 > >>> OS: AIX 6.1 > >>> Database: Oracle 11 > >>> > >>> The web application installed on the server above makes data > connections > >>> to > >>> run file transfers from point A to point B. The default Database > >>> connection > >>> setting that are set when the application server comes up are as > follows: > >>> > >>> DataBasePoolingFlag - APACHE > >>> MaxActive - 400 > >>> MaxIdle - 20 > >>> MinIdle - 10 > >>> > >>> We had an incident where all these connections were actually used up > due > >>> to > >>> a script someone had that looped. I need to determine at any given > point > >>> in > >>> time how many DB connections exist from the web application to the DB. > >>> There may be more than one way to do this. I am sure there is a DB > >>> command > >>> that could be run against the schema but the schema is pointed to by > many > >>> servers. I am wondering if there is a java command of some kind that I > >>> could run that may tell me how many connections are open at that time > or > >>> possibly a tomcat or apache command. > >>> > >>> Thank you for the help in advance. > >>> > >>> > >> Hi. > >> Maybe an "out of the box" answer, not using java. > >> I don't know how the following commands fare under AIX, but on a Linux > >> system, the OS-level command : > >> ~# netstat -pan --tcp | grep ESTABLISHED > >> will show you pretty much all TCP connections that are established > >> between any process and any other, local or remote. > >> > >> Sample output : > >> > >> tcp6 0 0 127.0.0.1:45095 127.0.0.1:11002 > >> ESTABLISHED 11096/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53564 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53677 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53659 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53656 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53620 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:8009 127.0.0.1:53608 > >> ESTABLISHED 2677/java > >> tcp6 0 0 127.0.0.1:45142 127.0.0.1:11002 > >> ESTABLISHED 11096/java > >> tcp6 0 0 127.0.0.1:43558 127.0.0.1:11002 > >> ESTABLISHED 11096/java > >> tcp6 0 0 127.0.0.1:45128 127.0.0.1:11002 > >> ESTABLISHED 11096/java > >> tcp6 0 0 127.0.0.1:45069 127.0.0.1:11002 > >> ESTABLISHED 11096/java > >> > >> I presume that you could easily find out the process-id of your Tomcat, > >> and the port number under which the database is accessed. > >> It would be a simple matter to "grep" the above and count the lines, to > >> get the answer you seem to want. > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > >
