There's setup details in the integration tests [1] HTH - Ray
[1] https://github.com/apache/felix/tree/trunk/logback/itests On Mon, Aug 27, 2018 at 9:15 AM, Raymond Auge <[email protected]> wrote: > My personal favourite is the Apache Felix Logback [1] integration which > supports immediate logging when follow the correct steps. I feel it's the > best logging solution available. > > There are a couple of prerequisites as outlined in the documentation. But > it's very simple to achieve your goal (NO BUFFERING OR MISSED LOG RECORDS)! > > [1] http://felix.apache.org/documentation/subprojects/ > apache-felix-logback.html > > - Ray > > On Mon, Aug 27, 2018 at 7:50 AM, BJ Hargrave via osgi-dev < > [email protected]> wrote: > >> Equinox has the LogService implementation built into the framework, so it >> starts logging very early. >> >> In the alternate, for framework related information, you can write your >> own launcher and it can add listeners for the framework event types. >> -- >> >> BJ Hargrave >> Senior Technical Staff Member, IBM // office: +1 386 848 1781 >> OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 >> [email protected] >> >> >> >> ----- Original message ----- >> From: David Leangen via osgi-dev <[email protected]> >> Sent by: [email protected] >> To: [email protected] >> Cc: >> Subject: [osgi-dev] Logger at startup >> Date: Sun, Aug 26, 2018 3:06 PM >> >> Hi! >> >> I’m sure that this question has been asked before, but I did not >> successfully find an answer anywhere. It applies to both R6 and R7 logging. >> >> I would like to set up diagnostics so I can figure out what is happening >> during system startup. however, by the time the logger starts, I have >> already missed most of the messages that I needed to receive and there is >> no record of the things I want to see. Another oddity is that even after >> the logger has started, some messages are not getting logged. I can only >> assume that there is some concurrency/dynamics issue at play. >> >> In any case, other than using start levels, is there a way of ensuring >> that the LogService (or Logger) is available when I need it? >> >> >> Thanks! >> =David >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> > > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > (@OSGiAlliance) > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
