glassfish
  1. glassfish
  2. GLASSFISH-19900

4.0 SDK: Unable to deploy Concurrency Samples

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b79
    • Fix Version/s: 4.0_b80_EE7MS6
    • Component/s: concurrency
    • Labels:
      None
    • Environment:

      Description

      The three (3) Concurrency Samples in the 4.0 SDK full distribution fail to deploy. The test scenario is to build the sample and deploy on a local installation. Taking the executor sample as an example, the commands executed were:

      o cd $HOME/glassfish4/samples/concurrency/executor
      o mvn install
      [INFO] Installing /home/agpineda/glassfish4/samples/concurrency/executor/pom.xml to /home/agpineda/.m2/repository/org/glassfish-samples/executor/4.0-SNAPSHOT/executor-4.0-SNAPSHOT.pom
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESS
      [INFO] ------------------------------------------------------------------------

      o mvn cargo:start -Dglassfish.home=$HOME/workspace/glassfish4

      The following error is shown:

      [INFO] Building Sample Application using ManagedExecutorService 4.0-SNAPSHOT
      [INFO] ------------------------------------------------------------------------
      [WARNING] The POM for javax:javaee-api:jar:7.0-b78 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
      [INFO]
      [INFO] — cargo-maven2-plugin:1.3.2:start (default-cli) @ executor —
      [INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-glassfish:jar:1.3.2 for container glassfish3x
      [INFO] [talledLocalContainer] Using port 4848 for Admin.
      [INFO] [talledLocalContainer] Using port 8080 for HTTP Instance.
      [INFO] [talledLocalContainer] Using port 7676 for JMS.
      [INFO] [talledLocalContainer] Using port 3700 for IIOP.
      [INFO] [talledLocalContainer] Using port 8181 for HTTP_SSL.
      [INFO] [talledLocalContainer] Using port 3820 for IIOP_SSL.
      [INFO] [talledLocalContainer] Using port 3920 for IIOP_MUTUALAUTH.
      [INFO] [talledLocalContainer] Using port 8686 for JMX_ADMIN.
      [INFO] [talledLocalContainer] Using port 6666 for OSGI_SHELL.
      [INFO] [talledLocalContainer] Using port 9009 for JAVA_DEBUGGER.
      [INFO] [talledLocalContainer] Distinguished Name of the self-signed X.509 Server Certificate is:
      [INFO] [talledLocalContainer] [CN=wolfrun.us.oracle.com,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
      [INFO] [talledLocalContainer] Distinguished Name of the self-signed X.509 Server Certificate is:
      [INFO] [talledLocalContainer] [CN=wolfrun.us.oracle.com-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
      [INFO] [talledLocalContainer] Domain cargo-domain created.
      [INFO] [talledLocalContainer] Domain cargo-domain admin port is 4,848.
      [INFO] [talledLocalContainer] Domain cargo-domain admin user is "admin".
      [INFO] [talledLocalContainer] Command create-domain executed successfully.
      [INFO] [talledLocalContainer] GlassFish 3.x starting...
      [INFO] [talledLocalContainer] Waiting for cargo-domain to start ........
      [INFO] [talledLocalContainer] Successfully started the domain : cargo-domain
      [INFO] [talledLocalContainer] domain Location: /home/agpineda/glassfish4/glassfish/domains/cargo-domain
      [INFO] [talledLocalContainer] Log File: /home/agpineda/glassfish4/glassfish/domains/cargo-domain/logs/server.log
      [INFO] [talledLocalContainer] Admin Port: 4848
      [INFO] [talledLocalContainer] Command start-domain executed successfully.
      [INFO] [talledLocalContainer] remote failure: File not found : /home/agpineda/glassfish4/samples/concurrency/executor/target/executor-4.0-SNAPSHOT.war
      [INFO] [talledLocalContainer] Command deploy failed.
      [INFO] [talledLocalContainer] GlassFish 3.x is stopping...
      [INFO] [talledLocalContainer] Waiting for the domain to stop ..
      [INFO] [talledLocalContainer] Command stop-domain executed successfully.
      [INFO] [talledLocalContainer] GlassFish 3.x is stopped
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 34.879s
      [INFO] Finished at: Fri Mar 15 21:18:42 PDT 2013
      [INFO] Final Memory: 7M/212M
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.3.2:start (default-cli) on project executor: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.3.2:start failed: Failed to start the GlassFish 3.x container. At least one GlassFish deployment has failed: org.codehaus.cargo.util.CargoException: GlassFish admin command failed: asadmin exited 1 -> [Help 1]
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

      The same problem is seen on all 3 samples (executor, schedule, threads)

        Activity

        Hide
        anthony.lai added a comment -

        fixed in revision 958

        Show
        anthony.lai added a comment - fixed in revision 958
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Small nit: Java EE SDK b80 was already in progress at the time of this checkin so I am adjusting the fix version. If by any chance we end up restarting Java EE SDK build, I'll pick up the fix.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Small nit: Java EE SDK b80 was already in progress at the time of this checkin so I am adjusting the fix version. If by any chance we end up restarting Java EE SDK build, I'll pick up the fix.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Need to restart b80, resetting the fix version...

        Show
        Snjezana Sevo-Zenzerovic added a comment - Need to restart b80, resetting the fix version...
        Hide
        Alex Pineda added a comment -

        Issue is resolved with javaee_sdk build 80. Verified fix. Please update the bug accordingly.

        Show
        Alex Pineda added a comment - Issue is resolved with javaee_sdk build 80. Verified fix. Please update the bug accordingly.

          People

          • Assignee:
            anthony.lai
            Reporter:
            Alex Pineda
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: