glassfish
  1. glassfish
  2. GLASSFISH-13169

Add diagnostic information to explain why a module is being resolved

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Invalid
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: OSGi
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      13,169

      Description

      The OSGi shell permits one to view what modules have been resolved at a
      particular point in time. However, it is also important to know why a module
      has been resolved. What module was it that triggered getting a module resolved?

      This is a request to add diagnostic information to the system so that one can
      find out why a module was resolved. Preferably, this would show the entire chain
      of resolutions, starting with the explicit activation of a module, i.e., a
      module that is in the Active state. For example, if module A is activated, and
      it references module B which reference modules C which in turn references D, it
      should be possible to execute some command or view some log output and see:

      D <-- C <-- B <-- A

      The inspect command in the OSGi shell does this to some extent. However, it is
      not clear what the meanings of package, bundle, fragment and service are WRT an
      OSGi module, and the dependencies as shown by that command appear to be
      theoretical based on what is declared in the meta data rather than what actually
      happened when a module was loaded.

        Activity

        Tom Mueller created issue -
        kenaiadmin made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 13169 44773
        Chris Kasso made changes -
        Fix Version/s not determined [ 11149 ]
        Tom Mueller made changes -
        Assignee dochez [ dochez ] Sanjeeb Sahoo [ ss141213 ]
        Sanjeeb Sahoo made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Tom Mueller made changes -
        Resolution Won't Fix [ 2 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Sanjeeb Sahoo made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Invalid [ 6 ]

          People

          • Assignee:
            Sanjeeb Sahoo
            Reporter:
            Tom Mueller
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: