Yes, this solves the problem (but won't help e.g. QL run).
thanks,
-marina
Kedar Mhaswade wrote:
> I am not sure. This code has not changed in ages (that doesn't
> mean it's not buggy).
>
> I believe this should be set to the machine's physical name while
> GlassFish starts. Setting this to "localhost" is not a good idea because
> then server itself can't tell anyone else what machine it's running on.
>
> JF has reported something on this. I am sorry, I have hard time following
> what's going wrong and what problem is being uncovered by his recent
> (last week) change.
>
> There definitely is a problem with what asadmin sends as the host header
> while doing a remote command. For example, when I do:
>
> asadmin list-commands, or
> asadmin deploy (or any other command)
>
> *without* specifying the --host, the http "host" header must
> be "localhost:port". But on my machine it sends
> "kedar-mhaswades-macbook-pro.local:8080", which might be
> the source of the problem. If someone knowledgeable here thinks
> that this is the problem, try to do the following:
>
> asadmin deploy *--host localhost*
>
> Please let me know if this works (for those who are seeing this
> problem).
>
> Regards,
> Kedar
>
>
> Byron Nevins wrote:
>
>> Is there a bug reported on this?
>> There is an easy way to "fix" this on the launching side.
>>
>> Launcher sets c.s.a.hN to the *canonical* host name.
>> It could easily be changed to set it to "localhost".
>>
>>
>>
>>
>>
>> Shing Wai Chan wrote:
>>
>>> Ken Paulsen wrote:
>>>
>>>>
>>>> I thought it was resolved after re-rebuilding, however, it's not.
>>>> The first deploy goes through fine and I can access the web app.
>>>> However, when I try to deploy a 2nd web app, it now gives me a 404
>>>> during the asadmin command:
>>>>
>>>> % asadmin deploy /glassfish/v3/admingui/war/target/admingui.war
>>>> Command deploy executed successfully.
>>>> % asadmin deploy /tmp/demo.war
>>>> Status: 404
>>>> Command deploy failed.
>>>>
>>>> If I do this in reverse order demo.war succeeds and admingui.war
>>>> gives the 404/failed message.
>>>
>>> ok. You may suffer from the same issue that Maria and me saw in the
>>> last few days.
>>> The workaround is as follows:
>>> change ${com.sun.aas.hostName} to hostname of your change in domain.xml
>>>
>>> Hope that this helps.
>>> Shing Wai Chan
>>>
>>>>
>>>> Ken
>>>>
>>>> Ken Paulsen wrote:
>>>>
>>>>>
>>>>> I just checked out and built v3 (a couple hours ago). Server
>>>>> starts up fine. Deployment of web apps go through fine (tried
>>>>> admingui.war and demo.war). When I attempt to access them after
>>>>> they're deployed, I get 404 w/ no errors in the log. Once on
>>>>> demo.war and admingui.war I was able to access them after
>>>>> stopping/starting the server... but I have not been able to
>>>>> reproduce that.
>>>>>
>>>>> Is this a known problem? Here is what showed up in the server.log
>>>>> when I did the deploy for these 2 apps (nothing showed up when
>>>>> attempting to access the apps -- just 404):
>>>>>
>>>>> admingui.war: http://papernapkin.org/pastebin/view/2030/
>>>>> demo.war: http://papernapkin.org/pastebin/view/2031/
>>>>>
>>>>>
>>>>> Ken
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>