Re: JSR47 vs. log4j (take two)

2001-07-31 Thread Yuji Kumasaka
There is 2 typo. > The way the two APIs name their componets may vary but otherwise their degree of >resemblance is quite scary. > The way the two APIs name their components may vary but otherwise their degree of >resemblance is quite scary. > My gratitude goes to Jason Hunter for arranging th

Re: DailyRollingFileAppender

2001-07-31 Thread Kevin Steppe
I've made that suggestion myself. In setFile() of CompositeRollingAppender I added: if (!staticLogFileName) scheduledFilename = fileName = fileName.trim() + sdf.format(now); I believe that adding the assignment line to the DailyRollingFileAppender will do the trick though I haven't test

DailyRollingFileAppender

2001-07-31 Thread ONG CHIN HUI, C21PgM
>Hi all, > In our environment, we have a lot of processes that need to log >events to files on a daily or hourly basis. The DailyRollingFileAppender is appropriate for such logging. However, the behavior of naming the log file may cause some problems. Below is extracted from the javadoc of DailyR

Re: JSR47 vs. log4j (take two)

2001-07-31 Thread Kent Yang
I am encourage by the latest developments. However, I wonder why Sun didn't just specify an interface and allow different logging backends to be plug-in. That way developers can decide what implementation they want to use. Sun did this with a lot of their APIs (Security, Sockets, etc...) Can t

JSR47 vs. log4j (take two)

2001-07-31 Thread Ceki Gülcü
For the latest developments on the JSR47 front you might want to read: http://jakarta.apache.org/log4j/docs/critique2.html -- Ceki Gülcü - http://qos.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,

Re: Upgrading to 1.1.3 and JMS

2001-07-31 Thread Alex X Benke
Ceki, I believe you are right. I am trying to wrap an exception with a new custom exception, and I believe this is where the error is occuring. I can get basic logging to work fine over the JMS bus. I will look into this more tomorrow, and keep you up to date. Thanks for the help so far... -A

FQCN Category.log() question

2001-07-31 Thread Scot Hale
I currently converted the logging in my webapplication to use log4j 1.1.3 via a wrapper class.  So everything in the application, various packages, log via the function call in one class:       Category.getRoot().log(String callerFQCN, Priority priority, Object message, Throwable t)   I am

Re: Upgrading to 1.1.3 and JMS

2001-07-31 Thread Ceki Gülcü
Alex, Vow. Although I do not think it is a log4j problem, I'll double check and let you know. Regards, Ceki At 15:52 31.07.2001 -0400, you wrote: >I checked my classpath to make sure the old jar is out and have changed my code >that that I'm publishing a message and then pulling it down in the

Re: Upgrading to 1.1.3 and JMS

2001-07-31 Thread Alex X Benke
I checked my classpath to make sure the old jar is out and have changed my code that that I'm publishing a message and then pulling it down in the same method (1 process) and it still gives the same error... anyone have other ideas? thanks Alex [EMAIL PROTECTED] on 07/31/2001 12:55:33 PM Pl

Re: Upgrading to 1.1.3 and JMS

2001-07-31 Thread Ceki Gülcü
Alex, You probably have different versions on log4j running on the client side and the server side. HTH, Ceki At 10:30 31.07.2001 -0400, Alex X Benke wrote: >I've just upgraded to 1.1.3 and for some reason I'm having a problem with my JMS >publish/subscribe. The publish works fine, but when I

RE: Upgrading to 1.1.3 and JMS

2001-07-31 Thread Chip Morgan
just a guess, but are you running two separate processes - 1 to pub, 1 to sub? could your sub process still have the old jar in the classpath? On Tuesday, July 31, 2001 9:30 AM, Alex X Benke [SMTP:[EMAIL PROTECTED]] wrote: > I've just upgraded to 1.1.3 and for some reason I'm having a problem

RE: How to use xml configuration files

2001-07-31 Thread Johnson, Clay
> name. Could someone please suggest as to why this is not > working. The ROLLINGFILE.out never gets written to, only the > console and the FILE.out are used. > Just a hunch, but I've never tried setting this to 0.

Upgrading to 1.1.3 and JMS

2001-07-31 Thread Alex X Benke
I've just upgraded to 1.1.3 and for some reason I'm having a problem with my JMS publish/subscribe. The publish works fine, but when I pull the message off the bus (type LoggingEvent) it gives the following message: -- log4j:WARN Priority deserialization failed, rever

Re: disabling categories (was: channels in Log4j)

2001-07-31 Thread Eugene Katz
Am I missing something here? Can't you effectively turn off a category by not assigning it any appenders (and additivity=false)? I do admit that I'm very new to Log4j, so I must be missing something. --Eugene Ceki Gülcü wrote: > > As you have mentioned in your initial message you can turn o

Re: disabling categories (was: channels in Log4j)

2001-07-31 Thread Craig_Reichenbach
In a shipping application I wouldn't want to turn off FATAL messages. For "tracefile" Categories during development it might be conceivable to isolate certain Categories by turning others off. The notion of an on off switch for categories is appealing. I'm not sure to be honest. Why will log4

Request for java source code for testing log4J

2001-07-31 Thread Yee Kai Lai
hi can I have the a copy of the above to test the following function :debug,warn,info,error,fatal ? TIA Regards, Kai *Disclaimer* This mail and any accompanying documents contain confidential information intended for a specific individual and purpose. This information is private and prot