You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2009/11/20 14:13:39 UTC
[jira] Created: (GERONIMO-4959) Remote Deploy Broken on Jetty
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.
[jira] Closed: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841141#action_12841141 ]
Forrest Xia commented on GERONIMO-4959:
---------------------------------------
I also did testing on 2.1.4 and 2.2 jetty build, there are no problem either.
> 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.
[jira] Commented: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844344#action_12844344 ]
Kevan Miller commented on GERONIMO-4959:
----------------------------------------
Must be dependent upon network/os environment then. Was definitely required for my testing (btw same for tomcat and jetty). Environment:
client = mac os server = ubuntu server running in parallels virtual machine
> 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.
[jira] Assigned: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Forrest Xia reassigned GERONIMO-4959:
-------------------------------------
Assignee: Forrest Xia
> 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.
[jira] Commented: (GERONIMO-4959) Remote Deploy Broken on Jetty
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844317#action_12844317 ]
Forrest Xia commented on GERONIMO-4959:
---------------------------------------
>From my tries, we don't need to do the 3rd change, the remote deploy on jetty just works fine.
> 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.