How can I determine which ports are in use by UAPM?

Document ID : KB000025823
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

How can I determine which ports are in use by UAPM?

 

Environment: Windows

You can use the UAPM configurator and netstat to learn which ports are in use by UAPM processes.

 

Resolution:

You can use the UAPM configurator and netstat to learn which ports are in use by UAPM processes.

 

Open the Unicenter Asset Portfolio Management Configurator from the START menu

  • Select Asset Portfolio Management

  • ASP.NET State Service Port will be listed (default: 42424)

  • UAPM Cache Service Port will be listed (default: 8082)


    Figure 1

 

Interpreting Ports Using Netstat

 

Useful Task Manager Options

  • Open task manager from a command prompt: Taskmgr

  • Select the Processes tab

  • Click menu item View

  • Click Select Columns

  • Select PID (Process Identifier)

  • Select CPU Usage

  • Select Memory Usage

  • Select User Name

  • Click OK

    Figure 2

Use Task Manager to obtain these PIDs

  • ASP.NET State Service Aspnet_state.exe

  • PID from Taskmgr is 1928

  • UAPM Cache Service UAPMCacheService.exe

  • PID from Taskmgr is 2456

  • W3WP Service w3wp.exe (One per active Application Pool)

  • PID from Taskmgr is 536

  • We use the APM App Pool and the Default App Pool, but if you are not accessing APMWS (Web Services) at the time, you may not see a 2 nd W3WP process running for it, though you may see others if the IIS server has other Application Pools defined and they are currently being accessed.

Netstat options

  • /? get help

  • -a list all connections

  • -b list the executable using the connection

  • -o list the owning process of each connection

  • -p limit output to the specified protocol (TCP or UDP)

  • -v list the sequence of processes using the connection (when used with -b)

    Netstat provides a point in time snapshot of port activity.

    Use the netstat command to correlate ports.

    This is some of the output from a netstat -abv -p TCP command

    Figure 3

    Figure 4

    Figure 5
    Figure 6

    Figure 7

    Figure 8

From Taskmgr, we know that the PIDs we are interested in are:

  • 1928 asp.net state service

  • 2456 UAPM cache service

  • 536 w3wp worker process for the APM App Pool

 

Let's walk through an example. Using the output from taskmgr and netstat, we can figure out what processes the asp.net state service is talking to and what ports it is talking on. 


The asp.net state service is using PID 1928. From the netstat output above, we can see that PID 1928 has 2 connections defined. The first one says a connection was originated on port 42424. The left-hand column shows the originating port number, and it is listening for connections. It also shows that no connection has been established because the foreign port (the middle column) is 0 and the status is "listening".

Figure 9

There are several possible states a connection can be in. A listening state means that the originating port has been configured to accept connections from an incoming port. This is useful information if you are diagnosing a problem where you think something is failing because all available connections have been used up. If you see open listening ports in netstat, though, you know this is not the cause of the problem because there is a connection open and available.

The 2 nd one shows an active (established) connection between port 42424 and port 1791

Figure 10

To find out who asp.net is talking to on the 2 nd connection, return to the netstat output and look for an entry where the originating port is 1791 (left column) or the foreign port is 42424 (middle column). It appears in the first entry here, where we can see that asp.net is talking to the w3wp App Pool process.

Figure 11

Using netstat, you can figure out the chain of connections between multiple processes.

Based on the netstat output above, you can deduce that:

The UAPM Cache Service (pid 2456)

  • Originates on port 8082

  • Has 1 active connection to w3wp between ports 8082 and 2963

  • Has 1 available listener connection on 8082

The w3wp App Pool worker process (pid 536)

  • Has multiple originating ports (http, 1791, 2963, 2764, 2780 & 2781)

  • Has 1 active connection to asp.net between ports 1791 and 42424

  • Has 1 active connection to the UAPM Cache Service between ports 2963 and 8082

  • Has 1 active connection to Internet Explorer between ports http (80) and 1809

  • And 3 active connections to the dedicated SQL Server port (ms-sql-s) from 2764, 2780 & 2781

 

When a port is listed by name instead of a port number, that just means that it is a well-known port number. For instance, the well-known port number for http is 80, https is 443, telnet is 23, etc. In the case of MS SQL Server connections, the port number used is defined during database installation (it's 1433 by default) and given a name in the registry or the /etc/ports file in Unix/Linux.

From the list of connections to w3wp above, we can tell that there is only one active browser window open which is using UAPM at the moment. There may be other browser windows open, but if they have exceeded their timeout setting they will be shutdown and the port connection will be closed and the next time the user tries to do anything in that window they will have to login to UAPM again.