glassfish
  1. glassfish
  2. GLASSFISH-13279

[PERF] javax.xml.rpc.handler resolution at startup taken from metro rather than module that is already loaded

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: not determined
    • Component/s: ejb_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      13,279

      Description

      The security module resolution is eventually causing the following resolutions :

      bundle ID bundle Name Imported packaged
      220 security MasterPasswordImpl
      158 interna-connector-api com.sun.appserv.connectors.internal-api.
      69 dol com.sun.enterprise.deployment
      220 org.glassfish.javax.ejb javax.interceptor
      26 metro javax.xml.rpc.handler

      The issue here is that even though bundle 220 packaged and exports javax.xml.rpc.handler, because metro has a bundle
      with a lower number (26 versus 220), the resolver is resolving the metro module to satisfy the import.

      Jerome needs to work with Richard if it would be compatible with the OSGi specs that the resolver looks in the current
      module before resolving externally a package. this might still be an issue with Equinox obviously.

      Another way would be to "install" the metro package last so its bundle ID is higher but that really seems like
      deferring the issue...

        Issue Links

          Activity

          Hide
          Marek Potociar added a comment -

          Resolution of this issue is also blocked by issue #13877 : It is impossible to
          debug any OSGi related issues with a frequent deadlock in GF.

          Show
          Marek Potociar added a comment - Resolution of this issue is also blocked by issue #13877 : It is impossible to debug any OSGi related issues with a frequent deadlock in GF.
          Hide
          Marek Potociar added a comment -

          JAXRPC API OSGi module separated from Metro webservices-osgi module. This fix
          was just comitted into GF as part of Metro 2.1-b17 integration.

          What still remains to be done is to remove exporting of the JAXRPC API packages
          from EJB module(s). Thus reassigning the issue to the EJB container owners.

          Show
          Marek Potociar added a comment - JAXRPC API OSGi module separated from Metro webservices-osgi module. This fix was just comitted into GF as part of Metro 2.1-b17 integration. What still remains to be done is to remove exporting of the JAXRPC API packages from EJB module(s). Thus reassigning the issue to the EJB container owners.
          Hide
          dochez added a comment -

          I don't think there is anything else needed to be done by the EJB container but let me check all this and
          update the bug.

          Show
          dochez added a comment - I don't think there is anything else needed to be done by the EJB container but let me check all this and update the bug.
          Hide
          marina vatkina added a comment -

          I don't think we can change javax.ejb bundle because it's packaged according to
          the spec requirement

          Show
          marina vatkina added a comment - I don't think we can change javax.ejb bundle because it's packaged according to the spec requirement
          Hide
          dochez added a comment -

          I confirmed the changes are all we needed. closing this bug.

          Show
          dochez added a comment - I confirmed the changes are all we needed. closing this bug.

            People

            • Assignee:
              dochez
              Reporter:
              Tom Mueller
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: