Please do NOT file a JIRA. One already exists for this:
https://issues.apache.org/jira/browse/LOG4J2-322
On Mon, Jul 29, 2013 at 9:36 AM, Remko Popma wrote:
> Federico,
>
> Thanks for the report! Would you mind raising a Jira ticket with some
> environment details and if possible steps to reprod
I can live with having to use the Core directly to change logger
levels, as opposed to using the API. But your solution of cloning,
changing, and replacing the configuration seems extremely heavy and
excessive for merely changing the level for a single logger. There are
a lot of other things that h
You can certainly implement your own appender. Reading the Log4j
documentation and perusing the source code should help you get started. You
cannot, however, create a custom implementation of inserting messages into
the database. If you have a suggestion of how the JDBC appender could be
improved,
There won't ALWAYS be a problem, but there will be performance concerns and
there could SOMETIMES be a problem. Since your columns are non-Unicode,
PostgreSQL (either the database engine or the JDBC driver) will convert the
Unicode Strings to whatever character set your columns are in when it
inser
