Pages

Tuesday 12 November 2013

Error starting managed server from Console :Unable to create a server socket for listening on channel "Default"

While starting the managed server from the Admin console, after nodemanager configuration, managed server was failing with status as "FAILED_to_START"

Unable to create a server socket for listening on channel "Default". The address 151.49.38.9 might be incorrect or another process is using port 18101: java.net.BindException: Cannot assign requested address.

Solution:Setup was two node cluster. I configured nodemanager and started it. but in console node manager configuration for managed server opam_server2 was showing localhost and hence it was trying to start from first node(where domain was configured) and it was failing. So update localhost with node2 hostname as below.


In Weblogic console, go to Environment -> Machines -> Configuration -> Node  Manager.

Update opam_server2 manager server with remote server host name(test2.opam.com).