Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | |||||||||||
0039800 | |||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
design defect | [Openbravo ERP] A. Platform | minor | always | 2018-12-13 17:19 | 2022-02-01 08:07 | ||||||
Reporter | jarmendariz | View Status | public | ||||||||
Assigned To | Triage Platform Base | ||||||||||
Priority | normal | Resolution | open | Fixed in Version | |||||||
Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
Projection | none | ETA | none | Target Version | |||||||
OS | Any | Database | Any | Java version | |||||||
OS Version | Database version | Ant version | |||||||||
Product Version | SCM revision | ||||||||||
Review Assigned To | |||||||||||
Web browser | |||||||||||
Modules | Core | ||||||||||
Regression level | |||||||||||
Regression date | |||||||||||
Regression introduced in release | |||||||||||
Regression introduced by commit | |||||||||||
Triggers an Emergency Pack | No | ||||||||||
Summary | 0039800: Log4j configuration is not found when shutting down Tomcat | ||||||||||
Description | During shutdown process the following error message appears in the logs: INFO: Stopping service Catalina 2018-12-13 17:15:07,914 localhost-startStop-1 ERROR No Log4j 2 configuration file found. Using default configuration (logging only errors to the console), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal initialization logging. See https://logging.apache.org/log4j/2.x/manual/configuration.html [^] for instructions on how to configure Log4j 2 It is caused by Weld, that creates a Logger object during context destroy just after log4j configuration is destroyed. As there is no log4j config file using their default names, configuration cannot be found and error appears to indicate the default one will be used. | ||||||||||
Steps To Reproduce | - Start Tomcat with Openbravo - Stop Tomcat - See the log file | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | issue-39800.patch [^] (2,336 bytes) 2018-12-13 17:23 [Show Content] | ||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0108593) jarmendariz (developer) 2018-12-13 17:25 |
This issue have been asked in Stack Overflow: https://stackoverflow.com/questions/53740087/logging-not-working-in-contextlistener-at-application-shutdown [^] Also, a minimal scenario to reproduce this bug have been created: https://github.com/katanagari7c1/tomcat-shutdown-test [^] |
Issue History | |||
Date Modified | Username | Field | Change |
2018-12-13 17:19 | jarmendariz | New Issue | |
2018-12-13 17:19 | jarmendariz | Assigned To | => platform |
2018-12-13 17:19 | jarmendariz | Modules | => Core |
2018-12-13 17:19 | jarmendariz | Triggers an Emergency Pack | => No |
2018-12-13 17:23 | jarmendariz | File Added: issue-39800.patch | |
2018-12-13 17:25 | jarmendariz | Note Added: 0108593 | |
2018-12-13 17:25 | jarmendariz | Relationship added | related to 0039504 |
2018-12-14 09:34 | alostale | Status | new => acknowledged |
2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base |
Copyright © 2000 - 2009 MantisBT Group |