geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Closed: (GERONIMO-1682) remote deployment fails when server is running on machine with DHCP
Date Thu, 16 Aug 2007 19:51:30 GMT


Donald Woods closed GERONIMO-1682.

       Resolution: Fixed
    Fix Version/s: 1.1.x

This should already have been fixed in the 1.1 releases.
If not, please reopen against 2.0.x.

> remote deployment fails when server is running on machine with DHCP
> -------------------------------------------------------------------
>                 Key: GERONIMO-1682
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.0
>         Environment: Windows 2003
>            Reporter: Song
>             Fix For: 1.1.x
> Remote deployment failed when I used IP address of a DHCP machine.
> C:\>deploy --host  --verbose deploy hello-1.0.war
> ......
> Username: system
> Password:
>     Uploading 1 file(s) to server
>     Error: Unable to distribute hello-1.0.war: st68rts17h
> st68rts17h
>         at
>         at
>         at
>         at
>         at
>         at
>         at<init>(
>         at<init>(
>         at
>         at
>         at
>         at 
>         at
>         at
>     org.apache.geronimo.deployment.plugin.remote.RemoteDeployUtil.connectToServer(
>         at
>     org.apache.geronimo.deployment.plugin.remote.RemoteDeployUtil.uploadFilesToServer(
>         at
>     org.apache.geronimo.deployment.plugin.remote.DistributeCommand.massageFileNames(
>         at
>     org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(
>         at
>         at
> "" is the DHCP ip for remote host "st68rts17h". During remote deployment,
following steps occur in turn:
> 1)Local server uses URI supplied from deployer tool (that is "") to get connector
for container on remote machine;
> 2)Remote machine replies the connectURL to itself, which is using short hostname(that
is "st68rts17h");
> 3)Local server uses URL reply from remote machine to upload application archive file.
But "st68rts17h" is not recognized by local server, so the error happens.
> That's why URI specified in deployer tool, regardless long hostname or IP address,  is
always converted to short hostname.
> So the only workaround is to manually add shortname of remote host to hosts file on local
> After I switched remote machine(running the server) to static IP and changed the machine
name to be the same as hostname which is resolvable by DNS, this problem went away.
> I think the logic of remote deploy need to be enhanced. Simply using URI specified in
the command line to connect to remote server runtime(step3 as I mentioned above) should be
much more understandable and workable.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message