Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 2.1.4
    • Fix Version/s: 2.1.5
    • Component/s: deployment
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      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

        Activity

        Hide
        Kevan Miller added a comment -

        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

        Show
        Kevan Miller added a comment - 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
        Hide
        Forrest Xia added a comment -

        From my tries, we don't need to do the 3rd change, the remote deploy on jetty just works fine.

        Show
        Forrest Xia added a comment - From my tries, we don't need to do the 3rd change, the remote deploy on jetty just works fine.
        Hide
        Kevan Miller added a comment -

        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...

        Show
        Kevan Miller added a comment - 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...
        Hide
        Forrest Xia added a comment -

        I also did testing on 2.1.4 and 2.2 jetty build, there are no problem either.

        Show
        Forrest Xia added a comment - I also did testing on 2.1.4 and 2.2 jetty build, there are no problem either.
        Hide
        Forrest Xia added a comment -

        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

        Show
        Forrest Xia added a comment - 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

          People

          • Assignee:
            Forrest Xia
            Reporter:
            Kevan Miller
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development