But why do we have to specify port all of the sudden if we use the same
port as where the server is installed? Does anyone know if this is an
intended change?
- Hong
sankara rao bhogi wrote:
> Karthik Sudarshan wrote:
>
>> Hi all,
>> I installed Glassfish v2 milestone 3 build (which is today's build
>> :) ) on Windows XP. I tried to deploy a webapp using asadmin deploy and
>> it failed saying the admin server is not accessible, wheresas I could
>> login to the admin console and deploy the same war using the admin
>> console. The exact message I got was this:
>>
>> CLI171 Command deploy failed : Deployment of application failed - Unable
>> to conn
>> ect to admin-server. Please check if the server is up and running and
>> that the
>> host and port provided are correct.
>>
>> Also, there were no errors while starting the server, I checked
>> server.log for that. Is this specific to Win XP? Is there a workaround
>> or have I missed anything? I have an install script which uses asadmin
>> for deploying our application, and using admin console is not an
>> option :)
>
>
> If you specify "--port 4848" option to "asadmin deploy" it would work.
>
> regards
> sankar
>
>>
>> Regards,
>> Karthik
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>