glassfish
  1. glassfish
  2. GLASSFISH-11480

Not possible to use log TRACE in Felix console of GlassFish v3

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: not determined
    • Component/s: OSGi
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      11,480

      Description

      Hi,

      I'm connected to the Felix OSGI server of Glassfish v3 (using telnet localhost
      6666) and when I try to use the command :

      -> log DEBUG

      I receive the following message : No LogReaderService available

        Activity

        Hide
        Sanjeeb Sahoo added a comment -

        All glassfish logs appear in $

        {domain_dir}

        /logs/server.log. Either you can open
        the log file in your favorite editor or use "GlassFish admin console" to view
        the log file entries. To use the later option, open "http://localhost:4848,"
        select enterprise server node, select "view Log" tab.

        We will enhance GF to add a OSGi Log Reader as well.

        Show
        Sanjeeb Sahoo added a comment - All glassfish logs appear in $ {domain_dir} /logs/server.log. Either you can open the log file in your favorite editor or use "GlassFish admin console" to view the log file entries. To use the later option, open "http://localhost:4848," select enterprise server node, select "view Log" tab. We will enhance GF to add a OSGi Log Reader as well.
        Hide
        Richard S. Hall added a comment -

        The value of this depends on what you hope to see in the logs. You will not see logs from the Felix framework since it doesn't use the OSGi Log Service to log its messages (we tried to do this a long time ago, but it lead to deadlock issues since you tend to log at sensitive times and calling out to external code is problematic).

        If you want to see logs from installed bundles, then this could be accomplished as simply as installing the Apache Felix Log Service bundle. Not much else needs to be done, no?

        Show
        Richard S. Hall added a comment - The value of this depends on what you hope to see in the logs. You will not see logs from the Felix framework since it doesn't use the OSGi Log Service to log its messages (we tried to do this a long time ago, but it lead to deadlock issues since you tend to log at sensitive times and calling out to external code is problematic). If you want to see logs from installed bundles, then this could be accomplished as simply as installing the Apache Felix Log Service bundle. Not much else needs to be done, no?
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
        Hide
        TangYong added a comment -

        Hi sahoo,

        Now, trunk has merged gf osgi shell command, so, whether not resolving felix console related issues or not? If yes, should close the issue.

        Show
        TangYong added a comment - Hi sahoo, Now, trunk has merged gf osgi shell command, so, whether not resolving felix console related issues or not? If yes, should close the issue.

          People

          • Assignee:
            Richard S. Hall
            Reporter:
            charliem
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: