That's rather strange, but I think it's related to how quickly the JVM is
cycled through in forked tests and isn't anything to worry about. :)
On 20 June 2017 at 20:08, Gary Gregory wrote:
> I fixed the NPE, now you just get the "real" exception:
>
> ERROR StatusLogger Cannot start ShutdownCallb
I fixed the NPE, now you just get the "real" exception:
ERROR StatusLogger Cannot start ShutdownCallbackRegistry, already shutting
down.
ERROR StatusLogger Unable to create class
org.apache.logging.log4j.core.impl.Log4jContextFactory specified in
provider URL null
java.lang.IllegalStateException:
Doesn't sound too serious. Probably had the process killed before it fully
shut down.
On 19 June 2017 at 21:53, Gary Gregory wrote:
> Hi All:
>
> I just saw this go by with a local build:
>
> [INFO] Running org.apache.logging.log4j.core.Log4j1222Test
> [INFO] Tests run: 1, Failures: 0, Errors: 0
Hi All:
I just saw this go by with a local build:
[INFO] Running org.apache.logging.log4j.core.Log4j1222Test
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.002 s - in org.apache.logging.log4j.core.Log4j1222Test
ERROR StatusLogger Cannot start ShutdownCallbackRegistry, al
