Re: [jira] [Created] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Ralph Goers
I think it was probably renamed. Sent from my iPad > On May 5, 2014, at 7:40 PM, Remko Popma wrote: > > Sorry I didn't understand your message Matt. > If your message is meant for Bryan, could you add a comment to the JIRA > ticket? I doubt he is on this list. Or is JIRA bridge something that

Re: [jira] [Created] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Remko Popma
Sorry I didn't understand your message Matt. If your message is meant for Bryan, could you add a comment to the JIRA ticket? I doubt he is on this list. Or is JIRA bridge something that automatically creates a JIRA comment when you reply to an email? Which class produces the "Unable to locate Serv

[jira] [Closed] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Bryan Hsueh (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Hsueh closed LOG4J2-628. -- > Cannot set log4j.Clock with Async appender > -- > >

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990093#comment-13990093 ] Remko Popma commented on LOG4J2-628: Bryan, good to hear that. About the error, we are

Re: [jira] [Created] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Matt Sicker
JIRA bridge still isn't set up right? Anyway, I fixed that error message the other day. I changed it to info IIRC as it's not super relevant other than to mention you can't use the WebLookup plugin. On Monday, 5 May 2014, Bryan Hsueh (JIRA) wrote: > > [ > https://issues.apache.org/jira/brows

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Ralph Goers
If your intention is to contribute it to the ASF then check out log4j2 and add the new classes into the NoSQL project. If you are intending to keep it for yourself then create a standalone project that has dependencies on log4j-nosql, log4j-core and log4j-api and make sure you are using package

AW: Splitting off NoSQL to its own module.

2014-05-05 Thread lo...@markus-klose.de
I meant it the other way around. Is it possible to develop additional nosql stuff in an external project? - Reply message - Von: "Ralph Goers" An: "Log4J Developers List" Betreff: Splitting off NoSQL to its own module. Datum: Mo., Mai 5, 2014 19:12 If you are trying to add something to

AW: Splitting off NoSQL to its own module.

2014-05-05 Thread lo...@markus-klose.de
Sry for my stupid questions :)...I will check my project again - Reply message - Von: "Matt Sicker" An: "Log4J Developers List" Betreff: Splitting off NoSQL to its own module. Datum: Mo., Mai 5, 2014 18:51 You just need log4j-core as a dependency when you compile. By default, it will i

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-05-05 Thread Bryan Hsueh (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989899#comment-13989899 ] Bryan Hsueh commented on LOG4J2-628: Tested, and works, thanks. I see this message lo

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Ralph Goers
If you are trying to add something to the log4j nosql package then it should be part of that project, not a separate project. Ralph On May 5, 2014, at 9:49 AM, lo...@markus-klose.de wrote: > Do I understand the process right? At compile time of log4j-nosql all nosql > based appender must be k

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Matt Sicker
You just need log4j-core as a dependency when you compile. By default, it will invoke the plugin processor to generate that .dat file. On 5 May 2014 11:49, lo...@markus-klose.de wrote: > Do I understand the process right? At compile time of log4j-nosql all > nosql based appender must be known?

AW: Splitting off NoSQL to its own module.

2014-05-05 Thread lo...@markus-klose.de
Do I understand the process right? At compile time of log4j-nosql all nosql based appender must be known? Does it mean that I never could implement a new appender if I do not have the sources? - Reply message - Von: "Matt Sicker" An: "Log4J Developers List" , "Markus Klose" Betreff:

AW: Splitting off NoSQL to its own module.

2014-05-05 Thread lo...@markus-klose.de
I added the new module to my pom and I refactored the import statements in the solr appender classes. Otherwise nothing would compile. For me it looks like that all nosql appender plugins are now unknown. At least if you are using the xml configuration. - Reply message - Von: "Ralph Goer

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Ralph Goers
Do you have the new nosql jar in your classpath? Ralph On May 5, 2014, at 8:15 AM, Markus Klose wrote: > Hi, > > since you moved the nosql appender into a separate module some of my other > test are failing. > > I have a test that reads a log4j.xml, getting a specific logger and getting

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Matt Sicker
You are adding log4j-nosql to your deployment or classpath, right? When log4j-nosql is compiled, the Log4j2plugins.dat file is created by an annotation processor. In a typical environment, the classpath is scanned for all the resource files with the correct name and path. Are you getting any releva

Re: Splitting off NoSQL to its own module.

2014-05-05 Thread Markus Klose
Hi, since you moved the nosql appender into a separate module some of my other test are failing. I have a test that reads a log4j.xml, getting a specific logger and getting all appenders of that specific logger. but now this test does not have any (nosql) appender anymore in my output i have se

[jira] [Resolved] (LOG4J2-566) Configure RollingRandomAccessFileAppender buffer size

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-566. Resolution: Fixed Fixed in revision 1592539. Please verify and close. > Configure RollingRandomAcc

[jira] [Commented] (LOG4J2-537) application does not end.

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989512#comment-13989512 ] Remko Popma commented on LOG4J2-537: Moonumi, Gleb, Is this still a problem? > applic

[jira] [Resolved] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-520. Resolution: Fixed Fix Version/s: 2.0-rc2 Fixed in revision 1592522. Please verify and close.

[jira] [Commented] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989463#comment-13989463 ] Remko Popma commented on LOG4J2-520: I think I got it. It took a bit of debugging, but

[jira] [Commented] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989407#comment-13989407 ] Remko Popma commented on LOG4J2-520: I revisited the fix for LOG4J2-392 and confirmed

[jira] [Commented] (LOG4J2-520) RollingRandomAccessFile with Async Appender skip logs

2014-05-05 Thread Andre Bogus (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989396#comment-13989396 ] Andre Bogus commented on LOG4J2-520: I see on 392 that you have pushed a fix, I'm in t

[jira] [Resolved] (LOG4J2-392) Intermittent errors with appenders

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-392. Resolution: Fixed Fix Version/s: (was: 2.0-rc1) 2.1

[jira] [Closed] (LOG4J2-521) RollingRandomAccessFile + Async Appender skip logs sometimes (while logging into same file and while switching to another log file)

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-521. -- Resolution: Duplicate No reaction from the user, closing this issue as a duplicate of LOG4J2-520. Plea

[jira] [Reopened] (LOG4J2-392) Intermittent errors with appenders

2014-05-05 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-392: Re-opening as the current fix may result in dropped events in case of slow appenders (LOG4J2-520). >