glassfish
  1. glassfish
  2. GLASSFISH-15574

copy a war in autodeploy folder of the cluster instances does not actually deploy the war

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1_b34
    • Fix Version/s: 4.0_b84_RC1
    • Component/s: deployment
    • Labels:
      None
    • Environment:

      Linux Ubuntu 32bit

      Description

      release: glassfish-3.1-b34-12_19_2010

      Create a cluster with 2 instances in the DAS and 2 instances in a host remote machine.

      Deploying a WAR in that cluster using admin gui works!

      Autodeploy feature in the cluster does NOT work:

      • I copied WAR file into autodeploy folder of each instances of the cluster:
        @DAS:
        /glassfish3/glassfish/nodes/localhost-domain1/mila/autodeploy/
        /glassfish3/glassfish/nodes/localhost-domain1/instance2/autodeploy/
        @remote machine:
        /glassfish3/glassfish/nodes/localhost-domain1/instance3/autodeploy/
        /glassfish3/glassfish/nodes/localhost-domain1/instance4/autodeploy/
      • just after copying the WAR, a new txt file has been automatically created for each instance:
        JerseyREST.war_deployed
      • and another file has been created in the /.autodeploystatus/ folder:
        JerseyREST.war (which is an empty file)

      "mila" is the name of an instance of my cluster (which is on the DAS)

      server.log of "mila" instance says:
      ###############################################
      [#|2011-01-13T14:06:58.459+0100|INFO|glassfish3.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=18;_ThreadName=Thread-1;|[AutoDeploy] Selecting file /root/tools/glassfish3/glassfish/nodes/localhost-domain1/mila/autodeploy/JerseyREST.war for autodeployment.|#]

      [#|2011-01-13T14:06:58.829+0100|INFO|glassfish3.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=18;_ThreadName=Thread-1;|[AutoDeploy] Successfully autodeployed : /root/tools/glassfish3/glassfish/nodes/localhost-domain1/mila/autodeploy/JerseyREST.war.|#]
      ###############################################
      Same for the other instances.

      So, it looked like WAR file was deployed in each instances, but actually it was not:

      28083 is the http port used by "mila" instance
      28084 is the http port used by "istance2"

      Same happens if I try http ports on the remote machine, for instance3 and 4.

      If I do the same things but deploying using the admin gui, everything works perfectly.

        Activity

        Hide
        Hong Zhang added a comment -

        Right, this is expected. The autodeploy feature which is mainly a developer feature is only supported on DAS and not cluster instances.

        Show
        Hong Zhang added a comment - Right, this is expected. The autodeploy feature which is mainly a developer feature is only supported on DAS and not cluster instances.
        Hide
        diluzio2000 added a comment -

        Ok!
        In this case I would suggest to remove the "autodeploy" folder creation when instance is created!

        If a developer see that "autodeploy" folder, he/she obviously thinks that autodeploy in cluster works!

        btw, thanks for the prompt reply. This avoided me long and stress debug time!

        Show
        diluzio2000 added a comment - Ok! In this case I would suggest to remove the "autodeploy" folder creation when instance is created! If a developer see that "autodeploy" folder, he/she obviously thinks that autodeploy in cluster works! btw, thanks for the prompt reply. This avoided me long and stress debug time!
        Hide
        Hong Zhang added a comment -

        Yes, good point. I am going to change this to RFE and see if we can clean this up in the next release.

        Show
        Hong Zhang added a comment - Yes, good point. I am going to change this to RFE and see if we can clean this up in the next release.
        Hide
        Hong Zhang added a comment -

        change to RFE to see if we can clean this up and make it less confusing to user

        Show
        Hong Zhang added a comment - change to RFE to see if we can clean this up and make it less confusing to user
        Hide
        Jeremy_Lv added a comment - - edited

        Hong:

        It seems the autodeploy folder will not generated when we create an instance on the cluster. I think we should marked it as fixed in V4.0 released version.
        (Marked the autodeploy folder won't support when it comes to the cluster or standalone instance.)

        Thanks

        Jeremy.

        Show
        Jeremy_Lv added a comment - - edited Hong: It seems the autodeploy folder will not generated when we create an instance on the cluster. I think we should marked it as fixed in V4.0 released version. (Marked the autodeploy folder won't support when it comes to the cluster or standalone instance.) Thanks Jeremy.
        Hide
        Hong Zhang added a comment -

        Jeremy, you are right. I tried to create/start a cluster and also a standalone instance and no longer see autodeploy directory under the instances directory. I am marking this RFE as fixed.

        Show
        Hong Zhang added a comment - Jeremy, you are right. I tried to create/start a cluster and also a standalone instance and no longer see autodeploy directory under the instances directory. I am marking this RFE as fixed.

          People

          • Assignee:
            Hong Zhang
            Reporter:
            diluzio2000
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: