[jira] [Work started] (LOG4J2-2307) Reusable event memento messages should retain format

2018-04-04 Thread Carter Kozak (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on LOG4J2-2307 started by Carter Kozak.

> Reusable event memento messages should retain format
> 
>
> Key: LOG4J2-2307
> URL: https://issues.apache.org/jira/browse/LOG4J2-2307
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.11.0
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> Currently MutableLogEvent and RingBufferLogEvent memento implementations 
> create ParameterizedMessage instances using the formatted message string and 
> a copy of the parameter array.
> We can use a "MementoMessage" type with fields for both references to the 
> formatted message and the message format, as well as parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2307) Reusable event memento messages should retain format

2018-04-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426479#comment-16426479
 ] 

ASF GitHub Bot commented on LOG4J2-2307:


GitHub user cakofony opened a pull request:

https://github.com/apache/logging-log4j2/pull/162

LOG4J2-2307: MutableLogEvent memento retains format string

MementoLogEvent provides the original format string and parameters
in addition to the formatted text.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cakofony/logging-log4j2 memento_message

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/logging-log4j2/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #162


commit 39b82e15fde0cb64bbff04a610818219383ae9bc
Author: Carter Kozak 
Date:   2018-04-03T03:49:09Z

LOG4J2-2307: RingBufferLogEvent and MutableLogEvent memento to 
MementoLogEvent

MementoLogEvent provides the original format string and parameters
in addition to the formatted text.




> Reusable event memento messages should retain format
> 
>
> Key: LOG4J2-2307
> URL: https://issues.apache.org/jira/browse/LOG4J2-2307
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.11.0
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> Currently MutableLogEvent and RingBufferLogEvent memento implementations 
> create ParameterizedMessage instances using the formatted message string and 
> a copy of the parameter array.
> We can use a "MementoMessage" type with fields for both references to the 
> formatted message and the message format, as well as parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Carter Kozak (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carter Kozak closed LOG4J2-2306.


> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
> Fix For: 3.0.0
>
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Carter Kozak (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carter Kozak resolved LOG4J2-2306.
--
   Resolution: Fixed
Fix Version/s: 3.0.0

> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
> Fix For: 3.0.0
>
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426414#comment-16426414
 ] 

ASF GitHub Bot commented on LOG4J2-2306:


Github user cakofony closed the pull request at:

https://github.com/apache/logging-log4j2/pull/161


> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] logging-log4j2 pull request #161: LOG4J2-2306: Compile with Error Prone

2018-04-04 Thread cakofony 
Github user cakofony closed the pull request at:

https://github.com/apache/logging-log4j2/pull/161


---

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426412#comment-16426412
 ] 

ASF subversion and git services commented on LOG4J2-2306:
-

Commit 74df59c51ff62589ec9b9e7df11c27b9b88edc51 in logging-log4j2's branch 
refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=74df59c ]

[LOG4J2-2306] Compile with Error Prone for static analysis

Fixes several minor bugs uncovered by error prone.
Offset timezones are correctly parsed rather than using GMT.


> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426345#comment-16426345
 ] 

ASF GitHub Bot commented on LOG4J2-2306:


Github user remkop commented on the issue:

https://github.com/apache/logging-log4j2/pull/161
  
Changes look fine to me. 


> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] logging-log4j2 issue #161: LOG4J2-2306: Compile with Error Prone

2018-04-04 Thread remkop 
Github user remkop commented on the issue:

https://github.com/apache/logging-log4j2/pull/161
  
Changes look fine to me. 


---

[jira] [Commented] (LOG4J2-2129) Log4j2 throws NoClassDefFoundError in Java 9

2018-04-04 Thread Christopher (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426333#comment-16426333
 ] 

Christopher commented on LOG4J2-2129:
-

I get a similar error (jdk 9.0.4) using log4j 2.11.0 during runtime of an 
executable jar. I extracted the jar and the classes are there, but java -jar 
MyClass.jar outputs:

Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize 
class org.apache.logging.log4j.util.PropertiesUtil
 at org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:78)
 at org.apache.logging.log4j.LogManager.(LogManager.java:60)
 at com.myco.project.subproject.MyClass.(MyClass.java:37)

private static final Logger LOGGER = LogManager.getLogger(MyClass.class); // 37

 

> Log4j2 throws NoClassDefFoundError in Java 9
> 
>
> Key: LOG4J2-2129
> URL: https://issues.apache.org/jira/browse/LOG4J2-2129
> Project: Log4j 2
>  Issue Type: Bug
>  Components: API
>Affects Versions: 2.10.0, 2.11.0
> Environment: Java 9
>Reporter: Blazej
>Priority: Major
> Fix For: 2.11.0
>
> Attachments: log4j-api-patch.jar
>
>
> When I execute a sample project 
> (https://github.com/bbucko/log4j2-jpms-sample) in Java 9 a following 
> exception is thrown:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: Could not 
> initialize class org.apache.logging.log4j.util.PropertiesUtil
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:71)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.LogManager.(LogManager.java:60)
> {code}
> Exception is a little bit misleading because it seems that true root cause 
> can be found here:
> {code}
> java.util.ServiceConfigurationError: 
> org.apache.logging.log4j.util.PropertySource: module org.apache.logging.log4j 
> does not declare `uses`
>   at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
>   at java.base/java.util.ServiceLoader.checkCaller(ServiceLoader.java:574)
>   at java.base/java.util.ServiceLoader.(ServiceLoader.java:503)
>   at java.base/java.util.ServiceLoader.load(ServiceLoader.java:1684)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.(PropertiesUtil.java:319)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil$Environment.(PropertiesUtil.java:310)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.(PropertiesUtil.java:69)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.util.PropertiesUtil.(PropertiesUtil.java:49)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.util.Constants.(Constants.java:30)
>   at java.base/java.lang.Class.forName0(Native Method)
>   at java.base/java.lang.Class.forName(Class.java:375)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.createClassForProperty(AbstractLogger.java:198)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.spi.AbstractLogger.(AbstractLogger.java:88)
>   at 
> org.apache.logging.log4j/org.apache.logging.log4j.LogManager.(LogManager.java:60)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is still unstable: Log4j 2 2.x #3440

2018-04-04 Thread Apache Jenkins Server 
See

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Matt Sicker (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426148#comment-16426148
 ] 

Matt Sicker commented on LOG4J2-2306:
-

Seems handy!

> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Carter Kozak (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426141#comment-16426141
 ] 

Carter Kozak commented on LOG4J2-2306:
--

Commit with error prone enabled as well as bugfixes here: 
[https://github.com/apache/logging-log4j2/pull/161]

I can decouple the bugfixes from adding the plugin.

> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426138#comment-16426138
 ] 

ASF GitHub Bot commented on LOG4J2-2306:


GitHub user cakofony opened a pull request:

https://github.com/apache/logging-log4j2/pull/161

LOG4J2-2306: Compile with Error Prone



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cakofony/logging-log4j2 errorprone

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/logging-log4j2/pull/161.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #161


commit 08eaa24ca307ed5db47698b10293dca1a76c96d6
Author: Carter Kozak 
Date:   2018-04-04T19:35:46Z

Compile with Error Prone




> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] logging-log4j2 pull request #161: LOG4J2-2306: Compile with Error Prone

2018-04-04 Thread cakofony 
GitHub user cakofony opened a pull request:

https://github.com/apache/logging-log4j2/pull/161

LOG4J2-2306: Compile with Error Prone



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cakofony/logging-log4j2 errorprone

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/logging-log4j2/pull/161.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #161


commit 08eaa24ca307ed5db47698b10293dca1a76c96d6
Author: Carter Kozak 
Date:   2018-04-04T19:35:46Z

Compile with Error Prone




---

[jira] [Assigned] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Carter Kozak (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carter Kozak reassigned LOG4J2-2306:


Assignee: Carter Kozak

> Investigate using Error Prone for Static Analysis
> -
>
> Key: LOG4J2-2306
> URL: https://issues.apache.org/jira/browse/LOG4J2-2306
> Project: Log4j 2
>  Issue Type: Task
>  Components: Tests
>Reporter: Carter Kozak
>Assignee: Carter Kozak
>Priority: Major
>
> I'm curious if folks have experience using error prone.
> [http://errorprone.info/]
> I have applied the plugin locally and discovered a few minor issues (fixes 
> incoming shortly) but I wanted to discuss possibly applying error prone to 
> our standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (LOG4J2-2306) Investigate using Error Prone for Static Analysis

2018-04-04 Thread Carter Kozak (JIRA) 
Carter Kozak created LOG4J2-2306:


 Summary: Investigate using Error Prone for Static Analysis
 Key: LOG4J2-2306
 URL: https://issues.apache.org/jira/browse/LOG4J2-2306
 Project: Log4j 2
  Issue Type: Task
  Components: Tests
Reporter: Carter Kozak


I'm curious if folks have experience using error prone.

[http://errorprone.info/]

I have applied the plugin locally and discovered a few minor issues (fixes 
incoming shortly) but I wanted to discuss possibly applying error prone to our 
standard suite of tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (LOG4J2-2305) Log4j 2.10+not working with SLF4J 1.8 in OSGI environment

2018-04-04 Thread Rob Gansevles (JIRA) 
Rob Gansevles created LOG4J2-2305:
-

 Summary: Log4j 2.10+not working with SLF4J 1.8 in OSGI environment
 Key: LOG4J2-2305
 URL: https://issues.apache.org/jira/browse/LOG4J2-2305
 Project: Log4j 2
  Issue Type: Bug
Affects Versions: 2.11.0, 2.10.0
Reporter: Rob Gansevles


I have a simple osgi plugin that just logs something to slf4j Logger in the 
Activator's bundle start method.
When I install and start log4j-core-2.11.0.jar, log4j-api-2.11.0.jar, 
log4j-slf4j-impl-2.11.0.jar and slf4j-api-1.8.0-beta1.jar in a clean felix gogo 
shell, and then install and start my plugin, it prints the 
No-SLF4J-providers-were-found message.
 
 
It does work if I do the same with log4j  2.9.1 and slf4j-api-1.7.25.
 
You can find my simple plugin on github: 
[https://github.com/rgansevles/osgi-slf4j-sample]
 
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build became unstable: Log4j 2 2.x #3439

2018-04-04 Thread Apache Jenkins Server 
See

[jira] [Resolved] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Gregory resolved LOG4J2-2304.
--
   Resolution: Fixed
Fix Version/s: 2.11.1
   3.0.0

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
> Fix For: 3.0.0, 2.11.1
>
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425866#comment-16425866
 ] 

ASF subversion and git services commented on LOG4J2-2304:
-

Commit 74942b3bdb447fda6df0f11819fca85f7303c511 in logging-log4j2's branch 
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=74942b3 ]

[LOG4J2-2304] Log4j2 2.8.2 JMX unregister NullPointerException.

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425863#comment-16425863
 ] 

ASF subversion and git services commented on LOG4J2-2304:
-

Commit 66d0d231a1e4b096275170a45399c13f8647d72b in logging-log4j2's branch 
refs/heads/release-2.x from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=66d0d23 ]

[LOG4J2-2304] Log4j2 2.8.2 JMX unregister NullPointerException.

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425858#comment-16425858
 ] 

Gary Gregory commented on LOG4J2-2304:
--

As an aside it looks like {{com.caucho.jmx.AbstractMBeanServer.queryNames()}} 
might be returning {{null}} instead of an empty set.

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425856#comment-16425856
 ] 

Gary Gregory edited comment on LOG4J2-2304 at 4/4/18 4:57 PM:
--

To the team:

How does a line of code like this make sense, it feels like an unfinished 
refactoring:

{code:java}
final String search = String.format(StatusLoggerAdminMBean.PATTERN, 
escape(contextName), "*");
{code}
Where {{PATTERN}} is:
{code:java}
String PATTERN = Server.DOMAIN + ":type=%s,component=StatusLogger";
{code}
This means the second argument to {{String.format()}}, {{"\*"}}, is ignored. 
But we usually pass in {{"\*"}} anyway.

So it seems that the second argument should just be removed.

Thoughts?
 


was (Author: garydgregory):
To the team:

How does a line of code like this make sense, it feels like an unfinished 
refactoring:

{code:java}
final String search = String.format(StatusLoggerAdminMBean.PATTERN, 
escape(contextName), "*");
{code}
Where {{PATTERN}} is:
{code:java}
String PATTERN = Server.DOMAIN + ":type=%s,component=StatusLogger";
{code}
This means the second argument to {{String.format()}}, {{"*"}}, is ignored. But 
we usually pass in {{"*"}} anyway.

So it seems that the second argument should just be removed.

Thoughts?
 

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534]

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425856#comment-16425856
 ] 

Gary Gregory commented on LOG4J2-2304:
--

To the team:

How does a line of code like this make sense, it feels like an unfinished 
refactoring:

{code:java}
final String search = String.format(StatusLoggerAdminMBean.PATTERN, 
escape(contextName), "*");
{code}
Where {{PATTERN}} is:
{code:java}
String PATTERN = Server.DOMAIN + ":type=%s,component=StatusLogger";
{code}
This means the second argument to {{String.format()}}, {{"*"}}, is ignored. But 
we usually pass in {{"*"}} anyway.

So it seems that the second argument should just be removed.

Thoughts?
 

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425851#comment-16425851
 ] 

Gary Gregory commented on LOG4J2-2304:
--

Thank you for your report [~wu560130911]:
Please try:
- Version 2.11.0
- If that does not work, I've added a few null checks in the current version: 
2.11.1-SNAPSHOT
- Then report back to us with your findings :-)

Gary

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425823#comment-16425823
 ] 

ASF subversion and git services commented on LOG4J2-2304:
-

Commit 20cb63d746241a8f2a85ac7db5391c6ed209e051 in logging-log4j2's branch 
refs/heads/release-2.x from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=20cb63d ]

[LOG4J2-2304] Log4j2 2.8.2 JMX unregister NullPointerException. Avoid
some NPEs that don't seem like they should happen. Refactor the "*"
context name into a constant.

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (LOG4J2-2304) Log4j2 2.8.2 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Gregory updated LOG4J2-2304:
-
Summary: Log4j2 2.8.2 JMX unregister NullPointerException  (was: log4j2 2.8 
JMX unregister NullPointerException)

> Log4j2 2.8.2 JMX unregister NullPointerException
> 
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (LOG4J2-2304) log4j2 2.8 JMX unregister NullPointerException

2018-04-04 Thread Gary Gregory (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Gregory updated LOG4J2-2304:
-
Summary: log4j2 2.8 JMX unregister NullPointerException  (was: log4j2 2.8 
jmx unregister NullPointerException)

> log4j2 2.8 JMX unregister NullPointerException
> --
>
> Key: LOG4J2-2304
> URL: https://issues.apache.org/jira/browse/LOG4J2-2304
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
>Affects Versions: 2.8.2
>Reporter: wumengsheng
>Priority: Major
>
> 2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
> 2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
> org.apache.logging.log4j2:type=Default,component=StatusLogger 
> java.lang.NullPointerException
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
>  at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
>  at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
>  at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
>  at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
>  at java.lang.Thread.run(Thread.java:745)
>  
>  
> [2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
> java.lang.IllegalStateException: JMX context 
> EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
> [2018/04/04 14:07:07.534] at 
> com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
> [2018/04/04 14:07:07.534] at 
> org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
> [2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
> [2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2284) Logfile rolling broken with RollingFileAppender and TimeBasedTriggeringPolicy

2018-04-04 Thread Stephen Dawkins (JIRA) 

[ 
https://issues.apache.org/jira/browse/LOG4J2-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425520#comment-16425520
 ] 

Stephen Dawkins commented on LOG4J2-2284:
-

I'm having the same issues, with both TimeBasedTriggeringPolicy and 
CronTriggeringPolicy. Here's the debug output using TimeBasedTriggeringPolicy 
from my sample application:

{{2018-04-04 14:02:52,450 main DEBUG Setting prev file time to 
2018-04-04T14:02:52.418+0100}}
{{2018-04-04 14:02:52,450 main DEBUG Initializing triggering policy 
TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)}}
{{2018-04-04 14:02:52,450 main TRACE PatternProcessor.getNextTime returning 
2018/04/04-14:03:00.000, nextFileTime=2018/04/04-14:02:00.000, 
prevFileTime=1970/01/01-01:00:00.000, current=2018/04/04-14:02:52.450, 
freq=EVERY_MINUTE}}
{{2018-04-04 14:02:52,450 main TRACE PatternProcessor.getNextTime returning 
2018/04/04-14:03:00.000, nextFileTime=2018/04/04-14:02:00.000, 
prevFileTime=2018/04/04-14:02:00.000, current=2018/04/04-14:02:52.450, 
freq=EVERY_MINUTE}}
{{...}}
{{2018-04-04 14:02:53,573 main DEBUG Now writing to 
logs/requests.log.2018-04-04-14-02 at 2018-04-04T14:02:53.573+0100}}
{{2018-04-04 14:02:53,557 DEBUG foo  [main] hello: 2018-04-04 14:02:53}}
{{...}}
{{2018-04-04 14:02:58,643 DEBUG foo  [main] hello: 2018-04-04 14:02:58}}
{{2018-04-04 14:02:59,657 DEBUG foo  [main] hello: 2018-04-04 14:02:59}}
{{2018-04-04 14:03:00,671 main TRACE PatternProcessor.getNextTime returning 
2018/04/04-14:04:00.000, nextFileTime=2018/04/04-14:03:00.000, 
prevFileTime=2018/04/04-14:02:00.000, current=2018/04/04-14:03:00.671, 
freq=EVERY_MINUTE}}
{{2018-04-04 14:03:00,671 main DEBUG Rolling 
logs/requests.log.2018-04-04-14-02}}
{{2018-04-04 14:03:00,671 main DEBUG Found 0 eligible files, max is  
2147483647}}
{{2018-04-04 14:03:00,671 main TRACE DirectWriteRolloverStrategy.purge() took 
1.0 milliseconds}}
{{2018-04-04 14:03:00,671 main DEBUG Now writing to 
logs/requests.log.2018-04-04-14-02 at 2018-04-04T14:03:00.671+0100}}
{{2018-04-04 14:03:00,671 DEBUG foo  [main] hello: 2018-04-04 14:03:00}}
{{2018-04-04 14:03:01,685 DEBUG foo  [main] hello: 2018-04-04 14:03:01}}
{{...}}
{{2018-04-04 14:03:58,469 DEBUG foo  [main] hello: 2018-04-04 14:03:58}}
{{2018-04-04 14:03:59,483 DEBUG foo  [main] hello: 2018-04-04 14:03:59}}
{{2018-04-04 14:04:00,497 main TRACE PatternProcessor.getNextTime returning 
2018/04/04-14:05:00.000, nextFileTime=2018/04/04-14:04:00.000, 
prevFileTime=2018/04/04-14:03:00.000, current=2018/04/04-14:04:00.497, 
freq=EVERY_MINUTE}}
{{2018-04-04 14:04:00,497 main DEBUG Rolling 
logs/requests.log.2018-04-04-14-02}}
{{2018-04-04 14:04:00,497 main DEBUG Found 0 eligible files, max is  
2147483647}}
{{2018-04-04 14:04:00,497 main TRACE DirectWriteRolloverStrategy.purge() took 
1.0 milliseconds}}
{{2018-04-04 14:04:00,497 main DEBUG Now writing to 
logs/requests.log.2018-04-04-14-03 at 2018-04-04T14:04:00.497+0100}}
{{2018-04-04 14:04:00,497 DEBUG foo  [main] hello: 2018-04-04 14:04:00}}
{{2018-04-04 14:04:01,511 DEBUG foo  [main] hello: 2018-04-04 14:04:01}}
{{2018-04-04 14:04:02,525 DEBUG foo  [main] hello: 2018-04-04 14:04:02}}

The issue seems to be that prevFileTime is used for the filename as 
setCurrentFileTime is never called.

> Logfile rolling broken with RollingFileAppender and TimeBasedTriggeringPolicy
> -
>
> Key: LOG4J2-2284
> URL: https://issues.apache.org/jira/browse/LOG4J2-2284
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.10.0, 2.11.0
> Environment: Windows 10, Java 1.8.161
>Reporter: Hartmut Honisch
>Priority: Major
>
> I have a log4j config that uses RollingFileAppender with 
> TimeBasedTriggeringPolicy to create one logfile per minute (well in reality 
> it’s actually one logfile per day, but testing/reproducing the described 
> behaviour is easier when you don’t have to wait an entire day for the logfile 
> rolling to occur, and the bug described here applies to both rolling per day 
> and rolling per minute).
> I would expect that each logfile contains only log entries written within the 
> same minute that’s suggested by its filename, for example:
>  * Logfile app.2018-03-21_*10-00*.log  contains log messages starting with 
> timestamp 2018-03-21 *10:00*
>  * Logfile app.2018-03-21_*10-01*.log  contains log messages starting with 
> timestamp 2018-03-21 *10:01*
>  * Logfile app.2018-03-21_*10-02*.log  contains log messages starting with 
> timestamp 2018-03-21 *10:02*
>  * …
>  
> However that’s not the case:  When I start the application, the first logfile 
> created contains log messages from both the minute suggested by its filename 
> and the next minute, and all subsequent logfiles contain messages that are 
> off by 1

[jira] [Created] (LOG4J2-2304) log4j2 2.8 jmx unregister NullPointerException

2018-04-04 Thread wumengsheng (JIRA) 
wumengsheng created LOG4J2-2304:
---

 Summary: log4j2 2.8 jmx unregister NullPointerException
 Key: LOG4J2-2304
 URL: https://issues.apache.org/jira/browse/LOG4J2-2304
 Project: Log4j 2
  Issue Type: Bug
  Components: Configurators
Affects Versions: 2.8.2
Reporter: wumengsheng


2018-04-04 14:07:07,545 pool-2-thread-1 ERROR Could not unregister MBeans for 
org.apache.logging.log4j2:type=Default java.lang.NullPointerException
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
 at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
 at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
 at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
 at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
 at java.lang.Thread.run(Thread.java:745)

2018-04-04 14:07:07,548 pool-2-thread-1 ERROR Could not unregister MBeans for 
org.apache.logging.log4j2:type=Default,component=StatusLogger 
java.lang.NullPointerException
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:336)
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterStatusLogger(Server.java:288)
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:262)
 at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
 at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
 at org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
 at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
 at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
 at java.lang.Thread.run(Thread.java:745)

 

 

[2018/04/04 14:07:07.534] WARNING com.caucho.jmx.AbstractMBeanServer 
java.lang.IllegalStateException: JMX context 
EnvironmentClassLoader[web-app:http://localhost:8001] has been closed.
[2018/04/04 14:07:07.534] at 
com.caucho.jmx.EnvironmentMBeanServer.createContext(EnvironmentMBeanServer.java:101)
[2018/04/04 14:07:07.534] at 
com.caucho.jmx.GlobalMBeanServer.createContext(GlobalMBeanServer.java:77)
[2018/04/04 14:07:07.534] at 
com.caucho.jmx.AbstractMBeanServer.createContext(AbstractMBeanServer.java:77)
[2018/04/04 14:07:07.534] at 
com.caucho.jmx.GlobalMBeanServer.getView(GlobalMBeanServer.java:115)
[2018/04/04 14:07:07.534] at 
com.caucho.jmx.AbstractMBeanServer.queryNames(AbstractMBeanServer.java:551)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:259)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:247)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:338)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.LoggerContext$1.run(LoggerContext.java:279)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry$RegisteredCancellable.run(DefaultShutdownCallbackRegistry.java:109)
[2018/04/04 14:07:07.534] at 
org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.run(DefaultShutdownCallbackRegistry.java:74)
[2018/04/04 14:07:07.534] at java.lang.Thread.run(Thread.java:745)
[2018/04/04 14:07:07.534]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)