Recent changes to bugs

Cant log to file - microlog produces invalid file path

Zakhar — Thu, 02 Dec 2010 09:31:20 -0000

My phone is Nokia 6303i. It has got MicroSD card (E:/, the root name was checked with FileSystemRegistry.listRoots).
I am using microlog-2.3.5.

My MIDlet has 2 sequential steps in its constuctor:
1. Create file "by hand" using FileConnection API (filename = "file:///E:/log.txt")
2. Create FileAppender and call its setFileName () method.

When I start my MIDlet on my phone I see the following:
1. First, the file is created "by hand", the phone ask me for the confirmation to create file. I press "info" to get additional info about the file created.
The phone displays:
Location: Memory Card
File: log.txt.
I confirm the operation. The file is created without any problems.
2. Then the phone asks me again for the confirmation to create file in the phone's Gallery. Why is in the gallery??? I press "info" to get additional info about the file created.
Location: Memory Card///E:
File: log.txt
I confirm the operation. After that exception happens.
"Illegal Argument java/lang/IllegalArgument exception
Invalid name".
For me it looks like the bug in microlog's FileAppender.

First log statement at valid level is lost with no appenders

Anonymous — Tue, 01 Dec 2009 19:26:11 -0000

This is an extremely minor bug.

As of the latest version of net.sf.microlog.core.Logger (revision 1399), a simple logic error causes the first log statement (at a valid priority level) on a Logger to be lost when no appenders have been added. In line 249, the integer value nofAppenders is set to the size of the appenderList Vector. However, when nofAppenders is zero and a ConsoleAppender is added in line 257, nofAppenders is not incremented to account for the new appender. Then attempting to iterate over the appenders in appenderList on line 270 fails since nofAppenders is still zero.

Adding "nofAppenders++;" directly after line 257 fixes the bug.

Not possible to set the lineseparator in AbstractFileAppende

Johan Karlsson — Fri, 16 Oct 2009 07:31:02 -0000

Not possible to set the lineseparator in AbstractFileAppender.

Sun SPOT does not work in Microlog V2.0.x

Johan Karlsson — Wed, 14 Oct 2009 11:41:41 -0000

Microlog does not work out-of-the-box in v2.0.3. There is no jar available. However when compiling the code, the ConsoleAppender is reported to work.

Comments in properties files causes problems

Johan Karlsson — Tue, 13 Oct 2009 20:09:11 -0000

If the properties file starts with a #-sign, the reading of the properties files fails. This will lead to a NPE when reading the properties file.

isDebugEnabled() creates a NullPointerException

Johan Karlsson — Tue, 07 Jul 2009 06:06:36 -0000

When calling isDebugEnabled() a NullPointerException is thrown.

RecordStoreAppender fails with java.lang.RuntimeException: W

Reiner Saddey — Thu, 26 Feb 2009 07:40:32 -0000

Applies to:

Both Version 1.0.0 and current trunk (at revision 721).

Symptom:

Only the first log request succeeeds. Subsequent requests fail with "java.lang.RuntimeException: Writing to closed ByteArrayOutputStream."

Cause:

Within method createLogData RecordStoreAppender closes its dataOutputStream on each log request, causing all but the first log request to fail.

Neither dataOutputStream nor byteArrayOutputStream must be closed (not even within method close()), as they are created within the constructor and assumed to be available forever.

Fix:

Just remove the "dataOutputStream.close();" from method createLogData.

Notes:

1. As DataOutputStream uses the decorator pattern, its close() will delegated to its decorated OutputStream.

2. jaywayjohan and k_o_ appear not to be able to agree upon as to whether dataOuputStream and byteArrayOutputStream should be class fields or local variables.

FileAppender not working in some environments

Johan Karlsson — Sun, 28 Dec 2008 08:54:06 -0000

The FileAppender does not not log correctly in all environment. This is where the logging takes to much time. The solution is to execute the logging in its own thread, the same was as is done in S3FileAppender et.al.

Coverage report is not correct

Johan Karlsson — Tue, 09 Dec 2008 20:11:26 -0000

The coverage reports from the Java ME tests are not correct. They show 0% although tests are executed.

microlog.properties is overwritten by one in microlog.jar

Jimisola Laursen — Sun, 24 Aug 2008 21:23:54 -0000

The issue is that the user defined microlog.properties file is overwritten during packaging by the example properties that packaged with the jar file.

The workaround could be to open the MicroLog0.5.0.2.jar file in winzip and delete the microlog.properties file.

https://sourceforge.net/forum/message.php?msg_id=5191139