glassfish
  1. glassfish
  2. GLASSFISH-17038

3.1.1 deployment performance - ejb container module get loaded for a pure web application

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.2.2
    • Component/s: ejb_container
    • Labels:
      None

      Description

      Using the felix console to monitor which module get loaded for the web application deployment, noticed the ejb container module got active and the ejb security module got resolved

      208|Active | 1|org.glassfish.ejb.ejb-container (3.1.1.SNAPSHOT)

      94|Resolved | 1|org.glassfish.security.ejb.security (3.1.1.SNAPSHOT)

      we need to figure out which dependency had triggered the ejb related modules get loaded/resolved, they should not be for a pure web application. I will attach the test web application in the issue next.

        Issue Links

          Activity

          Hide
          marina vatkina added a comment -

          According to Scott it's no longer critical

          Show
          marina vatkina added a comment - According to Scott it's no longer critical
          Hide
          Cheng Fang added a comment - - edited

          committed Rev: 48926 to 3.1.2 branch, moving annotation handler classes, archivist class, scanner class, and the related from ejb-container to ejb-connector.

          committed revision 48934 to trunk.

          Show
          Cheng Fang added a comment - - edited committed Rev: 48926 to 3.1.2 branch, moving annotation handler classes, archivist class, scanner class, and the related from ejb-container to ejb-connector. committed revision 48934 to trunk.
          Hide
          Cheng Fang added a comment -

          With the above fix and when web container obtains JavaEEIOUtils lazily, or when web container uses a generic JavaEEIOUtils impl, ejb container will not be loaded when deploying servlet/jsp-based web app.

          For jsf-based app, the lookup by jsf impl of "clientStateSavingPassword" will trigger the loading of global NamedNamingProxy, which includes EJBContext. As a result, ejb-container will be loaded. This naming proxy bootstrapping happens prior to the first lookup operation, and in this case jsf happens to perform the first lookup.

          Show
          Cheng Fang added a comment - With the above fix and when web container obtains JavaEEIOUtils lazily, or when web container uses a generic JavaEEIOUtils impl, ejb container will not be loaded when deploying servlet/jsp-based web app. For jsf-based app, the lookup by jsf impl of "clientStateSavingPassword" will trigger the loading of global NamedNamingProxy, which includes EJBContext. As a result, ejb-container will be loaded. This naming proxy bootstrapping happens prior to the first lookup operation, and in this case jsf happens to perform the first lookup.
          Hide
          Cheng Fang added a comment -

          In 4.0 trunk only, ejb-related annotation handler classes are moved back to ejb-container. See issue http://java.net/jira/browse/GLASSFISH-17988 (move ejb annotation handlers out of ejb-connector)

          Show
          Cheng Fang added a comment - In 4.0 trunk only, ejb-related annotation handler classes are moved back to ejb-container. See issue http://java.net/jira/browse/GLASSFISH-17988 (move ejb annotation handlers out of ejb-connector)
          Hide
          Hong Zhang added a comment -

          I just checked this for 3.1.2.2 and ejb container is no longer loaded (in active state) after deployment.

          Show
          Hong Zhang added a comment - I just checked this for 3.1.2.2 and ejb container is no longer loaded (in active state) after deployment.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: