Show tasks originating from a TCP/IP service

You can identify all unresponsive tasks that originated from a specific TCP/IP service. For example, your system might be configured such that all transactions from your WebSphere Application Server come in on a specific TCP/IP service. Using transaction tracking you can identify all unresponsive tasks from the one source.

About this task

This procedure describes how to identify all the tasks that originate from a specific TCP/IP service.

Procedure

  1. In the TCP/IP Services view locate the TCP/IP service for the incoming service.
  2. Right-click the TCP/IP service and click Search > Tasks from TCP/IP Service.

Results

The results are displayed in the Search view. The view shows all the currently active tasks that originated from the TCP/IP service.

A screen capture of the Search view showing the tasks originating from the selected TCP/IP service. The TCP/IP service is identified in the view status field underneath the view tab.

You can run the search again by clicking the Search again icon The Search again icon, or by clicking F5.