Re: [ANNOUNCEMENT] Welcome Matt Sicker

Congratulations, Matt! Welcome aboard! Nick On Mar 3, 2014, at 8:20 AM, Remko Popma wrote: > Welcome Matt! > > > On Mon, Mar 3, 2014 at 10:57 PM, Matt Sicker wrote: > >> Thanks guys! I'm looking forward to making more direct contributions now! >> In fact, cleaning up some unit tests was some

[ANNOUNCEMENT] Apache Log4j 2.0-rc1 released

nosql.mongo package to org.apache.logging.log4j.core.appender.db.nosql.mongodb. o Renamed the org.apache.logging.log4j.core.appender.db.nosql.couch package to org.apache.logging.log4j.core.appender.db.nosql.couchdb. o LOG4J2-507: Space Level numbers by 100 instead of 1. o LOG4J2-41: Add support for custom logging levels. Thanks to Nick

Re: log4j2 and Hibernate

; > To my knowledge, Hibernate does not use JBoss logging until version 4.x and > we're using Hibernate 3.x, so JBoss logging is not on our classpath. Am I > mistaken? > > Michael > ____ > From: Nick Williams [nicho...@nicholaswilli

Re: log4j2 and Hibernate

Michael, what version of JBoss Logging is on your classpath? N On Feb 14, 2014, at 11:22 AM, Michael Friedmann wrote: > We are using log4j2 and Hibernate (3.6.0.Final) wired through Spring > (HibernateJpaVendorAdapter). Whenever 'showSql' is set to true, this seems > to cause the application

Re: Servlet 2.5 compatibility - Log4jServletContainerInitializer

This has been fixed as of RC1. Thanks, Nick On Jan 21, 2014, at 10:47 AM, Dave Levitt wrote: > Did a bit of research on Jira - this is issue > LOG4J2-359 > > > On Tue, Jan 21, 2014 at 11:15 AM, Dave Levitt wrote: > >> I'm trying to add log4j

Re: Modify how log4J takes location from the stack

Avi, there is a simple solution to this: What other components do (the tag library, the Commons adapter, and the JBoss Logging project) is, when they create their wrapping logger, they make sure the Log4j logger actually extends org.apache.logging.log4j.spi.AbstractLogger. That's part of the co

Re: Using Spring-managed DataSource (or other Spring beans) in log4j2 configuration

On Sep 13, 2013, at 10:26 AM, Francesco Chicchiriccò wrote: > Hi all, > I am trying to configure a JDBCAppender in log4j 2.0-beta9-SNAPSHOT, with a > pre-existing DataSource managed via Spring; such DataSource is used by the > rest of Syncope. > > I have tried, without success. to provide a cu

Re: javadoc

This has been fixed. When the next version of Log4j releases and the site updates, there will be prominent Javadoc/API documentation links directly at the top of the left-hand menu. Nick On Aug 26, 2013, at 4:18 PM, Eric Schwarzenbach wrote: > I find myself unable to find the log4j2 javadoc. I

Re: Log4j2: Column casting in JDBCAppender

ically enough that a simple, generic prepared statement can handle 99% of cases correctly. Nick On Aug 22, 2013, at 5:13 PM, Scott Deboy wrote: > That doesn't look like much work. Particularly since you could lift > what's provided and just extend it to support the one-off we

Re: Log4j2 Tag Library + Tomcat 7

Tomcat 7 introduced a feature to skip the scanning of certain JARs to improve JSP engine initialization. This feature including a default setting to skip many popular JARs that were known not to contain TLDs or SCIs. Unfortunately, this included a log4j*.jar default exclusion, meaning the Log4j

Re: Log4j2: Column casting in JDBCAppender

Yes, I mean like that. I want to avoid something like that. N On Aug 22, 2013, at 4:59 PM, Scott Deboy wrote: > You mean like: > http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/log4j/db/dialect/package-summary.html > > Scott > > On 8/22/13, Nick Willi

Re: Log4j2: Column casting in JDBCAppender

IMO, this is a bug in the PGSQL JDBC driver and not something that Log4j can easily (or should) address. For a detailed discussion, see the PGSQL thread about casting text to PGSQL enums [1]. The problem lies in PGSQL's type handling. With PGSQL, MySQL, and any other database type that supports

Re: Error in JDBCAppender when used with tomcat6 and log4j2

Please paste your log4j2.xml/json config file. All of the information you have given is helpful, but it's not quite enough. Nick On Jul 28, 2013, at 9:44 AM, gokulvsmail wrote: > hi, > when i am trying to use the jdbcappender..am getting the error as > No suitable driver found in the Tomcat s

Re: Connection leak with JDBCAppender

I can, yes. Nick On Jul 26, 2013, at 5:20 PM, Gary Gregory wrote: > The approach currently implemented sounds good to me. > > Nick, can you document the appender's behavior to avoid further confusion? > > Thank you, > Gary > > On Jul 26, 2013, at 14:32, Nick

Re: Connection leak with JDBCAppender

Yes, this is the intended behavior, and a false-positive on the part of the leak detection. If the JDBCAppender has to open and close a connection and prepare the same statement for each logging event (even if it just has to borrow a connection from a pool and prepare the same statement for eac

Re: Logging only particular users

On Jul 24, 2013, at 9:35 AM, Michael Wechner wrote: > Hi > > We are using log4j for many years now for our open source CMS www.yanel.org > and it works really great > and I really would like to thank everyone who contributed to log4j. > > Over the years we are experiencing that more and more p

Re: Log4j2: Programmatically setting log4j2 log level

We do the _exact same thing_ in our apps that use Log4j 1. Being able to do this is crucial to us. Being able to do this using the API is ideal and obviously preferred so that the Core can be a runtime dependency, but as long as we can do it one way or another we're ok. Nick On Jul 22, 2013, a

Re: Log4j 2 - Not implemented method used in JDBC appender

Actually I need to correct myself: On Jul 16, 2013, at 7:57 AM, Nick Williams wrote: > M., > > setNString() is part of JDBC 4.0, which came with Java 6. It sounds like you > are using the postgresql-x.x-.jdbc3.jar JDBC driver, which was written > for Java 4. Please down

Re: Log4j 2 - Not implemented method used in JDBC appender

M., setNString() is part of JDBC 4.0, which came with Java 6. It sounds like you are using the postgresql-x.x-.jdbc3.jar JDBC driver, which was written for Java 4. Please download the latest JDBC driver postgresql-9.2-1003.jdbc4.jar (http://jdbc.postgresql.org/download/postgresql-9.2-1003.j

Re: New to mailing list, inquiring if there is a release date for 2.0-beta 8?

A topic was just started about this on the developers' list. You're free to subscribe to that list as well in order to monitor the decisions, or you can view the topic in the archives here: http://marc.info/?l=log4j-dev&m=137279002901510&w=2 The most recent message suggested Monday for the vote

Re: better way to handle objects in messages?

Check out Log4j 2. It has a significantly expanded API that does just what you're looking for. http://logging.apache.org/log4j/2.x/ Nick On Jun 9, 2013, at 4:36 PM, Ray Kiddy wrote: > > I have done something and can see where it might be generalized to help other > users of log4j. Has this i

Re: how to configure log4j (1.2) in JBoss 6?

Piers, IIRC, JBoss 6, by default, prefers the parent class loaders over child class loaders. This means that, when a class path resource is referenced, it is first searched for in the server class loaders and _then_ in the web application class loader. This is similar to the default behavior in

Re: Programmatically setting log4j2 log level

I agree, Scott. On May 18, 2013, at 11:11 AM, Scott Deboy wrote: > From looking at this, seems like config.getRootLoggerConfig() would be a > better name. > On May 17, 2013 10:40 PM, "Ralph Goers" wrote: > >> No, the X Logger does not inherit its level from the root Logger. It >> inherits its l

Re: log4cxx - reaching out for interested developers

Lacking any responses, I'll chime in: I didn't know log4cxx existed. The only Cxx code I write is Java+Native. With that said, now that I know it exists, I will investigate using it in my native code; I'm not sure. I'd love to try to help some, but I simply don't have time right now. I'm in th

Re: Three things I couldn't find on the Log4j 2 Site

On Mar 28, 2013, at 5:58 PM, Ralph Goers wrote: > > On Mar 28, 2013, at 7:53 AM, Gary Gregory wrote: > >> On Sun, Mar 24, 2013 at 4:08 AM, Nick Williams < >> nicho...@nicholaswilliams.net> wrote: >> >>> I've been a Log4j 1 user for years and

Re: Three things I couldn't find on the Log4j 2 Site

the same for each component. > > 4a) I would actually recommend SLF4J over Commons Logging if the application > is looking for an independent logging API. > b) Again, many applications want an independent API. That is why they choose > Commons Logging or SLF4J. As you noted,

Three things I couldn't find on the Log4j 2 Site

I've been a Log4j 1 user for years and I love it. I'm currently writing a book for Java EE 7 + Spring Framework 4 development and one of my chapters is on application logging. I was going to cover Log4j 1 and then I stumbled upon Log4j 2. It looks like a serious improvement over Log4j 1 and I'm