[
https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841130#action_12841130
]
Forrest Xia commented on GERONIMO-4959:
---------------------------------------
I verified remote deploy on the latest jetty 2.1.5 snapshot build (got from
http://people.apache.org/builds/geronimo/server/binaries/2.1/latest/), there is
no problem.
Some environment settings may impact remote deployment:
1. firewall
Ensure the remote server has no firewall running which forbids the remote
connection
2. TCP/IP setting
Ensure there is a ip-to-hostname mapping either via DNS or local hosts file on
the remote server machine. For example, you remote host ip is 10.0.0.2, if
there is no DNS service available, you shall add an entry into the local hosts
file:
10.0.0.2 hostname
> 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
> 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.
