[java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '7001']

[Kumar Allamraju]

If you are going to start managed servers from the command line, then
you don't need nodemanager. The way managed server's can be started
& stopped via console is below

1. start NodeManaged on a remote box
2. Create Managed server & fill in the fields in remote start tab
3. Start the server via admin console.

--
Kumar

Sunil Tomar wrote:

> Hi,
>
> I am setting a admin and multiple managed servers environment for clustering. Some
> of the important settings which i have made are as follows.
>
> 1) Added the "-Dweblogic.management.server=172.16.3.41:7001" to the java command
> in startmanagedweblogic.cmd file along with all other parameters to this java command.
> Where "172.16.3.41:7001" is the IP address of the Admin server.
>
> 2) Modified the "nodemanager.hosts" file to add the IP address of the admin server(
> the same as above).
>
> 3) Added "-Dweblogic.nodemanager.listenAddress=172.16.2.103" in nodemanager.cmd
> file.
>
> after doing all these needed settings along with other settings through my admin
> server console, when i start my managed server through the admin server console,
> then i get the following error the error log is attached also.
>
> ERROR::START
> ***************************************
> The WebLogic Server did not start up properly.
> Exception raised: weblogic.management.configuration.ConfigurationException: connecting
> to
> http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
> [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
> HTTP to server: 'localhost', port: '7001']
> ***************************************
> ERROR::END
>
> The point to note is that even after giving the management server IP address in the
> host file and startmanagedserver.cmd file, manage server is still taking localhost:7001
> as the managed server.
>
> Please help....
>
> regards,
> Sunil Tomar
>