Hi Hong,
Thanks a lot for the suggestion. It does work when I explicitly
specify the port. I do have the same query as you, which is why specify
the default port all of a sudden? :)
-Karthik
Hong Zhang wrote:
> Hi, Karthik
>
>> 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:
>
> Could you try to specify the port explicitly in your deploy command
> see whether it works?
>
> asadmin deploy --port 4848 foo.ear
>
> I noticed similar problem. Although I did "maven configure-runtime"
> which configures a PE environment (which uses the default port 4848),
> somehow the default port of the admin commands (not only deploy, but
> also list-components etc) is no longer "4848".
>
> - Hong
>
>>
>> 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 :)
>>
>> 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
>