From: <modjklist_at_comcast.net>
Date: Tue, 3 Jul 2012 18:21:57 +0000 (UTC)

I am observing the following:

asadmin> list-domains
domain1 not running
Command list-domains executed successfully.
asadmin> start-domain domain1 --port 4850
There is a process already using the admin port 4850 -- it probably is another instance of a GlassFish server.
Command start-domain failed.

Shouldn't the "list-domains" show running domains on port 4850? Or, more importantly, how do I stop whatever is running on port 4850, so I can start domain1 on that port?