If you have a machine setup which includes "WebSphere Portal server" and "WebSphere Application server" running on same machine along with another instance of "WebSphere Portal server" then you might end up getting an error while starting the "server1" instance when the WPS is already started.
This is due to port conflict between processes "server1" and "WebSphere Portal". To resolve this issue, follow these simple steps.
1. Stop all WebSphere processes: Application Servers, node agents, and the deployment manager.
2. View all ports in use on the operating system by issuing a netstat -a command (in Windows). Make note of any ports in use. This way it gives the ports that are used by the Portal server as whole but does not give any details of each port.
3. To know exact port details we need to look in serverindex.xml file in the wp_profile folder of the portal installation. Open the serverindex.xml file for your server. You can find it in the directory
In the serverindex.xml, we will have all the ports classified by the each server instance. By looking at the server entries for serverName="WebSphere_Portal" we can find the ports that are used by the Portal server. Here we will have two ports assigned to default_host and admin_consoleeach, where one port is for the secure communication.
4. Check this file for any of the port conflict with the result in step-2.
5. Resolve the port conflict by editing the serverindex.xml and change the conflicting port number to one that is not in use, then restart all the WebSphere processes.
Another way and simple way which we can use to identify the ports for the server by using ConfigEngine.bat command.
The following are the steps to achieve this
1. Open the ConfigEngine.bat or .sh directory (\IBM\WebSphere\wp_profile\ConfigEngine\ConfigEngine.bat ) from the command prompt.
2. Run the following command
The generated output in that file will something look like below
Error occurred during startup :com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4
This is due to port conflict between processes "server1" and "WebSphere Portal". To resolve this issue, follow these simple steps.
1. Stop all WebSphere processes: Application Servers, node agents, and the deployment manager.
2. View all ports in use on the operating system by issuing a netstat -a command (in Windows). Make note of any ports in use. This way it gives the ports that are used by the Portal server as whole but does not give any details of each port.
3. To know exact port details we need to look in serverindex.xml file in the wp_profile folder of the portal installation. Open the serverindex.xml file for your server. You can find it in the directory
\wp_profile\config\cells\nodeName\nodes\nodeName\serverindex.xml
In the serverindex.xml, we will have all the ports classified by the each server instance. By looking at the server entries for serverName="WebSphere_Portal" we can find the ports that are used by the Portal server. Here we will have two ports assigned to default_host and admin_consoleeach, where one port is for the secure communication.
 |
| serverindex.xml |
5. Resolve the port conflict by editing the serverindex.xml and change the conflicting port number to one that is not in use, then restart all the WebSphere processes.
Another way and simple way which we can use to identify the ports for the server by using ConfigEngine.bat command.
The following are the steps to achieve this
1. Open the ConfigEngine.bat or .sh directory (\IBM\WebSphere\wp_profile\ConfigEngine\ConfigEngine.bat ) from the command prompt.
2. Run the following command
ConfigEngine.bat list-server-ports -DPassword=password3. After successfully running the command. It will generate a text file with all available ports at the following (\IBM\WebSphere\wp_profile\ConfigEngine\log\WebSphere_Portal_PortMatrix.txt) location.
The generated output in that file will something look like below
Ports for WebSphere_Portal
- WC_defaulthost=10039
- WC_adminhost=10042
- WC_defaulthost_secure=10029
- WC_adminhost_secure=10032
- BOOTSTRAP_ADDRESS=10035
- SOAP_CONNECTOR_ADDRESS=10025
No comments:
Post a Comment