> Hi Anand,
>
> thanks for your reply. But I think it should be a normal function for a
> logging library to create logfiles for each start of an application. The
> renaming was only an example. Of course it would also be okay using the
> rollOver Function of log4cxx.
>
> But logging seems either s
Did you take a look at "ImmediateFlush" option? Is that what you want?
On 7/24/07, Andrew La Motte-Mitchell <[EMAIL PROTECTED]> wrote:
I didn't see any response to this question... was the discussion taken
off-line? If anyone knows anything about this caching feature I'd really
be
interested
i,
Looks like you are facing similar problem that I had faced few days back.
But I was on SPARC Solaris. I'm producing the problem statement and its
resolution below.
On Jun 19, 2007, at 7:58 AM, Anand Sherkhane wrote:
> Hi,
>
> I'm seeing a crash in CharsetDecoder when I execu
On 6/19/07, Curt Arnold <[EMAIL PROTECTED]> wrote:
On Jun 19, 2007, at 7:58 AM, Anand Sherkhane wrote:
> Hi,
>
> I'm seeing a crash in CharsetDecoder when I execute following
> statement in a test program:
> Logger::getLogger("test");
>
> Complet
Hi,
Yes, it is possible that 'plainMsg' was NULL.
I checked this behavior in a test program(passed NULL to LogRawMesg) and I
see similar crash.
Thanks for pointing it out.
Regards,
Anand.
On 6/23/07, Curt Arnold <[EMAIL PROTECTED]> wrote:
On Jun 22, 2007, at 12:34 AM, Anand
gards,
Anand.
On 6/21/07, Curt Arnold <[EMAIL PROTECTED]> wrote:
On Jun 21, 2007, at 12:38 AM, Anand Sherkhane wrote:
Hi,
Any updates?
Regards,
Anand.
On 6/20/07, Anand Sherkhane <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm seeing a crash in my app that uses log4cxx
Hi,
Any updates?
Regards,
Anand.
On 6/20/07, Anand Sherkhane <[EMAIL PROTECTED]> wrote:
Hi,
I'm seeing a crash in my app that uses log4cxx v0.10.0. Relevant stack
trace is produced below:
fee20218 _lwp_kill (6, 0, fa77a410, fee88ef8, 1, fa77a47c) + 8
fedb6e98 abort (feee1afc, 1b
Hi,
I'm seeing a crash in my app that uses log4cxx v0.10.0. Relevant stack trace
is produced below:
fee20218 _lwp_kill (6, 0, fa77a410, fee88ef8, 1, fa77a47c) + 8
fedb6e98 abort (feee1afc, 1bf, feead104, fee88248, 1, fa77a1a5) + 100
feee1ac4 _ZN10__cxxabiv111__terminateEPFvvE (7178ac, fa779e38,
Hi,
I'm seeing a crash in CharsetDecoder when I execute following statement in a
test program:
Logger::getLogger("test");
Complete stack trace is as follows:
ff01e42c _lwp_kill (6, 0, ffbff178, ff088f18, 1, ffbff1e4) + 8
fefb5c60 abort(ff0e1afc, 1bf, ff0ad104, ff088238, 1, ffbfef0d) + 100
f
Hi,
I'm seeing this message printed on console: "log4cxx: Large window sizes are
not allowed"
Any idea why this is happening?
My conf file looks like this:
log4j.rootLogger=DEBUG, abc
log4j.appender.abc=org.apache.log4j.RollingFileAppender
log4j.appender.abc.Threshold=DEBUG
log4j.appender.ab
f this mail does not belong to this mailing list. Please
suggest me an appropriate place to post this query.
On 3/29/07, Anand Sherkhane <[EMAIL PROTECTED]> wrote:
Hi,
I was using log4cxx 0.9.7 and during trial runs, it started crashing. Our
customer got paranoid when he read f
Hi,
I was using log4cxx 0.9.7 and during trial runs, it started crashing. Our
customer got paranoid when he read following statement at
http://logging.apache.org/log4cxx:
Regards,
Anand.
Hi,
I do not know if log4cxx supports this out-of-the-box but for your
application to do it should be a simple task, I guess.
Upon exit OR start, the application checks if their exists a log file and
renames it(with current timestamp, say), if it is.
Regards,
Anand.
On 3/27/07, Alexander Baur
Hi,
I'm building log4cxx using autogen, confgure, and make. It requires apr and
apr-util and cpp-unit amongst others.
For that, I first build apr and apr-util. I don't build cpp-unit because
that is optional.
Then I provide path to these packages when installing log4cxx. I wish to
know what all
14 matches
Mail list logo
