If a server process does not start or starts with errors, the following topics might help you to diagnose the problem.
For example, in a base or non-distributed
configuration on Windows systems, browse profile_root\config\cells/ApplicationServerCell\nodes\node_name\servers\server_name\server.xml,
and examine the XML tags for the properties of that resource. Change its initialState value
from START to STOP.
For example, browse profile_root/config/cells/ApplicationServerCell/nodes/node_name/servers/server_name/server.xml,
and examine the XML tags for the properties of that resource. Change its initialState value
from START to STOP.
addNode.sh localhost 8879 -includeapps -startingport 3333
The deployment manager is using the default SOAP port of 8879. Both processes are on the same machine. All of the installed applications (except the administrative console, which is a system application) on the application server are installed on the deployment manager.
The startingport parameter avoids a problem with coexisting node agent processes on one machine. All of the ports for the node agent process start at port number 3333. You can also assign ports specifically using the -portprops parameter.
See the description of the addNode command for more information.
chown -R QEJBSVR profile_root
The socket bind failed for host hostname and port portnumber. The port may already be in use.
This problem might occur if the network is slow, and the port listed in the message text did not finish listening when the application was stopped and restarted.
To verify that this is the problem, check the port status.
netstat -a
NETSTAT *CNN