Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0039800
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformminoralways2018-12-13 17:192022-02-01 08:07
ReporterjarmendarizView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0039800: Log4j configuration is not found when shutting down Tomcat

DescriptionDuring 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
TagsNo tags attached.
Attached Filespatch file icon issue-39800.patch [^] (2,336 bytes) 2018-12-13 17:23 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0039504 closedjarmendariz Upgrade Log4j to version 2 

-  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
Powered by Mantis Bugtracker