https://bz.apache.org/bugzilla/show_bug.cgi?id=61717
Bug ID: 61717
Summary: Wepapp deployment errors are not logged to context log
Product: Tomcat 8
Version: 8.5.9
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: JULI
Assignee: dev@tomcat.apache.org
Reporter: s.kiesewet...@igniti.de
Target Milestone: ----
If one configures JULI (logging.properties) to log context-specific messages
using a separate handler (at least) wepapp-startup-errors are lost completely.
Those errors are whether logged to the context log nor the host log. The root
log just says:
"03-Nov-2017 12:21:54.237 SEVERE [localhost-startStop-1]
org.apache.catalina.core.StandardContext.startInternal One or more listeners
failed to start. Full details will be found in the appropriate container log
file
03-Nov-2017 12:21:54.237 SEVERE [localhost-startStop-1]
org.apache.catalina.core.StandardContext.startInternal Context [/myCtx] startup
failed due to previous errors".
Example:
When configuring logging.properies like:
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers =
2localhost.org.apache.juli.AsyncFileHandler
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myCtx].level =
INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myCtx].handlers
= 3manager.org.apache.juli.AsyncFileHandler
startup error of the webapp that belongs to context "myCtx" are lost
completely.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
