glassfish
  1. glassfish
  2. GLASSFISH-12654

Issues with <engine> for deployed application

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Component/s: rest-interface
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      12,654

      Description

      To reproduce, deploy the attached singleton_ejb_war.ear
      After deployment, go to
      http://localhost:4848/management/domain/applications/application/singleton_ejb_war/module
      It listed out the 2 modules. <== Good.
      Now continue to singletonejb.jar, you see that there is no engine listed. This is a bug.

      In domain.xml, it says:

      <module name="singletonejb.jar">
      <engine sniffer="ejb" />
      <engine sniffer="security" />
      </module>

      <module name="singletonweb.war">
      <engine sniffer="security" />
      <engine sniffer="web" />
      </module>

      "security" is suppose to be hidden, i will expect to see "ejb". or "web".

      =========
      Another issue is that, for <application>, engine is listed. But 'sniffer' is an attribute, not a child under
      engine.
      To see this, go to
      http://localhost:4848/management/domain/applications/application/singleton_ejb_war/engine
      notice that "ejb" is shown as child, not as the sniffer attribute.

      In domain.xml, it says:
      <application location="$

      {com.sun.aas.instanceRootURI}

      /applications/singleton_ejb_war/"
      name="singleton_ejb_war" object-type="user">

      <engine sniffer="ear" />

        Issue Links

          Activity

          Hide
          Anissa Lam added a comment -

          The fix doesn't solve the first issue i raised.
          If you deploy the attached ear,

          domain.xml says:

          <module name="singletonejb.jar">
          <engine sniffer="ejb" />
          <engine sniffer="security" />
          </module>

          <module name="singletonweb.war">
          <engine sniffer="security" />
          <engine sniffer="web" />
          </module>

          but
          if you to
          http://localhost:4848/management/domain/applications/application/singleton_ejb_war/module/inglet
          onejb.jar

          you don't see any <engine> under it.

          Basically there is no engine shown for any <module> under <application>
          You can try something simplier, just deploy hello.war if you want, the same issue occurs. I can't see
          any engine.

          Show
          Anissa Lam added a comment - The fix doesn't solve the first issue i raised. If you deploy the attached ear, domain.xml says: <module name="singletonejb.jar"> <engine sniffer="ejb" /> <engine sniffer="security" /> </module> <module name="singletonweb.war"> <engine sniffer="security" /> <engine sniffer="web" /> </module> but if you to http://localhost:4848/management/domain/applications/application/singleton_ejb_war/module/inglet onejb.jar you don't see any <engine> under it. Basically there is no engine shown for any <module> under <application> You can try something simplier, just deploy hello.war if you want, the same issue occurs. I can't see any engine.
          Hide
          Anissa Lam added a comment -

          Created an attachment (id=4608)
          hello.war

          Show
          Anissa Lam added a comment - Created an attachment (id=4608) hello.war
          Hide
          Anissa Lam added a comment -

          Change to MS4 , please give this a high priority.

          Show
          Anissa Lam added a comment - Change to MS4 , please give this a high priority.
          Hide
          Jason Lee added a comment -

          -> Ludo

          Show
          Jason Lee added a comment - -> Ludo
          Hide
          ludo added a comment -

          cheching for null and in this case, return the annotated type.
          Committed revision 39416.

          Show
          ludo added a comment - cheching for null and in this case, return the annotated type. Committed revision 39416.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: