gmane.comp.jakarta.log4j.user

Re: log4j window size

Christian Grobmeier — 2012-05-10T07:50:56

On Thu, May 10, 2012 at 9:46 AM, Stadelmann Josef
<josef.stadelmann< at >axa-winterthur.ch> wrote:

+1 for configurable naming strategies - everybody to his taste.
Patches are welcome! :-)

AW: log4j window size

Stadelmann Josef — 2012-05-10T07:46:20

why not a different renaming schema where only one file, 
the current to be rolled over file has to be renamed?
Josef

-----Ursprüngliche Nachricht-----
Von: Curt Arnold [mailto:curt.arnld< at >gmail.com] Im Auftrag von Curt Arnold
Gesendet: Donnerstag, 10. Mai 2012 07:30
An: Log4J Users List
Betreff: Re: log4j window size

I believe the renaming time can become significant depending on the platform. Unless wrapped in an async appender, this can cause the rollover logic block the caller for an extended period of time.


On May 7, 2012, at 9:11 AM, aanjaneya shukla wrote:



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe< at >logging.apache.org
For additional commands, e-mail: log4j-user-help< at >logging.apache.org

Re: log4j window size

Curt Arnold — 2012-05-10T05:30:20

I believe the renaming time can become significant depending on the platform. Unless wrapped in an async appender, this can cause the rollover logic block the caller for an extended period of time.


On May 7, 2012, at 9:11 AM, aanjaneya shukla wrote:

Re: unable to set properties

Jacob Kjome — 2012-05-07T20:01:22

As is stated at the link I provided previously...

"These components are built and tested using Apache log4j 1.2.9 and supported 
for use with any later 1.2.x release."

According to this quote, Log4j-1.2.15 should be fine.  Regarding other runtime 
dependnecies, the dependencies report [1] lists only Log4j.  You should be 
good to go.  Try it.  If it fails, report back and we'll try to determine 
what's missing.


[1] http://logging.apache.org/log4j/companions/extras/dependencies.html

Jake

On Tue, 8 May 2012 00:21:54 +0530
 aanjaneya shukla <shuklaaanjaneya< at >gmail.com> wrote:

Re: unable to set properties

aanjaneya shukla — 2012-05-07T18:51:54

Can you please tell me what are runtime dependencies for the log4j-extras?
I see compile time dependency as log4j-1.2.16 but could not find anything
for compile time dependency. Will log4j-1.2.15 work for runtime.

Thanks


On Mon, May 7, 2012 at 8:36 PM, Jacob Kjome <hoju< at >visi.com> wrote:

Re: unable to set properties

Jacob Kjome — 2012-05-07T15:06:40

Do you have log4j-extras.jar [1] in the classpath along with log4j.jar?  If 
not, that's the problem.

[1] http://logging.apache.org/log4j/companions/extras/

Jake

On Mon, 7 May 2012 15:03:08 +0530
 aanjaneya shukla <shuklaaanjaneya< at >gmail.com> wrote:

Re: unable to set properties

Tushar Kapila — 2012-05-07T14:59:33

1. which version of log4j are you using
2. use the debug feature to analyze which file is being loaded
...http://jaitechwriteups.blogspot.in/2006/07/know-how-log4j-tries-to-configure.html
(same tip is there somewhere in the docs too have a look
http://logging.apache.org/log4j/1.2/manual.html search for
-Dlog4j.debug ... can make it -Dlog4j.debug=true in windows maybe that
is implied in unix)

On Mon, May 7, 2012 at 3:03 PM, aanjaneya shukla
<shuklaaanjaneya< at >gmail.com> wrote:

log4j window size

aanjaneya shukla — 2012-05-07T14:11:36

Hi,
Is there any specific reason for having a max index at 13 in log4j? Since
we can archive the log files with significant compression we can increase
this.
Thanks

unable to set properties

aanjaneya shukla — 2012-05-07T09:33:08

Hi,
I am using the below mentioned log4j.properties file in tomcat 6.0.35

log4j.appender.request=org.apache.log4j.rolling.RollingFileAppender
log4j.appender.request.Append=true
log4j.fileName=logs/test
log4j.appender.request.File=${log4j.fileName}.log
log4j.appender.request.RollingPolicy=org.apache.log4j.rolling.FixedWindowRollingPolicy
log4j.appender.request.RollingPolicy.FileNamePattern=${log4j.fileName}.%i.log.zip
log4j.appender.request.RollingPolicy.MinIndex=1
log4j.appender.request.RollingPolicy.MaxIndex=10

log4j.appender.request.TriggeringPolicy=org.apache.log4j.rolling.SizeBasedTriggeringPolicy
log4j.appender.request.TriggeringPolicy.MaxFileSize=10485760

log4j.appender.request.layout=org.apache.log4j.PatternLayout
log4j.appender.request.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L -
%m%n

log4j.rootLogger=info, request

But I get the following messages returned
log4j:WARN Failed to set property [rollingPolicy] to value
"org.apache.log4j.rolling.FixedWindowRollingPolicy".
log4j:WARN Failed to

Re: RootCategory and RootLogger

Jacob Kjome — 2012-05-01T14:58:09

Excellent idea for a project!

Category/Priority are deprecated in favor of Logger/Level.  I would suggest 
that any converter you create have an option to convert deprecated names to 
non-deprecated names.

Jake

On Tue, 1 May 2012 15:36:37 +0200
 "janinko.g" <janinko.g< at >gmail.com> wrote:

RootCategory and RootLogger

janinko.g — 2012-05-01T13:36:37

Hello,

we are making converter for log4j configuration (xml <-> properties)
[1]. It's school project but I hope it would be useful :)

My question is if there is difference between RootCategory and
RootLogger, or if we can just rename RootCategory to RootLogger.

Thanks

Honza Brázdil

[1]: https://github.com/janinko/Log4J-configuration-converter

Campfire Log4j Appender

Taner Diler — 2012-04-19T06:20:59

Hi

I've started the Campfire4j
<https://github.com/tanerdiler/Campfire4j>project. Campfire4j sends
log events to
Campfire <http://campfirenow.com/> Room.
Campfire is a 37 Signals <http://37signals.com> service.

Here is the project link https://github.com/tanerdiler/Campfire4j

Taner Diler

AW: forcing [root] logging - to a separate appender

Stadelmann Josef — 2012-04-16T08:36:20

do you understand that log4j loggers work in a hierarchy?

root
com
com.axa
com.axa.ws
com.axa.ws.spezpla
com.axa.ws.spezpla.transport

Now
com.axa.ws.spezpla.SpezplaService.java

would become a logger named com.axa.ws.spezpla.SpezplaService
and maybe at various levels in the hierarchy, you have loggers as well.

now you can add 
log4j.logger.com.axa.ws=INFO, TC_CONS, TC_ROLF, TC_FAP, TC_CHAINSAW
to block that bad or too fine grained logging events from 
com.axa.ws.spezpla.SpezplaService reach the root logger or any logger above com.axa.ws

by doing so you can intercept unwanted logging events on their way to the top root logger.

hope I got you right.
Josef

-----Ursprüngliche Nachricht-----
Von: Sean A. [mailto:seanga2< at >gmail.com] 
Gesendet: Samstag, 7. April 2012 03:23
An: Log4J Users List
Betreff: Re: forcing [root] logging - to a separate appender

On 04/03/2012 11:24 AM, BRUNO MELLONI wrote:
You could try implementing you own filter.  Have your class implement 
org.apache.log4j.spi.Filte

Re: Log4J doesn't work at all

ceki — 2012-04-12T10:06:38

[snip]




As the warning message above shows, 
selenium-server-standalone-2.20.0.jar contains an SLF4J binding. It also 
contains the classes of an *older* version of slf4j-api.jar. Which 
explains the NoSuchMethodError exception about 
org.slf4j.spi.LocationAwareLogger.log method.

Interestingly enough, selenium-server-standalone-2.21.0.jar released 
just a few hours ago does *not* bundle slf4j classes. Note: perhaps 
using a jar file which includes "standalone" in its name was the 
original error. (Disclaimer: I have never used selenium.)

Re: Log4J doesn't work at all

tommmmmm — 2012-04-12T08:57:11

I have just rewritten all selenium code to HtmlUnit code. That's it....
Works now.

I know I should write to Selenium (I did, but they are silent) and lcf4j
but after 25hours of me hugging 10 lines of code till blood and tears all
go out... no I rather go the easy way now. No more fighting. I just hope
HtmlUnit will do the job for me and that I will never have to use
selenium... that's it.

Re: Log4J doesn't work at all

Douglas E Wegscheid — 2012-04-11T21:22:25

woho! slf4j is in there! you have 2 copies of a slf4j binding loaded, one 
in the slf4j jar, one in the selenium jar. slf4j docs say it should use 
the first one found, which means slf should be binding to log4j. slf4j may 
be catching all the common-logging messages. 

You have a mess here: multiple versions of the same classes loading from 
different jars (httpclient, slf4j, commons logging). I wouldn't even 
hazard how to fix it with things in such disarray. Jacob was right: "it's 
usually a classpath problem". Eliminating the duplicate jars (if you are 
using slf4j, the only commons-logging jar you need is 
commons-logging-api). I don't know how to keep the slf4j configuration 
bundled into the selenium jar from  bunging up everything else. 

It's not HttpComponents that has the problem, and log4j is working just 
fine.  I'd take it to the slf4j list if you continue to have problems...

■ DOUGLAS E. WEGSCHEID // LEAD ENGINEER
(269) 923-5278 // Douglas_E_Wegscheid< at >whirlpool.com
"A wron

Re: Log4J doesn't work at all

Jacob Kjome — 2012-04-11T21:19:48

Selenium depends upon SLF4J.  You may recall that I mentioned SLF4J in a 
previous email.  In appears Selenium includes it's own SLF4J binding.  It 
seems rather silly to me that they would include this as part of their main 
library rather than as a separate, optional, jar.

I suggest you contact the Selenium developers and, possibly, the SLF4J 
developers to find a solution.

In any case, if you are going to have SLF4J in your classpath and want to use 
Log4j as the implementation, you should include the following in the 
classpath....

jcl-over-slf4j.jar
slf4j-api.jar
slf4j-log4j12.jar
log4j.jar

And get rid of any, and all, commons-logging jars.  The "jcl-over-slf4j.jar" 
contains the package/classes of commons-logging, except they are a 
re-implementation bound to SLF4J.


Jake


On Wed, 11 Apr 2012 19:55:20 +0200
 tommmmmm <tommmmmm< at >gmail.com> wrote:

Re: Log4J doesn't work at all

tommmmmm — 2012-04-11T17:55:20


I added/removed jars one by one.... of course it had to be the last one.
When I removed
/home/min/ucng/javaLibs/selenium-server-standalone-2.20.0.jar

It started to work. However... I need selenium - it's my main browser. So
when I added it back....
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/home/min/ucng/javaLibs/pbapi-full-1.4.0.91/lib/test/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/min/ucng/javaLibs/selenium-server-standalone-2.20.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.

Exception in thread "main" java.lang.NoSuchMethodError:
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
at
org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:99)
at
org.apache.http.impl.conn.SingleClientConnManager.getConnection(SingleClient

Re: Log4J doesn't work at all

tommmmmm — 2012-04-11T16:45:49

I used the old project I had in my Projects list. And it works there
flawlessly.

For easier readability here are the results:

Log4j configuration debug output in working project:
**Start of LogManager static initializer
*** configurationOptionStr=null
** End of LogManager static initializer
DEBUG [org.apache.log4j.PropertyConfigurator] Parsing for [root] with
value=[DEBUG, stdout].
DEBUG [org.apache.log4j.PropertyConfigurator] Level token is [DEBUG].
DEBUG [org.apache.log4j.PropertyConfigurator] Category root set to DEBUG.
DEBUG [org.apache.log4j.PropertyConfigurator] Parsing appender named
"stdout".
DEBUG [org.apache.log4j.PropertyConfigurator] Parsing layout options for
"stdout".
DEBUG [org.apache.log4j.config.PropertySetter] Setting property
[conversionPattern] to [%5p [%c] %m%n].
DEBUG [org.apache.log4j.PropertyConfigurator] End of parsing for "stdout".
DEBUG [org.apache.log4j.PropertyConfigurator] Parsed "stdout" options.
DEBUG [org.apache.log4j.PropertyConfigurator] Parsing for
[org.apache.http.wire]

Re: Log4J doesn't work at all

Douglas E Wegscheid — 2012-04-11T16:34:58

tommmmmm <tommmmmm< at >gmail.com> wrote on 04/11/2012 11:55:59 AM:


try making a new project with >>exactly<< what I posted. Then we'll know 
if it's your environment, or that specific project....

Re: Log4J doesn't work at all

Douglas E Wegscheid — 2012-04-11T16:32:59

tommmmmm <tommmmmm< at >gmail.com> wrote on 04/11/2012 11:55:59 AM:


Have you tried creating a new project with just these jars and just the 
Test1.java and log4j.properties and the jars I listed? If so, I'm stumped. 
If not, try it.

You *must* have something different than I do (something else on the 
classpath), but I can't think of what it is. I've made it work with both 
Eclipse Indigo and Netbeans 6.9.1.