IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Port 9090 Conflicts error on AIX

The problem: When you start your Managing Server, the following error is returned:

Error: Failed to Start Transport on host , port 9090. The most likely cause is that the port is already in use. Please ensure that no other applications are 
using this port and restart the server. 
com.ibm.ws.webcontainer.exception.TransportException: Failed to start transport
http: java.net.BindException: Address already in use.

The cause: There is a port number conflict between the WAS administrative console and WebSM service on AIX. Both use port 9090. WebSM is a tool that is useful to administrators who manage many AIX computers. The WAS administrative console is used to administer WAS. The port 9090 conflict on AIX is a known WAS issue. Ensure that no other applications are using this port.

The solution: Before starting the server, it is required to make sure that there are no pid files under the /tmp directory that was created by other users during previous operations. As another option, the right of executing these scripts can be restricted to one user by changing the ownership and mode of these files with chown and chmod commands.

For the Application Monitor component running on WAS, it is recommended that the same Windows account is used to operate the Managing Server. To modify the port number used by WAS administrative console, perform the following steps:

  1. Disable WebSM Service by issuing the following command:
    # /usr/websm/bin/wsmserver -disable

    Failure to complete this step before installing WebSphere Portal Server results in an incomplete deployment of portlets.

  2. Install WAS and WebSphere Portal Server (including fix packs and interim fixes).

  3. Modify the WAS administrative console port number 9090 in the following files to the desired port for the administrative console. Refer to WAS documentation for more information.

    • was_root/config/cells/cell_name/nodes /node_name/servers/server1/server.xml

    • was_root/config/cells/cell_name/virtualhosts.xml

  4. Restart WAS and WebSphere Portal Servers.

  5. Enable WebSM Service by issuing the following command:
    # /usr/websm/bin/wsmserver -enable


Parent topic:

Run the Managing Server

+

Search Tips   |   Advanced Search