You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2017/11/03 11:28:40 UTC
[Bug 61717] New: Wepapp deployment errors are not logged to context
log
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.kiesewetter@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61717] Wepapp deployment errors are not logged to context log
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61717
s.kiesewetter@igniti.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |s.kiesewetter@igniti.de
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61717] Wepapp deployment errors are not logged to context log
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61717
s.kiesewetter@igniti.de changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
Hardware|PC |All
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61717] Wepapp deployment errors are not logged to context log
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61717
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
I can't reproduce this.
If you still see this issue please provides the steps to reproduce this on a
clean install of the latest 8.5.x release.
I suggest reproduce this by making the minimal necessary changes to the web.xml
of the host-manager app.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org