glassfish
  1. glassfish
  2. GLASSFISH-16635

context-root not available after deploying Jersey simple-servlet sample, sometimes rebooting Glassfish enables war

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1_dev
    • Fix Version/s: 3.1.1_dev
    • Component/s: jax-rs
    • Labels:
      None
    • Environment:

      Description

      Deploying Jersey sample simple-servlet to Glassfish 3.1, and trying to access application URL [1], results in browser displaying:

      "HTTP Status 404 -

      type Status report

      message

      descriptionThe requested resource () is not available.
      GlassFish Server Open Source Edition 3.1"

      The context-root is not available in browser after deploying Jersey sample simple-servlet to Glassfish (Version = GlassFish Server Open Source Edition 3.1 (build 43))

      Restarting Glassfish sometimes enables context-root to be made available, but not consistently.

      URL to access in browser after successful deployment is :
      [1] http://localhost:8080/SimpleServlet/resources/start

      asadmin list-components shows that the .war is successfully deployed
      % asadmin list-components
      simple-servlet <web>
      Command list-components executed successfully.

      The source for this simple-servlet sample is available at [2].
      [2] http://java.net/projects/jersey/sources/svn/show/trunk/jersey/samples/simple-servlet?rev=4960

        Issue Links

          Activity

          Hide
          jbenoit added a comment -

          updated Environment section of bug report: mvn version used to build simple-servlet.war, and using windows XP platform. simple-servlet.war is attached to bug report.

          Sometimes shutting down Glassfish via:
          asadmin stop-domain domain

          followed by restarting server via:
          asadmin start-domain domain1

          will make the application available, but even that workaround is not consistent. Sometimes, I've restarted via asadmin stop-domain/start-domain multiple times and app is still not available.

          Show
          jbenoit added a comment - updated Environment section of bug report: mvn version used to build simple-servlet.war, and using windows XP platform. simple-servlet.war is attached to bug report. Sometimes shutting down Glassfish via: asadmin stop-domain domain followed by restarting server via: asadmin start-domain domain1 will make the application available, but even that workaround is not consistent. Sometimes, I've restarted via asadmin stop-domain/start-domain multiple times and app is still not available.
          Hide
          Jakub Podlesak added a comment -

          This could be related to http://java.net/jira/browse/GLASSFISH-16118
          Again a non-deterministic behavior when it comes to the Servlet 3/JAX-RS based application deployment.

          Show
          Jakub Podlesak added a comment - This could be related to http://java.net/jira/browse/GLASSFISH-16118 Again a non-deterministic behavior when it comes to the Servlet 3/JAX-RS based application deployment.
          Hide
          Jakub Podlesak added a comment -

          Workaround:

          set the following JVM property on the GF container and restart:

          asadmin create-jvm-options -Dorg.glassfish.web.parsing=true

          the issue should be gone and the application deployed all right under
          http://localhost:8080/SimpleServlet/resources/start

          Show
          Jakub Podlesak added a comment - Workaround: set the following JVM property on the GF container and restart: asadmin create-jvm-options -Dorg.glassfish.web.parsing=true the issue should be gone and the application deployed all right under http://localhost:8080/SimpleServlet/resources/start
          Hide
          scatari added a comment -

          Approved for 3.1.1. Please make sure to include "Fix in version" as "3.1.1_b09". Currently B09 is targeted for 06/23.

          Show
          scatari added a comment - Approved for 3.1.1. Please make sure to include "Fix in version" as "3.1.1_b09". Currently B09 is targeted for 06/23.
          Hide
          scatari added a comment -

          Fix for the dependent issue, 16872 was integrated into B10.

          Show
          scatari added a comment - Fix for the dependent issue, 16872 was integrated into B10.

            People

            • Assignee:
              Jakub Podlesak
              Reporter:
              jbenoit
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: