[jira] [Closed] (LOG4J2-1581) Warning should not display stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1581. --- Resolution: Fixed Fixed in master in commit 92b26b4. > Warning should not display stacktr

[jira] [Updated] (LOG4J2-1581) Warning should not display stacktrace

runtime-input-lookup-class-is-not-available-because-this-jre-does-not-suppor This warning does not need to print the full stacktrace: {noformat} 2016-09-12 12:01:26,124 main WARN JMX runtime input lookup class is not available because this JRE does not support JMX. JMX lookups will not be a

[jira] [Updated] (LOG4J2-1581) Warning should not display stacktrace

-not-available-because-this-jre-does-not-suppor This warning does not need to print the full stacktrace: {noformat} 2016-09-12 12:01:26,124 main WARN JMX runtime input lookup class is not available because this JRE does not support JMX. JMX lookups will not be available, continuing configuration

[jira] [Updated] (LOG4J2-1581) Warning should not display stacktrace

-not-available-because-this-jre-does-not-suppor This warning does not need to print the full stacktrace: {noformat} 2016-09-12 12:01:26,124 main WARN JMX runtime input lookup class is not available because this JRE does not support JMX. JMX lookups will not be available, continuing configuration

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

ctly you want to traverse the LoggerConfigs as those are where the actual filters and appender references reside. Loggers do contain the log lovel copied from their LoggerConfig, but that is a performance optimization. > Logger.getParent gives warning about MessageFactory m

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

see [~shangdi]'s point that simply calling {{logger.getParent()}} should not result in a warning. The suggested fix is one idea that may help, but note that this fix will only make the warnings go away if the parent logger uses the default message factory. This is because of the way {{getLogg

[jira] [Comment Edited] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

ccording to Log4j 2 architecture, am I supposed to be using LoggerConfig for parent traversal instead? As for the warning, I think it somewhat makes sense in the context of context.getLogger(name, messageFactory) alone, the problem here is that we are trying to overload this signature with 2 things: get OR

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

upport to SimpleLogger in general at that point. > Logger.getParent gives warning about MessageFactory mismatch > > > Key: LOG4J2-1585 > URL: https://issues.apache.org/jira/browse/LOG4J2-15

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

ng LoggerConfig for parent traversal instead? As for the warning, I think it somewhat makes sense in the context of context.getLogger(name, messageFactory) alone, the problem here is that we are trying to overload this signature with 2 things: get OR create. In the get case where the logger alread

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

y changes until I understand the use case better... > Logger.getParent gives warning about MessageFactory mismatch > > > Key: LOG4J2-1585 > URL: https://issues.apache.org

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

s to the StatusLogger in the configuration? Seems like too much... Or change that message from WARN to INFO? Or... what else? > Logger.getParent gives warning about MessageFactory mismatch > > >

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492920#comment-15492920 ] Remko Popma commented on LOG4J2-1585: - The warning can be useful for some peopl

[jira] [Updated] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1585: - Description: Hi I just noticed a lot of warning spam in my log like this: 2016-09-15 14:59

[jira] [Created] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

Di Shang created LOG4J2-1585: Summary: Logger.getParent gives warning about MessageFactory mismatch Key: LOG4J2-1585 URL: https://issues.apache.org/jira/browse/LOG4J2-1585 Project: Log4j 2

[jira] [Closed] (LOG4J2-1582) Warning should not display stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1582. --- Resolution: Fixed Fixed the other place too in commit f95c90b. > Warning should not disp

[jira] [Reopened] (LOG4J2-1582) Warning should not display stacktrace

other one also. > Warning should not display stacktrace > - > > Key: LOG4J2-1582 > URL: https://issues.apache.org/jira/browse/LOG4J2-1582 > Project: Log4j 2 > Issue Type: Improvement

[jira] [Closed] (LOG4J2-1582) Warning should not display stacktrace

[ https://issues.apache.org/jira/browse/LOG4J2-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1582. --- Resolution: Fixed Fixed in master in commit 01cc155. > Warning should not display stacktr

[jira] [Created] (LOG4J2-1582) Warning should not display stacktrace

Remko Popma created LOG4J2-1582: --- Summary: Warning should not display stacktrace Key: LOG4J2-1582 URL: https://issues.apache.org/jira/browse/LOG4J2-1582 Project: Log4j 2 Issue Type

[jira] [Created] (LOG4J2-1581) Warning should not display stacktrace

Remko Popma created LOG4J2-1581: --- Summary: Warning should not display stacktrace Key: LOG4J2-1581 URL: https://issues.apache.org/jira/browse/LOG4J2-1581 Project: Log4j 2 Issue Type

Re: compiler warning

t;> Sent from my iPhone >> >> On 2016/06/12, at 6:06, Gary Gregory wrote: >> >> The changes for MessageFactory2 now give the following warnings. I think >> we should fix these. >> >> [WARNING] >> E:\vcs\git\apache\logging\logging-log4j2\log4j-a

Re: compiler warning

give the following warnings. I think > we should fix these. > > [WARNING] > E:\vcs\git\apache\logging\logging-log4j2\log4j-api\src\main\java\org\apache\logging\log4j\status\StatusLogger.java:[45,13] > [unchecked] getMessageFactory() in AbstractLogger implements > getMessageFacto

Re: compiler warning

What needs to be done to fix this? Sent from my iPhone > On 2016/06/12, at 6:06, Gary Gregory wrote: > > The changes for MessageFactory2 now give the following warnings. I think we > should fix these. > > [WARNING] > E:\vcs\git\apache\logging\logging-log4j2\log4j-

compiler warning

The changes for MessageFactory2 now give the following warnings. I think we should fix these. [WARNING] E:\vcs\git\apache\logging\logging-log4j2\log4j-api\src\main\java\org\apache\logging\log4j\status\StatusLogger.java:[45,13] [unchecked] getMessageFactory() in AbstractLogger implements

[jira] [Resolved] (LOG4J2-1416) Log4j 2.6 warning for a null message factory

noticed and will be addressed in the upcoming 2.6.1 release (which is now under review and will be live in ~48 hours if no showstoppers are found). > Log4j 2.6 warning for a null message factory > > > Key: LOG4J2-1416 >

[jira] [Created] (LOG4J2-1416) Log4j 2.6 warning for a null message factory

Alireza Fattahi created LOG4J2-1416: --- Summary: Log4j 2.6 warning for a null message factory Key: LOG4J2-1416 URL: https://issues.apache.org/jira/browse/LOG4J2-1416 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

vise everybody to stop using SLF4J and use the Log4j2 API instead. It lets you use modern and powerful new features. If you change your mind later you can always fall back with log4j-to-slf4j. > log4j-slf4j-impl 2.6 is warning > > >

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314058#comment-15314058 ] yuedaxia commented on LOG4J2-1404: -- sorry ,my system is slow , because this warnin

[jira] [Closed] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1404. --- > log4j-slf4j-impl 2.6 is warning > > >

[jira] [Resolved] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1404. - Resolution: Duplicate > log4j-slf4j-impl 2.6 is warn

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

has been fixed in LOG4J2-1407. > log4j-slf4j-impl 2.6 is warning > > > Key: LOG4J2-1404 > URL: https://issues.apache.org/jira/browse/LOG4J2-1404 > Project: Log4j 2 > Issue Type: Bug >

[jira] [Updated] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

: when use log4j 2 2.6 , some class like private static final Logger log = LoggerFactory.getLogger(RestDispatcherServlet .class); has warning : WARN The Logger com.gentlesoft.framework.RestDispatcherServlet was created with the message factory org.apache.logging.log4j.spi.MessageFactory2Adapter

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is slow and warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311820#comment-15311820 ] Remko Popma commented on LOG4J2-1404: - The warning has also been reported in LO

[jira] [Created] (LOG4J2-1404) log4j-slf4j-impl 2.6 is slow and warning

yuedaxia created LOG4J2-1404: Summary: log4j-slf4j-impl 2.6 is slow and warning Key: LOG4J2-1404 URL: https://issues.apache.org/jira/browse/LOG4J2-1404 Project: Log4j 2 Issue Type: Bug

[jira] [Closed] (LOG4J2-729) Emit warning message to console if no config file found

[ https://issues.apache.org/jira/browse/LOG4J2-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyrille Karmann closed LOG4J2-729. -- Verified, thanks. Closing now. > Emit warning message to console if no config file fo

[jira] [Commented] (LOG4J2-729) Emit warning message to console if no config file found

ause I see this error message dozens of times every time I build log4j-core! > Emit warning message to console if no config file found > --- > > Key: LOG4J2-729 > URL: https://issues.apache.org/jir

[jira] [Resolved] (LOG4J2-729) Emit warning message to console if no config file found

[ https://issues.apache.org/jira/browse/LOG4J2-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-729. Resolution: Fixed Log4j2 will now emit the following warning message to System.err if no

[jira] [Updated] (LOG4J2-729) Emit warning message to console if no config file found

[ https://issues.apache.org/jira/browse/LOG4J2-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-729: --- Fix Version/s: 2.0.2 Assignee: Remko Popma Summary: Emit warning message to

[jira] [Closed] (LOG4J2-765) Feature request: log warning to console if default configuration is used when missing log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-765. -- > Feature request: log warning to console if default configuration is used when > missing log4

[jira] [Resolved] (LOG4J2-765) Feature request: log warning to console if default configuration is used when missing log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-765. Resolution: Fixed Fix Version/s: 2.0.2 Assignee: Remko Popma Improved the warning

[jira] [Updated] (LOG4J2-765) Feature request: log warning to console if default configuration is used when missing log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-765: --- Summary: Feature request: log warning to console if default configuration is used when missing log4j

[jira] [Commented] (LOG4J2-765) Feature request: log warning to console if default configuration is used

API doesn't have any plugins (no shaded Log42jPlugins.dat file). In fact, I'd like an API+Core jar just for OSGi simplification at some point, but it's not necessary (or encouraged). > Feature request: log warning to console if default

[jira] [Commented] (LOG4J2-765) Feature request: log warning to console if default configuration is used

d/or a api+core jar. > Feature request: log warning to console if default configuration is used > > > Key: LOG4J2-765 > URL: https://issues.apache.org/jira/browse/LOG4J2-765 &g

[jira] [Created] (LOG4J2-765) Feature request: log warning to console if default configuration is used

Remko Popma created LOG4J2-765: -- Summary: Feature request: log warning to console if default configuration is used Key: LOG4J2-765 URL: https://issues.apache.org/jira/browse/LOG4J2-765 Project: Log4j 2

[jira] [Resolved] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

and close. You'll still get warnings about "ch.qos.cal10n.verifier.processor.CAL10NAnnotationProcessor" when compiling log4j-core, though, but that's an SLF4J-related project. > PluginProcessor outputs w

[jira] [Assigned] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

[ https://issues.apache.org/jira/browse/LOG4J2-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-683: -- Assignee: Matt Sicker > PluginProcessor outputs warning if running JR

[jira] [Commented] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

ling with JDK 1.7 (with "-source 1.7" compiler flag) since upgrading to 2.0-rc2 > PluginProcessor outputs warning if running JRE>6 > > > Key: LOG4J2-683 > URL: https://issues.a

[jira] [Comment Edited] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

But since RC2 it is outputting this warning sometimes multiple times in my gradle build scripts if I activate Log4j2 and I hope this warning can be removed somehow. was (Author: jurmous): Ok I removed the suggestion from the comment to focus more on the issue itself. I should have known better

[jira] [Commented] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

ment to focus more on the issue itself. I should have known better than that. :) Here is something on stack overflow on this issue. http://stackoverflow.com/questions/8185331/forward-compatible-java-6-annotation-processor-and-supportedsourceversion But since RC2 it is outputting this war

[jira] [Updated] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

[ https://issues.apache.org/jira/browse/LOG4J2-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurriaan Mous updated LOG4J2-683: - Description: Output: warning: Supported source version 'RELEASE_6' from annotation

[jira] [Commented] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

tion like that. # I don't think you can increase the supported source version without compiling against that version of the API. The reasoning behind this annotation is due to changes in the model classes and such that go with the annotation processing API. > PluginProcessor outputs warni

[jira] [Created] (LOG4J2-683) PluginProcessor outputs warning if running newer JDK

Jurriaan Mous created LOG4J2-683: Summary: PluginProcessor outputs warning if running newer JDK Key: LOG4J2-683 URL: https://issues.apache.org/jira/browse/LOG4J2-683 Project: Log4j 2 Issue

[jira] [Updated] (LOG4J2-683) PluginProcessor outputs warning if running JRE>6

[ https://issues.apache.org/jira/browse/LOG4J2-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurriaan Mous updated LOG4J2-683: - Summary: PluginProcessor outputs warning if running JRE>6 (was: PluginProcessor outputs warn

DO NOT REPLY [Bug 41487] Warning when configuring inner-class logger

https://issues.apache.org/bugzilla/show_bug.cgi?id=41487 Curt Arnold changed: What|Removed |Added CC||rca...@gmail.com --- Comment #4 from

DO NOT REPLY [Bug 44219] 'WARNING' for a log level is silently ignored/changed to DEBUG

https://issues.apache.org/bugzilla/show_bug.cgi?id=44219 Maxx <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTED] --

DO NOT REPLY [Bug 44219] 'WARNING' for a log level is silently ignored/changed to DEBUG

us|NEW |NEEDINFO --- Comment #1 from Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> 2008-08-02 14:04:01 PST --- I am wondering whether this would be considered to break backwards compatibility or just considered a bug fix :) Personally I think that an explicit log4j warning "unknown l

DO NOT REPLY [Bug 44219] New: - 'WARNING' for a log level is silently ignored/changed to DEBUG

gzilla/show_bug.cgi?id=44219 Summary: 'WARNING' for a log level is silently ignored/changed to DEBUG Product: Log4j Version: 1.2 Platform: Other OS/Version: other Status: NEW Severity: normal

DO NOT REPLY [Bug 41487] - Warning when configuring inner-class logger

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41487] - Warning when configuring inner-class logger

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41487] - Warning when configuring inner-class logger

og any XML validation errors but will otherwise ignore them which results in you getting a distrurbing warning message but no other negative consequence. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You a

DO NOT REPLY [Bug 41487] New: - Warning when configuring inner-class logger

gzilla/show_bug.cgi?id=41487 Summary: Warning when configuring inner-class logger Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Config

Warning

Hi! I sent this message to [EMAIL PROTECTED], but as I don't have any response... I downloaded the last log4j, file logging-log4j-1.2.14.zip and sent it to my email address (at Yahoo!). Yahoo! Norton AntiVirus said that this file contains a virus that can't be eliminated! It don't said wh

[WARNING] Virus

Hello, It appears that a virus infected machine is sending message under my name. These messages are not from me. You should not attempt to open the infected attachments. I hardly ever use attachments in my email notes. Regards, -- Ceki Gülcü For log4j documentation consider "The complete