glassfish
  1. glassfish
  2. GLASSFISH-14948

404 error when web start is enabled later for app client applications

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1_b31
    • Fix Version/s: 3.1_b32
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      build: ogs-3.1-b31-12_01_2010.zip

      Description

      1. In Admin Console create a standalone instance, e.g. sin1, and start it.
      2. Go to Standalone Instances, click on instance name and Applications tab, click Deploy button.
      3. Select both instance and server as targets, select showArgsGUI-client application, deselect Java Web Start checkbox and click OK.
      4. Go to the newly deployed application apge and enable Java Web Start, hit Save.
      5. Click on Launch link that appeared in the table.
      6. Provide some argument to the execution, select url for the http instance port and click Launch button. New browser window opens with 404 error.

      The same application launches fine in the scenario above if Java Web Start is not disabled and then enabled.

      There is an exception printed to instance's server.log, though I don't know if it is related:

      [#|2010-12-01T21:07:43.210-0800|INFO|oracle-glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=19;_ThreadName=Thread-1;|showArgsGUI-client was successfully deployed in 266 milliseconds.|#]

      [#|2010-12-01T21:09:42.695-0800|SEVERE|oracle-glassfish3.1|javax.enterprise.system.container.appclient.org.glassfish.appclient.server.core.jws|_ThreadID=19;_ThreadName=Thread-1;|Adapter[/___JWSappclient/___system] s1as/glassfish/modules/webservices-osgi.jar
      java.io.IOException: Broken pipe
      at sun.nio.ch.SocketDispatcher.write0(Native Method)
      at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:19)
      at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
      at sun.nio.ch.IOUtil.write0(IOUtil.java:60)
      at sun.nio.ch.IOUtil.write(IOUtil.java)

        Activity

        Hide
        Anissa Lam added a comment -

        Transfer the Tim. The key point here is to deploy without enabling JWS, but enable it AFTER deployment will cause 404 when trying to launch this app client.

        Show
        Anissa Lam added a comment - Transfer the Tim. The key point here is to deploy without enabling JWS, but enable it AFTER deployment will cause 404 when trying to launch this app client.
        Hide
        Tim Quinn added a comment -

        If Java Web Start support is disabled when the application is deployed, then certain generated artifacts are not generated during that deployment. Simply re-enabling Java Web Start later does not automatically generated those missing files.

        It is not feasible for us to create the files we need after the app has been deployed. The user must redeploy the app with Java Web Start support enabled.

        Anissa, I have reassigned this to you in case there is some way the admin console can prevent the user from changing the Java Web Start enabled setting for an already-deployed application.

        Show
        Tim Quinn added a comment - If Java Web Start support is disabled when the application is deployed, then certain generated artifacts are not generated during that deployment. Simply re-enabling Java Web Start later does not automatically generated those missing files. It is not feasible for us to create the files we need after the app has been deployed. The user must redeploy the app with Java Web Start support enabled. Anissa, I have reassigned this to you in case there is some way the admin console can prevent the user from changing the Java Web Start enabled setting for an already-deployed application.
        Hide
        Anissa Lam added a comment -

        I didn't realize that JWS option should only be available during deploy and redeploy.
        I will not provide such checkbox after deployment so user can't change it.

        Show
        Anissa Lam added a comment - I didn't realize that JWS option should only be available during deploy and redeploy. I will not provide such checkbox after deployment so user can't change it.
        Hide
        Tim Quinn added a comment -

        I probably should have made this clearer to begin with in the one-pager, etc.

        Apologies.

        Show
        Tim Quinn added a comment - I probably should have made this clearer to begin with in the one-pager, etc. Apologies.
        Hide
        Anissa Lam added a comment -

        np. back to admingui.

        Show
        Anissa Lam added a comment - np. back to admingui.
        Hide
        Anissa Lam added a comment -

        I think we shouldn't hide the JWS info after deployment, otherwise user may not know why there is no launch link for this app client.
        The changes i implemented:

        • After deployment, the JWS checkbox is read only. There is inline help telling user they must redeploy the app to change this support.
        • In redeploy screen, show the JWS checkbox (this was hidden before), which will show them the current state of this property, and user is allowed to change that.

        And as previously discussed, JWS is checked by default for both application and app client type deployment

        Marking this fixed.

        Show
        Anissa Lam added a comment - I think we shouldn't hide the JWS info after deployment, otherwise user may not know why there is no launch link for this app client. The changes i implemented: After deployment, the JWS checkbox is read only. There is inline help telling user they must redeploy the app to change this support. In redeploy screen, show the JWS checkbox (this was hidden before), which will show them the current state of this property, and user is allowed to change that. And as previously discussed, JWS is checked by default for both application and app client type deployment Marking this fixed.
        Hide
        lidiam added a comment -

        Verified in build b40 - user can no longer change Web Start after application was deployed.

        Show
        lidiam added a comment - Verified in build b40 - user can no longer change Web Start after application was deployed.

          People

          • Assignee:
            Anissa Lam
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: