glassfish
  1. glassfish
  2. GLASSFISH-14961

[Regression] Warning message repeated twice in console

    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: deployment
    • Labels:
      None
    • Environment:

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

      Description

      When there is an issue with deployment of an application, the warning message is repeated. Steps to reproduce:

      1. Create a standalone instance and start it.
      2. Start database, e.g. asadmin start-database.
      3. Add instance as target to 2 default JDBC resources.
      4. Deploy attached test_create_war application (with create_timer context root).

      The following warning is displayed:

      Deployment succeeded with a warning, please look at the log file for details
      Application deployed with name create_timer. WARNING: Command _deploy did not complete successfully on server instance in1: org.glassfish.api.admin.CommandException: remote failure: Failed to load the application on instance in1. The application will not run properly. Please fix your application and redeploy. Failed to load the application on instance in1. The application will not run properly. Please fix your application and redeploy. Exception while loading the app. Please see server.log for...

      Note that "Failed to load (...) and redeploy." is repeated above.

        Activity

        Hide
        lidiam added a comment -

        Once this application fails to deploy, instance's state is reported as Restart Required.

        Show
        lidiam added a comment - Once this application fails to deploy, instance's state is reported as Restart Required.
        Hide
        Anissa Lam added a comment -

        I am seeing different thing when following the instructions. Do i need to deploy other app also ?

        After deployment,
        stageStatusMessage in "status" is set to ""Action failed create app ref failed; FAILURE: Command _deploy failed on server instance ST: org.glassfish.api.admin.CommandException: remote failure: Failed to load the application on instance ST. The application will not run properly. Please fix your application and redeploy.
        Failed to load the application on instance ST. The application will not run properly. Please fix your application and redeploy.
        Exception while loading the app. Please see server.log for more details. : EJB Timer Service is not available. Please see server.log for more details. "

        and

        stageStatus is FAILURE.

        But statusString is set to ""Application deployed with name test_create_war."

        So, i end up seeing the attached error. But the app is deployed.

        Request Hong to take a look.
        The warning that Lidia is seeing is whatever is returned from status and what i am seeing doesn't seem to be correct either.

        Here is the GUI code that extract the status information, found in v3/admingui/common/src/main/java/org/glassfish/admingui/common/util/DeployUtil.java

        around line#106

        public static boolean checkDeployStatus(DFDeploymentStatus status, HandlerContext handlerCtx, boolean stopProcessing, String warningMsgKey)
        {
        //TODO-V3 get more msg to user.
        //parse the deployment status and retrieve failure/warning msg
        ByteArrayOutputStream bos = new ByteArrayOutputStream();
        PrintWriter pw = new PrintWriter(bos);
        DFDeploymentStatus.parseDeploymentStatus(status, pw);
        byte[] statusBytes = bos.toByteArray();
        String statusString = new String(statusBytes);

        Show
        Anissa Lam added a comment - I am seeing different thing when following the instructions. Do i need to deploy other app also ? After deployment, stageStatusMessage in "status" is set to ""Action failed create app ref failed; FAILURE: Command _deploy failed on server instance ST: org.glassfish.api.admin.CommandException: remote failure: Failed to load the application on instance ST. The application will not run properly. Please fix your application and redeploy. Failed to load the application on instance ST. The application will not run properly. Please fix your application and redeploy. Exception while loading the app. Please see server.log for more details. : EJB Timer Service is not available. Please see server.log for more details. " and stageStatus is FAILURE. But statusString is set to ""Application deployed with name test_create_war." So, i end up seeing the attached error. But the app is deployed. Request Hong to take a look. The warning that Lidia is seeing is whatever is returned from status and what i am seeing doesn't seem to be correct either. Here is the GUI code that extract the status information, found in v3/admingui/common/src/main/java/org/glassfish/admingui/common/util/DeployUtil.java around line#106 public static boolean checkDeployStatus(DFDeploymentStatus status, HandlerContext handlerCtx, boolean stopProcessing, String warningMsgKey) { //TODO-V3 get more msg to user. //parse the deployment status and retrieve failure/warning msg ByteArrayOutputStream bos = new ByteArrayOutputStream(); PrintWriter pw = new PrintWriter(bos); DFDeploymentStatus.parseDeploymentStatus(status, pw); byte[] statusBytes = bos.toByteArray(); String statusString = new String(statusBytes);
        Hide
        Hong Zhang added a comment -

        Yes, I've noticed it also when I was debugging another issue. I have fixed it yesterday so it should be today's nightly.

        Show
        Hong Zhang added a comment - Yes, I've noticed it also when I was debugging another issue. I have fixed it yesterday so it should be today's nightly.
        Hide
        lidiam added a comment -

        Verified in promoted build b43.

        Show
        lidiam added a comment - Verified in promoted build b43.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: