felix-dev mailing list archives

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

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

Valentin Valchev commented on FELIX-4720:

So to reduce the used memory, we don't have to rely on a single service that tracks the log
entries, but instead Web Console, Gogo shell, should keep their own queue?

IMHO the equinox implementation by trying to 'prevent pinning objects in memory' would actually
force other OSGi applications do the same.

And if other OSGi applications, must provide their own Log Listener, how they are going to
show the log events that came *before* that application has been installed?

Another question? - Why anybody would use equinox log service or trying to be compatible with
that particular implementation if there are many other implementation that has a working Log
Reader Service. Wasn't OSGi specification intention to add some common services, so you don't
have to be vendor-specific?

> 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