Hello,
I currently work for a project which involves server side
logging of client requests.
Clients are uniquely identified by a client id.
Our customer demands different logging 'coverage' depending
on the client id:
client c1:
com --- mycompany --- util
[ERROR]
Thomas,
Off the top of my head, you could log everything with NDC then take logs
from the main log based on user id and the level. This removes the
complexity to your text parser, which could run as a separate application
watching the log files, but won't appeal to your client if they want to
Hmm, thanks, haven't seen anything about NDC before, but
now I'm wiser.
Still, it doesn't really solve the problem nicely. I
just created a prototype for my client-id restrictions and
it seems to work well.
Most likely I will go for my approach, however any comments
would be *very*
Hello,
I am using DailyRollingFileAppender to split my log files every day. Is it
possible to copy the file in another location once it has been splitted. More
explicity, if I have a log into /var/log/myapp/mylogs.log and it's splitted I
would like that mylogs.log.2002.04.24 go into
Hi,
Thanks for the response to my problem of the object is not assignable message. I
still have the problem though. From reviewing what Ceki said I have looked at my
classpath for my given application simple application.
C:\dev\JDK\jdk1.3.1_04\\bin\javaw -classpath
Howdy,
I don't think that's part of log4j's job. I'd be surprised it if were possible to do,
using log4j only. However, it would be easy to write a shell script to copy all files
except mylogs.log to the backup directory every day.
Yoav Shapira
Millennium ChemInformatics
-Original
Hi,
Unfortunately I don't know of any USB devices of the kind you mentioned, in fact the
USB suggestion was just something the occoured to me while reading your question. I
think you need to outline more regarding the type of attacks you are trying to protect
yourself from.
HTH,
Dotan
Hi all:
Can you limit the amount of files created by DailyRollingFileAppender? I
have it set up to create a new one each day but I don't want it to exceed
10 files. I know that the J2SE 1.4 logging package allows this - does
log4j offer this ability as well?
Thanks
--
To unsubscribe,
from the DOCUMENTATION of RollingFileAppender:
public void setMaxBackupIndex(int maxBackups)
Set the maximum number of backup files to keep around.
The MaxBackupIndex option determines how many backup files are kept
before the oldest is erased. This option takes a positive integer
value. If
Reg.
I remain convinced that the error is due to duplicate log4j.jar
setup. Here is a modified log4j version that is designed to give more
information on the reasons of the failure. Here it is:
http://qos.ch/log4j-1.2.6.jar
Can you please try it and report back?
At 10:14 23.07.2002 -0300,
Hi,
I have a problem regarding JMSAppender
I have a client program issuing a
log.debug(logBean)
where logBean is a instance of my own class LogBean (it's Serializable).
I'm using a MDB to receive this log message.
I'm able to get the LoggingEvent in the MDB, by
RollingFileAppender creates new logs when a size limit is reached. I want
to keep writing to the file regardless of size for the whole day, hence the
use of DailyRollingFileAppender.
RollingFileAppender rfa = new ...;
rfa.setMaximumFileSize(Long.MAX_VALUE);
I guess 2^63 - 1 bytes is enough? ;)
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 23. Juli 2002 17:37
An: Log4J Users List
Betreff: Re: AW: Limit for
Please could someone tell me if they have a working solution on how to
log using log4J in an EJB server.
Is the conclusion to use JBoss's own logging?
Thanks
Larry
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Larry,
The question is somewhat ambiguous because, as far as I know, JBoss
itself uses log4j for its own logging. Can you please clarify your
question?
At 17:48 23.07.2002 +0200, Larry wrote:
Please could someone tell me if they have a working solution on how to
log using log4J in an EJB
The reason for this exception is because log4j transforms the message
object into String before serialization, i.e. transmission on the
wire. This precautionary step avoids the serialization of potentially
very large message objects. Moreover, the advantage of serializing
message objects remains
We use Log4j in jboss without any incident--until recently.
we just copy our log4j.properties into our conf directory:
c:/projects/devtools/JBoss-2.4.6_Tomcat-4.0.3/jboss/conf/our-app
The problem arose (see my post from yesterday) when I attempted to use a
custom renderer. Since Jboss
Hello All,
We have the following requirements. We have a table called logMessage
in Oracle.
Fields in the table are
Emp_id -- Char data type
Session_id -- Char data type
Emp_name -- Char data type
Transaction_type-- Char data type
Transaction_timestamp -- Date data
Hello,
We are moving from Log4J version 1.1.3 to 1.2.5. I want to disable Level for a
particular Logger. In the old version we could get the Hierarchy object for a
Category(Logger in new release) and then call disable , to disable a Priority (Level
in new relase) for a particular
LogEvents don't have fields for those items, and the JDBCAppender logs
LogEvent objects. So you'll have to do some coding.
A couple options off the top of my hand:
1) extend PatternLayout with conversion characters for all those things
2) override getLogStatement(...) in JDBCAppender.
3)
20 matches
Mail list logo