dking | 1 Jul 21:54 2009
Picon

Re: Writing to Database


Aswani wrote:
> 
> Hello Everybody,
> 
> We want to write Logs to database, but not one DB call per logging event.
> Plans are like collecting all logging events till the end of each
> server request, and commit that to database as a single message(single
> record). I mean collect all log messages of a request (client - server -
> client)
> 

Were you able to do this? If so how?
--

-- 
View this message in context: http://www.nabble.com/Writing-to-Database-tp21360891p24296034.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
Mark Anderson | 6 Jul 13:36 2009
Picon

What versions of Windows does NTEventLogAppender support?

I have been unable to find a list of the versions of Windows that
NTEventLogAppender is supported on. Could someone please supply such a
list?

I am specifically interested in whether Windows Server 2008 64 bit is
supported.

Thanks,
Mark
Sandro Ruch | 6 Jul 16:02 2009

AUTO: Sandro Ruch/namics/com is out of the office. (returning 14.07.2009)


I am out of the office until 14.07.2009.

I will respond to your message when I return.

Note: This is an automated response to your message  "What versions of
Windows does NTEventLogAppender support?" sent on 06.07.2009 13:36:26.

This is the only notification you will receive while this person is away.
Brett Randall | 6 Jul 21:11 2009
Picon

Re: What versions of Windows does NTEventLogAppender support?

Hi Mark,

Last time I faced the same question myself (within the last 6 months) I was
unable to find a pre-compiled 64-bit DLL for NTEventLogAppender.  JNI will
not load/link the 32-bit one from a 64-bit JVM.

I've started my own library bridging to java.util.logging or log4j, based on
HOWTOs I found on the net.  It's called wel4j (Windows Event Log for Java)
and is hosted here: http://wel4j.googlecode.com/ .  Unfortunately it is
currently lacking a working native Maven build for the DLL, but if you want
to go this route I should be able to provide one in a releasable form.

Best
Brett

On Mon, Jul 6, 2009 at 9:36 PM, Mark Anderson <mark <at> panonet.net> wrote:

> I have been unable to find a list of the versions of Windows that
> NTEventLogAppender is supported on. Could someone please supply such a
> list?
>
> I am specifically interested in whether Windows Server 2008 64 bit is
> supported.
>
> Thanks,
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe <at> logging.apache.org
(Continue reading)

Yang Zhang | 7 Jul 21:13 2009
Picon

Specifying non-root loggers in properties files

How do I specify a non-root logger in a Java properties file?  I current 
have the root logger showing output at INFO level and above, but I'm 
interested in debugging one particular class, so I'd like to allow 
DEBUG-level output for that class.  (I always use 
Logger.getLogger(Blah.class).)  I couldn't find any examples of this in 
the documentation or on Google.  Thanks in advance.
--

-- 
Yang Zhang
http://www.mit.edu/~y_z/
Wendal Chen | 8 Jul 01:51 2009
Picon

Re: Specifying non-root loggers in properties files

use this:

lg4j.logger.yourpackage.Blah = DEBUG

2009/7/8 Yang Zhang <yanghatespam <at> gmail.com>

> How do I specify a non-root logger in a Java properties file?  I current
> have the root logger showing output at INFO level and above, but I'm
> interested in debugging one particular class, so I'd like to allow
> DEBUG-level output for that class.  (I always use
> Logger.getLogger(Blah.class).)  I couldn't find any examples of this in the
> documentation or on Google.  Thanks in advance.
>  --
> Yang Zhang
> http://www.mit.edu/~y_z/ <http://www.mit.edu/%7Ey_z/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe <at> logging.apache.org
> For additional commands, e-mail: log4j-user-help <at> logging.apache.org
>
>
Hebert, Marc | 9 Jul 23:59 2009

log4j 1.2.15 source compilation problem

Hello.

I'm ultimately trying to debug a deadlock problem we're encountering that appears to be in log4j (1.2.15),
but for starters I'm aiming to recompile the log4j 1.2.15 source, and running into the problem below.  This
is occurring within a cygwin shell running on a windows PC.  Near as I can tell, the compile is referencing an
older version of ant, resulting in the unresolved method call. Thanks in advance for any help.

First, I should spell out some environment parameters:

$ mvn --version
Apache Maven 2.1.0 (r755702; 2009-03-18 12:10:27-0700)
Java version: 1.5.0_17
Java home: c:\Program Files\Java\jdk1.5.0_17\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

$ mvn package
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Log4j
[INFO]    task-segment: [package]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 7 resources
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[FATAL ERROR]
org.codehaus.plexus.component.configurator.BasicComponentConfigurator#configureComponent(...)
caused a lin
(Continue reading)

Brenner Rene | 10 Jul 10:20 2009
Picon

log4j reference time

Hello all

I understand, that log4j uses an absolute time and reference time based on the system time of the underlying
operating system.
Is there a way to set a reference time to the log4j appender which is different to the actual system time? On my
system I use
a reference time which is only valid within the JVM environment.

Thanks,
René

Roberto Simoni | 10 Jul 11:37 2009
Picon

DailyRollingFileAppender & RollingFileAppender after a rollover continues to write on previous file...

Hi to all. We use log4j in a big project for our customer on a 
linux/unix system (JBoss 4, JDK 1.5).
Every day, I see current time logs present in two log file... the 
current (<application_name>.log) and the previous log 
(<application_name>.log.<date_pattern> or 
<application_name>.log.<counter>) as the rollover operation hasn't 
stopped to write to the previous file.
We have only a log4j.xml file and a file appender configured. What I see 
is that when the problem occurs a lot of logs is in writing in that moment.
We have a batch operation at midnight, so with DailyRollingFileAppender 
the problem occurs everyday, instead with RollingFileAppender the 
problem occurs only if the rollover is made around midnight.

I have seen that rollover operation is *not* synchronized due to a 
"already synchronization on doAppend method" (as sad in 
RollingFileAppender class).
Are you confident on this behaviour?

Thanks in advance
Bye
Lucas Vickers | 12 Jul 02:01 2009
Picon

using a different log4j.properties file per classes directory

Hello,
Excuse my simple question as I am new to tomcat/log4j.
I have looked at the mailing list and did some googling but no luck.

What I would like to do is have my tomcat installation use one log file, and
then my own servlet use a different log file.

./common/classes/log4j.properties =

log4j.rootLogger=INFO, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${catalina.home}/logs/tomcat.log
log4j.appender.R.MaxFileSize=100MB
log4j.appender.R.MaxBackupIndex=50
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n

./webapps/servlets-examples/WEB-INF/classes/log4j.properties =

log4j.rootLogger=DEBUG, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${catalina.home}/logs/tabs.log
log4j.appender.R.MaxFileSize=10MB
log4j.appender.R.MaxBackupIndex=100
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n

Ideal result is that my class in /servlets-examples will be in DEBUG level
and will output to the "tabs.log"

(Continue reading)


Gmane