On 10/12/2010 10:24 AM, Thorsten Schöning wrote:
I get an out_of_range exception everytime I use a logger which name is
longer than the name of the root logger
I'm not sure what this named root logger you're referring too. In xml
config it's just and in property format it's log4j.rootLogger.
On 10/15/2010 5:53 AM, Thorsten Schöning wrote:
Hello,
is there any way to get the method name of the logging caller in the
log message?
As you say, the log4j docs document %M in the PatternLayout (while
log4cxx does not) but caution against the inefficiency of it's use.
Additionally "The Co
>FromThorsten Schöning
>reply-toLog4CXX User
>toLog4CXX User
>date15 October 2010 11:14
>subjectapr_terminate called too early...
>mailing list Filter messages from
this mailing list
>
>Hello,
>
>I have a GUI-application in Borland C++-Builder 5 which I needed to
>add log
Hello,
is there any way to get the method name of the logging caller in the
log message? In some places %M is mentioned, but it doesn't seem to
work and is not in the documentation of class PatternLayout. With
log4perl and log4j I'm able to log the whole class path down to a
method and wondered if
Hello,
I have a GUI-application in Borland C++-Builder 5 which I needed to
add logging support using log4cxx. It started fine but I noticed
problems after closing the application. Like others on the net I have
the problem that the application crashes during accessing or deleting
some mutexes durin
