users@glassfish.java.net

Re: Which port is asaadm really listening on?

From: vince kraemer <vince.kraemer_at_oracle.com>
Date: Wed, 27 Oct 2010 17:06:57 -0700

You have changed the port in the right place for the server...

But asadmin does not know that you changed the port. It thinks you want
to talk to a server on 4848.

To tell the asadmin command that it should talk to a server on a
particular port, try using asadmin --port 7848...

HTH,
vbk

Pete Helgren wrote:
> I changed the address and port in the domain.xml and then started
> glassfish admin console. Here is what I see:
>
> start-domain domain1
> Waiting for DAS to start ................
> Started domain: domain1
> Domain location: /glassfishv3/glassfish/domains/domain1
> Log file: /glassfishv3/glassfish/domains/domain1/logs/server.log
> Admin port for the domain: 7848
> Command start-domain executed successfully.
> asadmin>
>
> I then wanted to deploy an application that refused to autodeploy so I
> used this command:
>
> deploy domains/domain1/autodeploy/asaap3.war
> Remote server does not listen for requests on [localhost:4848].
> Is the server up?
> Unable to get remote commands.
> Closest matching local command(s):
> help
> Command deploy failed.
> asadmin>
>
> The server should be listening on 10.0.10.207 port 7878 NOT localhost
> port 4848. Do I misuderstand the concept of "server" here or is there
> some other place I need to change the port and address?
>
> Attempting to stop the domain I see this:
> stop-domain domain1
> CLI306 Warning - server is not running.
> Command stop-domain executed successfully.
> asadmin>
>
> So I am thinking I missed changing a setting somewhere.
>
> Thanks ...
>