Re: Null pointer error when writing MapMessage key's value to database

2017-10-10 Thread gaurav9...@gmail.com
On 2017-10-11 04:29, Gary Gregory wrote: > On Tue, Oct 10, 2017 at 12:42 AM, gaurav9...@gmail.com > wrote: > > > > > > > On 2017-10-06 20:32, Gary Gregory wrote: > > > Hi, > > > > > > I think you will get better help if

Re: How to store custom-message variable values to the database table's column using log4j2

2017-10-10 Thread gaurav9...@gmail.com
On 2017-10-11 00:49, Matt Sicker wrote: > Are you using ColumnMapping? See < > https://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender>. > > See < > https://github.com/apache/logging-log4j2/blob/master/log4j-nosql/src/test/resources/CassandraAppenderTest.xml>

Re: Null pointer error when writing MapMessage key's value to database

2017-10-10 Thread Gary Gregory
On Tue, Oct 10, 2017 at 12:42 AM, gaurav9...@gmail.com wrote: > > > On 2017-10-06 20:32, Gary Gregory wrote: > > Hi, > > > > I think you will get better help if you provide a reproducible JUnit test > > case or program, on GitHub for example. > > >

Re: How to store custom-message variable values to the database table's column using log4j2

2017-10-10 Thread Matt Sicker
Are you using ColumnMapping? See < https://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender>. See < https://github.com/apache/logging-log4j2/blob/master/log4j-nosql/src/test/resources/CassandraAppenderTest.xml> for example usage (even though that uses the CassandraAppender, the

Re: Version 1.2 - send one logger to a separate file

2017-10-10 Thread Shawn Heisey
On 10/9/2017 5:56 PM, Remko Popma wrote: > Log4j 1.x was declared End of Life in August 2015 > (https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces). > > Also, Log4j 1.2 is known to be broken on Java 9 >

Fwd: How to store custom-message variable values to the database table's column using log4j2

2017-10-10 Thread Matt Sicker
-- Forwarded message -- From: Gaurav Deshpande Date: 10 October 2017 at 09:02 Subject: How to store custom-message variable values to the database table's column using log4j2 To: "mattsic...@apache.org" , "rgo...@apache.org" <

How to store custom-message variable values to the database table's column using log4j2

2017-10-10 Thread gaurav9...@gmail.com
Hi Log4j2 users, I've created custom-message implementing log4j2's 'message' interface like following tutorial https://logging.apache.org/log4j/2.x/manual/messages.html I've defined JDBCAppender in lo4j2.xml which writes values from above message to database table. I've tried using

Re: Upgrade from 2.5 to 2.9.0 and Logstash

2017-10-10 Thread Gary Gregory
You might want to post your config and the precise message along with any stack trace. You can also set status="DEBUG" on the Configuration element in the config file. Gary On Tue, Oct 10, 2017 at 12:54 AM, Pietro Galassi wrote: > Hi, > > i've just upgrated log4j from

Re: How to add log level for a specific package in log4j2?

2017-10-10 Thread Asma Zinneera Jabir
You can add it as below. loggers = org.apache.parquet logger.org.apache.parquet.name = org.apache.parquet logger.org.apache.parquet.level = ERROR If you need to add more loggers, add it to the loggers separated by a comma and add two more lines as above to specify the name and level. On Fri,

Re: Programmatically added loggers lost due to automatic reconfiguration

2017-10-10 Thread Michael Heinen
Thanks Gary! That was exactly what I was looking for. Michael Am 06.10.2017 um 17:09 schrieb Gary Gregory: Hi Michael, How about using org.apache.logging.log4j.core.config.Configuration.addListener(ConfigurationListener) ? Gary On Fri, Sep 29, 2017 at 6:30 AM, Michael Heinen

Upgrade from 2.5 to 2.9.0 and Logstash

2017-10-10 Thread Pietro Galassi
Hi, i've just upgrated log4j from 2.5 to 2.9.0 but after the upgrade i'm not able to send logs to logstash. Either while starting up now the application says that it cant find the Async logger.

Re: Null pointer error when writing MapMessage key's value to database

2017-10-10 Thread gaurav9...@gmail.com
On 2017-10-06 20:32, Gary Gregory wrote: > Hi, > > I think you will get better help if you provide a reproducible JUnit test > case or program, on GitHub for example. > > Whenever you mention an Error or Exception, you should copy it in your > message. > > Gary > >