The version of Apache log4j used by SoundHelix.

[[ 🗃 ^aEp6o apache-log4j ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/aEp6o

SSH: git clone USERNAME@vervis.peers.community:aEp6o

Branches

Tags

v1_2_15_rc1 :: src / xdocs / lf5 /

faq.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.

-->
<document>
  
  <properties>
    <author email="BMarlborough@thoughtworks.com">Brad Marlborough</author>
    <title>LogFactor5 Users' Guide</title>
  </properties>
  
  <body>
    <section name="Frequently Asked Questions">


      <p><b>Q. What is LogFactor5?</b> </p>

      <p><b>A.</b> LogFactor5 is a Swing based GUI that leverages the
	power of log4j to provide developers with a sophisticated,
	feature-rich, visual tool for managing log messages.</p> 

      <hr/>

      <p><b>Q. Do I need to know how to use log4j in order to use LogFactor5?</b></p>

      <p><b>A.</b> Yes, the documentation for LogFactor5 assumes the
	user has some understanding of how log4j works. Note however
	that the LogFactor5 examples will run regardless of a user's
	log4j knowledge level.</p> <hr/>

      <p><b>Q. What are the memory requirements for LogFactor5?</b></p>

      <p><b>A.</b> The LogFactor5 logging console window uses around
	13 MB of memory to run on a Windows OS. Our memory profiling
	has shown that with a logging message of 25 words in length,
	and a stack trace nested seven methods deep, every 1000
	records displayed in the logging console uses about 6.5 MB of
	memory. For this reason, when you are setting the maximum
	number of log records to be shown, you should be careful that
	you have enough memory to display all of the records.  The
	default maximum number of records that will be displayed is
	set to 5000 to minimize the possibility of running out of
	memory. We recommend that Windows users have at least 96 MB of
	RAM when using LogFactor5.</p>

    </section>
  </body>
</document>
[See repo JSON]