[PATCH] - LOG4J2-256 - SyslogWraplayout
Hi, my first OSS patch ever ;-) Tomek SyslogWrapLayout.java.patch Description: Binary data - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: [PATCH] - LOG4J2-256 - SyslogWraplayout
Hello Tomek, Thank you for the patch and welcome to OSS! The way to submit a contribution is to add your patch file to the JIRA you created for the issue. Adding unit tests to the patch is a best practice. It will increase the odds one of us will take the time to review it. Thank you! Gary On Fri, May 17, 2013 at 7:44 AM, Tomek Kaczynski tomek.kaczyn...@gmail.comwrote: Hi, my first OSS patch ever ;-) Tomek - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Editionhttp://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
[jira] [Updated] (LOG4J2-256) SyslogWrapAppender - embed layout format in SyslogLayout
[
https://issues.apache.org/jira/browse/LOG4J2-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Kaczyński updated LOG4J2-256:
---
Attachment: SyslogWrapLayout.java.patch
SyslogWrapAppender - embed layout format in SyslogLayout
Key: LOG4J2-256
URL: https://issues.apache.org/jira/browse/LOG4J2-256
Project: Log4j 2
Issue Type: Improvement
Components: Layouts
Affects Versions: 2.0-beta6
Reporter: Tomek Kaczyński
Attachments: SyslogWrapLayout.java.patch
It would be nice to be able to appy custom format to a message sent using
SyslogLayout, user will be able to use PatternLayout/XMLLayout, etc... and
format it as a syslog message (add syslog header ).
so the usage would be :
SyslogWrapLayout facility=lpr
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %marker.%-5level
%logger{2.} - %msg/
/SyslogWrapLayout
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[Bug 41006] Contributing XMLSocketHubReceiver
https://issues.apache.org/bugzilla/show_bug.cgi?id=41006 --- Comment #6 from Thomas Raddatz thomas.radd...@tools400.de --- I am sorry, but I do not have any unit tests for it. Are there any unit test for the SocketHubReceicer that could be taken as a starting point? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[Bug 41006] Contributing XMLSocketHubReceiver
https://issues.apache.org/bugzilla/show_bug.cgi?id=41006 --- Comment #7 from Scott Deboy sde...@iname.com --- There are probably no receiver unit tests..I think it would be ok to confirm it works via Chainsaw. Can you add a comment here describing how you test it? I can't believe this has been sitting here so long...terrible...I apologize. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-229) New JDBC, JPA, and NoSQL database Appenders
[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661251#comment-13661251 ] Nick Williams commented on LOG4J2-229: -- I have significantly improved the documentation. The JPA Appender isn't proved and won't be until the Hibernate bug is fixed, but the JDBC and NoSQL Appenders should be good to do. As far as I'm concerned, we're at a good point for beta7. New JDBC, JPA, and NoSQL database Appenders --- Key: LOG4J2-229 URL: https://issues.apache.org/jira/browse/LOG4J2-229 Project: Log4j 2 Issue Type: New Feature Components: Appenders, Core Affects Versions: 2.0-beta5 Reporter: Nick Williams Assignee: Nick Williams Attachments: db-appenders-r1479389.patch Original Estimate: 168h Remaining Estimate: 168h As discussed on the mailing list ([1] and [2]), Log4j 2 is in need of some database appenders. I have added this new feature and will attach a patch shortly. The patch contains: - A slight change to PatternLayout. Currently it is not possible to create a PatternLayout that doesn't always handle exceptions. If you leave all exception handling out of the pattern, an exception handler is forcibly added to the end of the pattern. This behavior is controlled by a flag, but that flag is always hard-coded to false. I added a parameter for it. This was necessary for the JDBC appender. - o.a.l.l.core.appender.db.AbstractDatabaseManager and AbstractDatabaseAppender, together in concert, take care of some core functionality common across all database appenders, such as buffering and connection state. - o.a.l.l.core.appender.db.jdbc.JDBCAppender (and Manager, other classes) supports writing events to a relational database using raw JDBC. It's injection-safe due to the use of prepared statements. It can be configured with URL/username/password, JNDI data source, or a connection factory method. - o.a.l.l.core.appender.db.jpa.JPAAppender (and Manager, other classes) supports writing events to a relational database using the Java Persistence API version 2.0. - o.a.l.l.core.appender.db.nosql.NoSQLAppender (and Manager, other classes) supports writing to an abstract concept of a NoSQL provider. Providers have been created for MongoDB and Apache CouchDB. Creating a new provider is extremely easy. - Thorough unit tests for the abstract classes, the JDBC and JPA appenders, and the abstract parts of the NoSQLAppender. Directly unit testing the MongoDB and CouchDB providers in a platform-independent way is not easy and may not be possible. - Thorough documentation (both JavaDoc and Site documentation) for all of the appenders. [1] http://markmail.org/thread/z2wpmwelv7p6xh2o [2] http://markmail.org/thread/s7pljqdjhjz5xfk5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Site Ideas
The roles are still there in the pom. Do we still need them? I don't mind removing them. From: Nick Williams nicho...@nicholaswilliams.net To: Log4J Developers List log4j-dev@logging.apache.org Sent: Tuesday, May 14, 2013 9:38 AM Subject: Re: Site Ideas Item #4 is now done as well. Nick On May 12, 2013, at 6:18 AM, Ralph Goers wrote: As for attribution, not really. The only place attribution really shows up is in svn. If someone really wants to know who wrote a piece of code they will just look at its history. Remember, the ASF is about community. As a committer you get just as much credit (or blame) for all the work I have done as I do. With attribution what you will find is people start emailing you in private off the lists. This has happened to me quite a bit over the last few years. We don't want that as it doesn't serve the whole community. That said, people will still know that you are the async expert when you are the main person answering questions and fixing issues related to it. Ralph On May 12, 2013, at 1:59 AM, Remko Popma rem...@yahoo.com wrote: 1. Agree this looks funny. What I found interesting is that (based on Ralph's link) the developers originally added the time zone in the Actual Time column, intentionally showing local time zone of the viewer. Ironically the intention was to avoid confusion. I'm sure there's a lesson in there somewhere. :-) 2. All right then, remove the roles. Is there a more acceptable way to get attribution for the Async Loggers somewhere on the site? 3. I experimented with it but switching on the pic also adds another column with the pic URL. (Not very useful IMHO. Shall we file another bug/feature request with the maven team? Show pic, without adding pic URL column.) 4. Sounds good. Sent from my iPhone On 2013/05/12, at 9:46, Ralph Goers ralph.go...@dslextreme.com wrote: Item one This makes no sense to me but see https://jira.codehaus.org/browse/MPIR-68 Item two Normally I would expect the Roles to contain PMC Member, Committer or Contributor, not the parts of the project individuals work on. Item three I don't care one way or the other about images. If you want to see what I look like you can just go to images.google.com and search on my name. You should find two photos; one in a yellow shirt that is several years old from the ApacheCon in Austin, TX and a recent photo from a Flume meetup. Item four I have no problem with the suggestion you are making. Ralph On May 11, 2013, at 4:13 PM, Nick Williams wrote: Guys, There are a couple of things about the site that have been bugging me. I wanted to run some ideas by you and see what you think. Since I can commit now, I can take care of them once we come to a consensus. :-) -- One -- On the Project Team pages, the Actual Time column is wrong for most of us. For those of us in the United States, it's one hour behind. Only for Remko is it right. For example, at 17:38:55 Central Time, here is what it said for all of us: Ralph: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Gary: Sat May 11 2013 17:38:55 GMT-0500 (CDT) (it's actually 18:38 there) Scott: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Remko: Sun May 12 2013 07:38:55 GMT-0500 (CDT) (the time is correct) Me: Sat May 11 2013 16:38:55 GMT-0500 (CDT) (it's actually 17:38 here) Not only is the time wrong for four of us, but they ALL say GMT-0500 (CDT), which is obviously incorrect for all of us except me. I did some looking around at other Maven-generated sites, and the problem seems to be the same on all of them. Wrong for people on Daylight Savings Time, and always displaying the wrong time zone for everyone: http://maven.apache.org/team-list.html http://displaytag.sourceforge.net/11/team-list.html This appears to be a problem with the Maven plugin itself, not with our site. The time appears to be calculated dynamically using JavaScript after the page loads. Is anyone aware of any bug reports anywhere concerning this issue? If not, I'll file a bug. -- Two -- On the Project Team pages, I suggest we remove the Roles column. Remko is the only one with any data in that column, and I think that makes it look like he doesn't contribute as much as the rest of us. Remko has contributed more than just what's listed in that column. Is everyone okay with removing that column? -- Three -- On the Project Team pages, none of us have images. I suggest we either add images for all of us or remove the column (as it's taking up unnecessary space). Remko already has an image URL in the POM, but it's commented out. I'm all for images, personally, but what do y'all think? -- Four -- The first item I visited the Log4j2 site, the Download and Build and Install links confused me. The Download page contained links to download the assembly JAR ... makes sense. But no Maven information. The Build
[jira] [Closed] (LOG4J2-255) Multi-byte character strings are scrambled in log output
[
https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-255.
--
Multi-byte character strings are scrambled in log output
Key: LOG4J2-255
URL: https://issues.apache.org/jira/browse/LOG4J2-255
Project: Log4j 2
Issue Type: Bug
Components: Appenders, Core
Affects Versions: 2.0-beta6
Reporter: Remko Popma
Assignee: Remko Popma
Priority: Blocker
Fix For: 2.0-beta7
When I tried to log a Japanese string the output was scrambled in both the
Console and a log file.
For example,
logger.warn(日本語テスト); // (Japanese test)
came out as
15:07:00.184 [main] WARN test.JapaneseTest - 譌･譛ｬ隱槭ユ繧ｹ繝?
This is the log4j2.xml configuration:
{code:xml}
?xml version=1.0 encoding=UTF-8?
configuration status=warn
appenders
Console name=Console target=SYSTEM_OUT
PatternLayout
pattern%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n
/pattern
/PatternLayout
/Console
File name=tracelog fileName=trace-log.txt immediateFlush=true
append=false
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level
%logger{36} - %msg%n/
/File
/appenders
loggers
root level=trace
appender-ref ref=Console/
appender-ref ref=tracelog/
/root
/loggers
/configuration
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Site Ideas
Per Gary and Ralph, the roles have been changed to PMC Member, Committer, etc. Nick On May 17, 2013, at 10:44 PM, Remko Popma wrote: The roles are still there in the pom. Do we still need them? I don't mind removing them. From: Nick Williams nicho...@nicholaswilliams.net To: Log4J Developers List log4j-dev@logging.apache.org Sent: Tuesday, May 14, 2013 9:38 AM Subject: Re: Site Ideas Item #4 is now done as well. Nick On May 12, 2013, at 6:18 AM, Ralph Goers wrote: As for attribution, not really. The only place attribution really shows up is in svn. If someone really wants to know who wrote a piece of code they will just look at its history. Remember, the ASF is about community. As a committer you get just as much credit (or blame) for all the work I have done as I do. With attribution what you will find is people start emailing you in private off the lists. This has happened to me quite a bit over the last few years. We don't want that as it doesn't serve the whole community. That said, people will still know that you are the async expert when you are the main person answering questions and fixing issues related to it. Ralph On May 12, 2013, at 1:59 AM, Remko Popma rem...@yahoo.com wrote: 1. Agree this looks funny. What I found interesting is that (based on Ralph's link) the developers originally added the time zone in the Actual Time column, intentionally showing local time zone of the viewer. Ironically the intention was to avoid confusion. I'm sure there's a lesson in there somewhere. :-) 2. All right then, remove the roles. Is there a more acceptable way to get attribution for the Async Loggers somewhere on the site? 3. I experimented with it but switching on the pic also adds another column with the pic URL. (Not very useful IMHO. Shall we file another bug/feature request with the maven team? Show pic, without adding pic URL column.) 4. Sounds good. Sent from my iPhone On 2013/05/12, at 9:46, Ralph Goers ralph.go...@dslextreme.com wrote: Item one This makes no sense to me but see https://jira.codehaus.org/browse/MPIR-68 Item two Normally I would expect the Roles to contain PMC Member, Committer or Contributor, not the parts of the project individuals work on. Item three I don't care one way or the other about images. If you want to see what I look like you can just go to images.google.com and search on my name. You should find two photos; one in a yellow shirt that is several years old from the ApacheCon in Austin, TX and a recent photo from a Flume meetup. Item four I have no problem with the suggestion you are making. Ralph On May 11, 2013, at 4:13 PM, Nick Williams wrote: Guys, There are a couple of things about the site that have been bugging me. I wanted to run some ideas by you and see what you think. Since I can commit now, I can take care of them once we come to a consensus. :-) -- One -- On the Project Team pages, the Actual Time column is wrong for most of us. For those of us in the United States, it's one hour behind. Only for Remko is it right. For example, at 17:38:55 Central Time, here is what it said for all of us: Ralph: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Gary: Sat May 11 2013 17:38:55 GMT-0500 (CDT) (it's actually 18:38 there) Scott: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Remko: Sun May 12 2013 07:38:55 GMT-0500 (CDT) (the time is correct) Me: Sat May 11 2013 16:38:55 GMT-0500 (CDT) (it's actually 17:38 here) Not only is the time wrong for four of us, but they ALL say GMT-0500 (CDT), which is obviously incorrect for all of us except me. I did some looking around at other Maven-generated sites, and the problem seems to be the same on all of them. Wrong for people on Daylight Savings Time, and always displaying the wrong time zone for everyone: http://maven.apache.org/team-list.html http://displaytag.sourceforge.net/11/team-list.html This appears to be a problem with the Maven plugin itself, not with our site. The time appears to be calculated dynamically using JavaScript after the page loads. Is anyone aware of any bug reports anywhere concerning this issue? If not, I'll file a bug. -- Two -- On the Project Team pages, I suggest we remove the Roles column. Remko is the only one with any data in that column, and I think that makes it look like he doesn't contribute as much as the rest of us. Remko has contributed more than just what's listed in that column. Is everyone okay with removing that column? -- Three -- On the Project Team pages, none of us have images. I suggest we either add images for all of us or remove the column (as it's taking up unnecessary space). Remko already has an image URL in the POM, but it's commented out. I'm all for images, personally, but what do y'all think? -- Four -- The first item I
Re: EmptyStackException in Log4j2 beta5 and beta6
I have verified that this is fixed in 2.0-beta7-SNAPSHOT. Thanks! Nick On May 15, 2013, at 11:29 AM, Ralph Goers wrote: Nick, Have you verified the fix I made to avoid the exception below? I have looked at the Java 8 source but I can't find the source for the sun classes - I'm not even sure where (or if) you found the javadoc. But so far I haven't found a replacement for getCallerClass in Java 8. Since Java 8 isn't even final yet though I'm reluctant to spend a lot of energy investigating how to deal with that - especially since I recall that you opened an issue (although my experience is those kinds of issues just get ignored). In any case, we said we would do a new release once this issue was fixed so I am thinking that I will probably do that sometime on Sunday (PDT). We have plenty of other issues that should be addressed and I am hoping I can use the time between now and then to get to a few of them. Ralph On May 8, 2013, at 8:45 PM, Nick Williams wrote: I get the following exception written to my Tomcat log. Looks like Spring Framework tried to log an error (through the log4j-jcl bridge) but something happened in Log4j2 that masked the error. Do I need to just file a bug? If this is a bug and not me doing something wrong, I'm going to -1 (non-binding) beta6. Why on Earth does peek() throw EmptyStackException!? Who's bright idea was that!? SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at org.apache.logging.log4j.core.impl.ThrowableProxy.resolvePackageData(ThrowableProxy.java:339) at org.apache.logging.log4j.core.impl.ThrowableProxy.init(ThrowableProxy.java:71) at org.apache.logging.log4j.core.impl.Log4jLogEvent.init(Log4jLogEvent.java:110) at org.apache.logging.log4j.core.impl.Log4jLogEvent.init(Log4jLogEvent.java:81) at org.apache.logging.log4j.core.config.LoggerConfig.createEvent(LoggerConfig.java:423) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:344) at org.apache.logging.log4j.core.Logger.log(Logger.java:110) at org.apache.logging.log4j.spi.AbstractLoggerWrapper.log(AbstractLoggerWrapper.java:55) at org.apache.logging.log4j.spi.AbstractLogger.error(AbstractLogger.java:539) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:319) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4765) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5210) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:702) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:698) at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1491) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:491) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:468) at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:415) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:491) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1465) at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:75) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1306) at
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661262#comment-13661262
]
Nick Williams commented on LOG4J2-223:
--
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.logging.log4j.core.config.NullConfiguration. The eventual following
stack trace is caused by an error thrown for debugging purposes as well as to
attempt to terminate the thread which caused the illegal access, and has no
functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more{noformat}
IlliegalStateException thrown during Tomcat shutdown
Key: LOG4J2-223
URL: https://issues.apache.org/jira/browse/LOG4J2-223
Project: Log4j 2
Issue Type: Bug
Components: Core
Affects Versions: 2.0-beta5
Reporter: Ralph Goers
Priority: Critical
Fix For: 2.0-beta7
Attachments: logging-integration-1.0.0.SNAPSHOT.war,
Logging-Integration.zip
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping
the Server instance.
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.
Could not load org.apache.logging.log4j.core.config.NullConfiguration. The
eventual following stack trace is caused by an error thrown for debugging
purposes as well as to attempt to terminate the thread which caused the
illegal access, and has no functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389)
Exception in thread Thread-18 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail:
[jira] [Commented] (LOG4J2-232) Custom Converter plugin won't load.
[
https://issues.apache.org/jira/browse/LOG4J2-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661261#comment-13661261
]
Remko Popma commented on LOG4J2-232:
Did you get a chance to run the stand-alone test program?
Custom Converter plugin won't load.
---
Key: LOG4J2-232
URL: https://issues.apache.org/jira/browse/LOG4J2-232
Project: Log4j 2
Issue Type: Bug
Affects Versions: 2.0-beta5
Reporter: Remko Popma
Assignee: Remko Popma
From: John Smith java.dev@gmail.com
To: log4j-u...@logging.apache.org
Sent: Thursday, May 2, 2013 5:41 AM
Subject: Custom Converter plugin won't load.
Using log4j2-beta5
I'm writing a custom PatternConverter to mask logs for such things as
Credit Card and Card Security Code and some additional elements.
My converter looks like so
package com.xxx.log4j.converters;
import java.util.List;
import java.util.regex.Pattern;
import org.apache.logging.log4j.core.LogEvent;
import org.apache.logging.log4j.core.config.Configuration;
import org.apache.logging.log4j.core.config.plugins.Plugin;
import org.apache.logging.log4j.core.layout.PatternLayout;
import org.apache.logging.log4j.core.pattern.ConverterKeys;
import org.apache.logging.log4j.core.pattern.LogEventPatternConverter;
import org.apache.logging.log4j.core.pattern.PatternFormatter;
import org.apache.logging.log4j.core.pattern.PatternParser;
@Plugin(name = MaskConverter, type = Converter)
@ConverterKeys({ma, mask })
public class MaskConverter extends LogEventPatternConverter {
private final ListPatternFormatter formatters;
private final Pattern ccPattern;
private final Pattern cvnPattern;
public static final String CARD_PATTERN =
(AcctNumber|AcctNumber2)([=\\^])([0-9]+)([0-9]{4});
public static final String CARD_MASK = $1$2$4;
public static final String CVN_PATTERN = (Cvn)([=\\^])([0-9]{3,4});
public static final String CVN_MASK = $1$2;
private MaskConverter(final ListPatternFormatter formatters, final
Pattern ccPattern, final Pattern cvnPattern) {
super(ma, mask);
System.out.println(Here...);
this.formatters = formatters;
this.ccPattern = ccPattern;
this.cvnPattern = cvnPattern;
}
public static MaskConverter newInstance(final Configuration config,
final String[] options) {
System.out.println(There...);
if (options.length != 1) {
LOGGER.error(Incorrect number of options on mask. Expected 1
received + options.length);
return null;
}
final Pattern ccPattern = Pattern.compile(CARD_PATTERN,
Pattern.CASE_INSENSITIVE);
final Pattern cvnPattern = Pattern.compile(CVN_PATTERN,
Pattern.CASE_INSENSITIVE);
final PatternParser parser =
PatternLayout.createPatternParser(config);
final ListPatternFormatter formatters = parser.parse(options[0]);
return new MaskConverter(formatters, ccPattern, cvnPattern);
}
@Override
public void format(final LogEvent event, final StringBuilder toAppendTo) {
System.out.println(Where... + event.getMessage());
final StringBuilder buf = new StringBuilder();
for (final PatternFormatter formatter : formatters) {
formatter.format(event, buf);
}
toAppendTo.append(ccPattern.matcher(cvnPattern.matcher(buf.toString()).replaceAll(CVN_MASK)).replaceAll(CARD_MASK));
}
}
And my log4j2.xml looks like...
?xml version=1.0 encoding=UTF-8?
configuration status=TRACE monitorInterval=5
packages=com.xxx.log4j.converters,
appenders
FastFile name=FILE fileName=C:/Temp/XXXJava/logs/vertx.log
immediateFlush=false append=false
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} -
%mask{%msg}%n/
/FastFile
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} -
%mask{%msg}%n/
/Console
/appenders
loggers
root level=DEBUG
appender-ref ref=Console/
appender-ref ref=FILE/
/root
/loggers
/configuration
But it doesn't seem to load the plugin I don't see any of my print
statements in the console and all I see is the word ask appended to my log
messages.
Have I missed something
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Comment Edited] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661262#comment-13661262
]
Nick Williams edited comment on LOG4J2-223 at 5/18/13 3:59 AM:
---
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.logging.log4j.core.config.NullConfiguration. The eventual following
stack trace is caused by an error thrown for debugging purposes as well as to
attempt to terminate the thread which caused the illegal access, and has no
functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more{noformat}
I'd really like to see this issue fixed before beta7 is released. Are you not
able to replicate it in my sample application?
I'd try to help with this, but now that Spring 4.0.0.M1 has been released
(today), I have to get back to working on my book now. I'm about four weeks
behind on chapters. Ooops.
was (Author: beamerblvd):
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.logging.log4j.core.config.NullConfiguration. The eventual following
stack trace is caused by an error thrown for debugging purposes as well as to
attempt to terminate the thread which caused the illegal access, and has no
functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more{noformat}
IlliegalStateException thrown during Tomcat shutdown
Key: LOG4J2-223
URL: https://issues.apache.org/jira/browse/LOG4J2-223
Project: Log4j 2
Issue Type: Bug
Components: Core
Affects Versions: 2.0-beta5
Reporter: Ralph Goers
Priority: Critical
Fix For: 2.0-beta7
Attachments: logging-integration-1.0.0.SNAPSHOT.war,
Logging-Integration.zip
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping
the Server instance.
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM
[jira] [Comment Edited] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661262#comment-13661262
]
Nick Williams edited comment on LOG4J2-223 at 5/18/13 4:01 AM:
---
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.logging.log4j.core.config.NullConfiguration. The eventual following
stack trace is caused by an error thrown for debugging purposes as well as to
attempt to terminate the thread which caused the illegal access, and has no
functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more{noformat}
I'd really like to see this issue fixed before beta7 is released. Are you able
to replicate it in my sample application? Or have you still not been able to
look at it? Is there anyone else that can look at it?
I'd try to help with this, but now that Spring 4.0.0.M1 has been released
(today), I have to get back to working on my book now. I'm about four weeks
behind on chapters. Ooops.
was (Author: beamerblvd):
In the latest 2.0-beta7-SNAPSHOT, this is still not fixed:
{noformat}INFO: Illegal access: this web application instance has been stopped
already. Could not load
org.apache.logging.log4j.core.config.NullConfiguration. The eventual following
stack trace is caused by an error thrown for debugging purposes as well as to
attempt to terminate the thread which caused the illegal access, and has no
functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Exception in thread Thread-19 java.lang.NoClassDefFoundError:
org/apache/logging/log4j/core/config/NullConfiguration
at
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:201)
at
org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:427)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.config.NullConfiguration
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310)
... 2 more{noformat}
I'd really like to see this issue fixed before beta7 is released. Are you not
able to replicate it in my sample application?
I'd try to help with this, but now that Spring 4.0.0.M1 has been released
(today), I have to get back to working on my book now. I'm about four weeks
behind on chapters. Ooops.
IlliegalStateException thrown during Tomcat shutdown
Key: LOG4J2-223
URL: https://issues.apache.org/jira/browse/LOG4J2-223
Project: Log4j 2
Issue Type: Bug
Components: Core
Affects Versions: 2.0-beta5
Reporter: Ralph Goers
Priority: Critical
Fix For: 2.0-beta7
Attachments: logging-integration-1.0.0.SNAPSHOT.war,
Logging-Integration.zip
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping
the Server instance.
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-nio-8080]
Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-nio-8009]
Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service
Re: Inconsistency in import ordering
Scott, is there a particular page on the Wiki you want me to add them to? I'm not finding a whole lot just looking around. :-/ Nick On May 16, 2013, at 5:28 PM, Scott Deboy wrote: Sure, add them to the wiki please. On 5/16/13, Nick Williams nicho...@nicholaswilliams.net wrote: CheckStyle ImportOrder changes committed. I also committed the changes necessary to rid all database appender and tag library classes of CheckStyle ImportOrder errors. I will continue to work on reordering imports in other classes. To prevent these CheckStyle errors from coming back, we should all align our IDEs' import settings with the CheckStyle rules below. If anyone is interested in a screenshot of the settings for IntelliJ IDEA, I can make that available. Nick On May 16, 2013, at 1:02 PM, Gary Gregory wrote: +1 Gary On Thu, May 16, 2013 at 1:45 PM, Nick Williams nicho...@nicholaswilliams.net wrote: I haven't heard any objections to this suggestion. I'm going to move forward with it later this afternoon if nobody objects before then. Thanks, Nick On May 13, 2013, at 11:06 AM, Nick Williams wrote: I've noticed a lot of inconsistence in import ordering, and importantly I've also noticed that when developers are using IDE (I believe we all are) the IDEs are constantly re-ordering imports previously committed by other developers. This results in lots of commits that appear to change imports but only change import ordering. I'd like to add the following CheckStyle: module name=ImportOrder !-- Imports must be separated (by one newline) into the following groups: java and javax org com all others Imports within a group must be sorted alphabetically (lexicographically) All static imports come below all other imports -- property name=groups value=/^javax?\./,org,com/ property name=ordered value=true/ property name=caseSensitive value=true / property name=separated value=true/ property name=option value=bottom/ /module This is similar to import order seen in other Apache projects. IntelliJ, Eclipse, and NetBeans are all capable of being configured to order imports in this same manner. If we agree to add this CheckStyle, we should all configure our local IDE per-project settings to enforce this ordering. Thoughts? - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661266#comment-13661266 ] Remko Popma commented on LOG4J2-223: Haven't had a chance. Have been making long hours at work. I don't think I'll be able to this weekend. I don't even have Tomcat set up yet... Btw, could you provide some more details on versions and stuff? Java version, Tomcat version? Any command line options? I'm not 100% sure but you are not using Async Loggers, are you? Are you using another ContextSelector? Also, not sure if relevant, but are you using the JSP TagLib? IlliegalStateException thrown during Tomcat shutdown Key: LOG4J2-223 URL: https://issues.apache.org/jira/browse/LOG4J2-223 Project: Log4j 2 Issue Type: Bug Components: Core Affects Versions: 2.0-beta5 Reporter: Ralph Goers Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.logging.log4j.core.config.NullConfiguration. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Exception in thread Thread-18 java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/config/NullConfiguration at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.config.NullConfiguration at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) ... 2 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661268#comment-13661268 ] Nick Williams commented on LOG4J2-223: -- Java 1.8.0-ea-b88 Tomcat 8.0-SNAPSHOT (r1478984) No special command-line options. I am not using Async Loggers. I am not using another ContextSelector. I /am/ using the Tag Library but I get this error even if I don't go to any JSPs, so I don't think that's it. I'd encourage you to try to duplicate this on Java 7 / Tomcat 7 before bothering trying to replicate my setup. IlliegalStateException thrown during Tomcat shutdown Key: LOG4J2-223 URL: https://issues.apache.org/jira/browse/LOG4J2-223 Project: Log4j 2 Issue Type: Bug Components: Core Affects Versions: 2.0-beta5 Reporter: Ralph Goers Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.logging.log4j.core.config.NullConfiguration. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Exception in thread Thread-18 java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/config/NullConfiguration at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.config.NullConfiguration at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) ... 2 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661289#comment-13661289 ] Remko Popma commented on LOG4J2-223: Thanks. Unexpected family circumstances just came up and I won't have access to a PC today, maybe this weekend. Only iPhone. Could you paste the output of StatusLogger debug output here? IlliegalStateException thrown during Tomcat shutdown Key: LOG4J2-223 URL: https://issues.apache.org/jira/browse/LOG4J2-223 Project: Log4j 2 Issue Type: Bug Components: Core Affects Versions: 2.0-beta5 Reporter: Ralph Goers Priority: Critical Fix For: 2.0-beta7 Attachments: logging-integration-1.0.0.SNAPSHOT.war, Logging-Integration.zip Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [http-nio-8080] Apr 25, 2013 3:03:33 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [ajp-nio-8009] Apr 25, 2013 3:03:33 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.logging.log4j.core.config.NullConfiguration. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1351) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Exception in thread Thread-18 java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/config/NullConfiguration at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:171) at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:389) Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.config.NullConfiguration at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1310) ... 2 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Site Ideas
Great, thank you. Gary On May 17, 2013, at 23:54, Nick Williams nicho...@nicholaswilliams.net wrote: Per Gary and Ralph, the roles have been changed to PMC Member, Committer, etc. Nick On May 17, 2013, at 10:44 PM, Remko Popma wrote: The roles are still there in the pom. Do we still need them? I don't mind removing them. -- *From:* Nick Williams nicho...@nicholaswilliams.net *To:* Log4J Developers List log4j-dev@logging.apache.org *Sent:* Tuesday, May 14, 2013 9:38 AM *Subject:* Re: Site Ideas Item #4 is now done as well. Nick On May 12, 2013, at 6:18 AM, Ralph Goers wrote: As for attribution, not really. The only place attribution really shows up is in svn. If someone really wants to know who wrote a piece of code they will just look at its history. Remember, the ASF is about community. As a committer you get just as much credit (or blame) for all the work I have done as I do. With attribution what you will find is people start emailing you in private off the lists. This has happened to me quite a bit over the last few years. We don't want that as it doesn't serve the whole community. That said, people will still know that you are the async expert when you are the main person answering questions and fixing issues related to it. Ralph On May 12, 2013, at 1:59 AM, Remko Popma rem...@yahoo.com wrote: 1. Agree this looks funny. What I found interesting is that (based on Ralph's link) the developers originally added the time zone in the Actual Time column, intentionally showing local time zone of the viewer. Ironically the intention was to avoid confusion. I'm sure there's a lesson in there somewhere. :-) 2. All right then, remove the roles. Is there a more acceptable way to get attribution for the Async Loggers somewhere on the site? 3. I experimented with it but switching on the pic also adds another column with the pic URL. (Not very useful IMHO. Shall we file another bug/feature request with the maven team? Show pic, without adding pic URL column.) 4. Sounds good. Sent from my iPhone On 2013/05/12, at 9:46, Ralph Goers ralph.go...@dslextreme.com wrote: Item one This makes no sense to me but see https://jira.codehaus.org/browse/MPIR-68 Item two Normally I would expect the Roles to contain PMC Member, Committer or Contributor, not the parts of the project individuals work on. Item three I don't care one way or the other about images. If you want to see what I look like you can just go to images.google.com and search on my name. You should find two photos; one in a yellow shirt that is several years old from the ApacheCon in Austin, TX and a recent photo from a Flume meetup. Item four I have no problem with the suggestion you are making. Ralph On May 11, 2013, at 4:13 PM, Nick Williams wrote: Guys, There are a couple of things about the site that have been bugging me. I wanted to run some ideas by you and see what you think. Since I can commit now, I can take care of them once we come to a consensus. :-) -- One -- On the Project Team pages, the Actual Time column is wrong for most of us. For those of us in the United States, it's one hour behind. Only for Remko is it right. For example, at 17:38:55 Central Time, here is what it said for all of us: Ralph: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Gary: Sat May 11 2013 17:38:55 GMT-0500 (CDT) (it's actually 18:38 there) Scott: Sat May 11 2013 14:38:55 GMT-0500 (CDT) (it's actually 15:38 there) Remko: Sun May 12 2013 07:38:55 GMT-0500 (CDT) (the time is correct) Me: Sat May 11 2013 16:38:55 GMT-0500 (CDT) (it's actually 17:38 here) Not only is the time wrong for four of us, but they ALL say GMT-0500 (CDT), which is obviously incorrect for all of us except me. I did some looking around at other Maven-generated sites, and the problem seems to be the same on all of them. Wrong for people on Daylight Savings Time, and always displaying the wrong time zone for everyone: http://maven.apache.org/team-list.html http://displaytag.sourceforge.net/11/team-list.html This appears to be a problem with the Maven plugin itself, not with our site. The time appears to be calculated dynamically using JavaScript after the page loads. Is anyone aware of any bug reports anywhere concerning this issue? If not, I'll file a bug. -- Two -- On the Project Team pages, I suggest we remove the Roles column. Remko is the only one with any data in that column, and I think that makes it look like he doesn't contribute as much as the rest of us. Remko has contributed more than just what's listed in that column. Is everyone okay with removing that column? -- Three -- On the Project Team pages, none of us have images. I suggest we either add images for all of us or remove the column (as it's taking up unnecessary space). Remko already has an image URL in the POM, but it's commented out. I'm all for images, personally, but what do y'all think? -- Four -- The first item I visited the Log4j2
