glassfish
  1. glassfish
  2. GLASSFISH-14751

should not allow to create a app ref if the virtual server doesn't exist

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Component/s: web_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      14,751

      Description

      Whats happening here is that the older version of Glassfish used to give some
      error or at least notification within the instance_server's log file when trying
      to deploy/load an app into a virtual server that does not exist. There is no
      such error or notification in the server log for this release.

      Here is what I was able to do to reproduce this failure/lack of a failure.

      Asadmin commands for setup and reproduce:
      ------------------------------------------
      asadmin --user admin --host hostOne --port 4848 create-node-config --nodehost
      hostOne --installdir /opt/glassfish3/glassfish/.. hostOne_agent

      asadmin --user admin --host hostOne --port 4848 create-instance --node
      nodeOne_agent sa_server1

      asadmin --user admin --host hostOne --port 4848 deploy ./helloworld.war

      asadmin --user admin --host hostOne --port 4848 list-virtual-servers sa_server1
      server
      __asadmin

      asadmin --user admin --host hostOne --port 4848 create-application-ref
      --virtualservers=server123 --target sa_server1 helloworld

      -------------------------------------------------------------------------

      I attached the server.log file of the instance.

        Activity

        Hide
        dougd added a comment -

        Created an attachment (id=5501)
        Instance server.log

        Show
        dougd added a comment - Created an attachment (id=5501) Instance server.log
        Hide
        Hong Zhang added a comment -

        The v2 server.log used to say failed to load the web module on virtual server
        xxx from the web container code and the admin cli test was grepping for that
        error message. I don't know if the test should really grep for a string like
        this, but we do need some kind of warning message for this from the web
        container like in v2 so the user know what's going on.
        Assign to web team for evaluation how to handle this in v3.

        Show
        Hong Zhang added a comment - The v2 server.log used to say failed to load the web module on virtual server xxx from the web container code and the admin cli test was grepping for that error message. I don't know if the test should really grep for a string like this, but we do need some kind of warning message for this from the web container like in v2 so the user know what's going on. Assign to web team for evaluation how to handle this in v3.
        Hide
        Shing Wai Chan added a comment -

        Sending war-util/src/main/resources/com/sun/logging/enterprise/system/container/web/LogStrings.properties
        Sending web-glue/src/main/java/com/sun/enterprise/web/WebContainer.java
        Transmitting file data ..
        Committed revision 43372.

        Show
        Shing Wai Chan added a comment - Sending war-util/src/main/resources/com/sun/logging/enterprise/system/container/web/LogStrings.properties Sending web-glue/src/main/java/com/sun/enterprise/web/WebContainer.java Transmitting file data .. Committed revision 43372.

          People

          • Assignee:
            Shing Wai Chan
            Reporter:
            dougd
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: