[ https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller closed GERONIMO-4959. ---------------------------------- Resolution: Invalid I can only assume I had a configuration problem. For remote deploy to work, you have to have the server's ip address/hostname correct in 3 places: 1) deploy command: e.g. deploy.sh -host x.x.x.x 2) RemoteDeployHostname in config-substitutions.properties 3) ServerHostname in config-substitutions.properties Why require RemoteDeployHostname, when the client had to specify host/ip address, already? And more significantly, IMO, we should not require a specific ip address on ServerHostname. The default value of ServerHostname=0.0.0.0 should work for remote deploy... Something to handle in a separate JIRA. Should target improvements like this for 3.0... > Remote Deploy Broken on Jetty > ----------------------------- > > Key: GERONIMO-4959 > URL: https://issues.apache.org/jira/browse/GERONIMO-4959 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 2.1.4 > Reporter: Kevan Miller > Assignee: Forrest Xia > Fix For: 2.1.5 > > > I tried to use remote deploy, yesterday. After configuring > RemoteDeployHostname, it didn't work. > I poked around a bit more. Looks like remote deploy is broken on > geronimo-jetty6 but working on geronimo-tomcat6. > Should test this on 2.2, also -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.