[
https://issues.apache.org/jira/browse/TOMEE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated TOMEE-1629:
--------------------------------------
Description:
Issue: logs are swallowed cause log4j2 shutdown hook is called before
undeployments of applications/shutdown of the container because both rely on
shutdown hooks and shutdown hooks execution ordering is not deterministic.
Adding log4j2-tomee module solves it - not done by default to avoid to break
conflict using the log4j2 SPI.
was:
Issue: logs are swallowed cause log4j2 shutdown hook is called before
undeployments of applications/shutdown of the container because both rely on
shutdown hooks.
Adding log4j2-tomee module solves it - not done by default to avoid to break
conflict using the log4j2 SPI.
> Implement a custom integration around log4j2
> org.apache.logging.log4j.core.util.ShutdownCallbackRegistry
> --------------------------------------------------------------------------------------------------------
>
> Key: TOMEE-1629
> URL: https://issues.apache.org/jira/browse/TOMEE-1629
> Project: TomEE
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Fix For: 7.0.0-M1
>
>
> Issue: logs are swallowed cause log4j2 shutdown hook is called before
> undeployments of applications/shutdown of the container because both rely on
> shutdown hooks and shutdown hooks execution ordering is not deterministic.
> Adding log4j2-tomee module solves it - not done by default to avoid to break
> conflict using the log4j2 SPI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
