Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368776

Summary: Consider adding -consolelog parameter in web.xml
Product: z_Archived Reporter: Ralf Sternberg <rsternberg>
Component: LibraAssignee: Project Inbox <libra.warproducts-inbox>
Status: NEW --- QA Contact: Holger Staudacher <holger.staudacher>
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Ralf Sternberg CLA 2012-01-16 16:16:36 EST 
Without the -consolelog commandline parameter, exceptions don't end up in the servlet container's log. They are written to some file at some obscure place, but the servlet container's log is the first place to look for in case of trouble. That's where exceptions should come up.

I'm not 100% sure about this suggestion, feel free to disagree.
Comment 1 Holger Staudacher CLA 2012-01-17 06:06:09 EST 
I partly disagree because the "obscure place" is the OSGi configuration area right? This is the normal location for the OSGi log. But while OSGi run inside a war file I think you are right that for a use the most intuitive place to look for the log is the container log. So, I will fix this for Juno M5.
Comment 2 Ralf Sternberg CLA 2012-01-17 08:51:31 EST 
Yes, that was exactly my thinking, thanks.

After all, users of the WAR product tooling can adjust their web.xml and cut out the -consolelog parameter if they prefer to keep the log files in the config area.  But for the first test deployments they're going to use the default - and that's where logged exceptions are most helpful.