Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 5 Dec 2014 08:49:12 +0000 (UTC)
From: "Peter Kriens (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12759629.1417769342000.82561.1417769352303@Atlassian.JIRA>
In-Reply-To: <JIRA.12759629.1417769342000@Atlassian.JIRA>
References: <JIRA.12759629.1417769342000@Atlassian.JIRA>
 <JIRA.12759629.1417769342378@arcas>
Subject: [jira] [Created] (FELIX-4720) Web Console and Gogo rely on Log
 history buffer in the Log Service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Peter Kriens created FELIX-4720:
-----------------------------------

             Summary: 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
(v6.3.4#6332)