It's all about the answers!

Ask a question

WebSphere 8.5.5 Initialization Failing at Startup


E Muehl (325) | asked Jun 29 '15, 3:10 p.m.
Running WebSphere 8.5.5 on RHEL 6.5.

WebSphere appears to start but will not initialize using the startServer.sh script.  Looking at the log, the failure appears to happen here:

ADMU3028I: Conflict detected on port 2809. Likely causes: a) An instance of the server server1 is already running  b) some other process is using port 2809

ADMU3029I: Conflict detected on port 2089 for endpoint JSR160RMI_CONNECTOR_ADDRESS of the server server1

ADMU3027E: An instance of the server may already be running: server1

ADMU3002E: Exception attempting to process server server1

ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1

This all happens following a reboot of the server.

Has anyone seen this before?

Comments
Guido Schneider commented Jun 29 '15, 3:38 p.m.

Have you multiple profiles? 


E Muehl commented Jun 29 '15, 3:49 p.m.

Why, yes.  One for work, one for not work - in theory!

One answer



permanent link
Donald Nong (14.5k414) | answered Jun 29 '15, 8:56 p.m.
Apparently you have port conflicts.

Normally, when you create multiple WAS profiles using WCT or PMT, you should not have any port conflicts. To confirm which process is listening on port 2809, run the following command.
netstat -lanp | grep 2809
Regardless whether it is another WAS profile listening on that port, you can always create a new WAS profile with a new set of ports - 2809 is the default "Bootstrap port" for the first WAS profile, and each WAS profile should have its own and unique bootstrap port (well for all types of port actually).

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.