Troubleshoot and support > Payments > Troubleshooting: Payments


Troubleshooting: Port conflicts

WebSphere Commerce Payments instances do not start properly because of port conflicts. The following messages might be logged in the SystemOut.log file to indicate the existence of a port conflict: 

SRVE0146E: Failed to Start Transport on host, port 9080. The
most likely cause is that the port is already in use.


NSMV0011E: Unable to start bootstrap server using port 9810.
Verify that no servers or other processes are already using the
bootstrap server port.


ADMC0015W: SOAP connector failed to start with exception: Address already in use.


Solution

To correct a port conflict issue, we will need to select another port number that is not already running on the system. Once you have determined the new port number, complete the following steps:

  1. Open the WebSphere Application Server Administration Console and sign on.

  2. On the left side of the WebSphere Application Server Administration Console, expand Servers and click Application Servers.

  3. Click on the application_server that has a port conflict.

  4. Scroll down to view the Additional Properties.

  5. The message that was posted in the SystemOut.log file, determines what to choose next.

    • If the message indicates a problem with the Transport port, click Web Container > HTTP transports.

      • Click the appropriate link under the Host column.

    • If the message indicates a problem with a Bootstrap, SOAP connector or another port, click End Points.

      • Click the appropriate link under the End Point Name column.

  6. Change the port number to the new port number and click Apply.

  7. Click save in the Message(s) box.

  8. A Save to Master Configuration message box is displayed. Click save within this message box.

  9. On the left side, expand Environment and click Update Web Server Plugin.

  10. Click OK to update the plug-in configuration file. The message box will post the following entry when the plug-in has been updated: 

    The web server plugin configuration was updated successfully.

  11. Restart the applicable Web server.

  12. Restart the applicable WCS instance or WebSphere Commerce Payments instance


+

Search Tips   |   Advanced Search