felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Kriens (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4720) Web Console and Gogo rely on Log history buffer in the Log Service
Date Tue, 16 Dec 2014 10:19:13 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248087#comment-14248087

Peter Kriens commented on FELIX-4720:

I also added a new log command in Basic that takes options but can also be called without
any arguments.

   scope: felix
      -n, --noexceptions   Do not print exceptions.
      -r, --reverse   Reverse the printout order to oldest is last
      -l, --level   Minimum level (error,warning,info,debug). Default is warning. [optional]
      -m, --max   Maximum number of entries to print [optional]
      -s, --skip   Skip the first entries [optional]
      -y, --style   Print style (classic,abbr) [optional]

> Web Console and Gogo rely on Log history buffer in the Log Service
> ------------------------------------------------------------------
>                 Key: FELIX-4720
>                 URL: https://issues.apache.org/jira/browse/FELIX-4720
>             Project: Felix
>          Issue Type: Bug
>          Components: Gogo Command, Web Console
>            Reporter: Peter Kriens
> The OSGi Log Reader Service has a command to get the history of the log. However, the
specification states that this history can be empty. The Equinox framework is nowadays registering
a Log Reader Service that has such an empty history to prevent pinning objects in memory.

> Using the history this way was always at odds with the specification since the history
was only intended to hold the start up events. The primary model of the Log Service is a dispatcher.
> I suggest that the Gogo log command and the Web Console maintain their own history buffer
to become independent on this fragile history buffer in the Log Reader service.

This message was sent by Atlassian JIRA

View raw message