tracker issue : CF-3126106

select a category, or use search below
(searches all categories and all time range)
Title:

Errors from Tomcat dont get logged in start.log or exception.log

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Asha K S)

Created: 02/29/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Public Beta / 281673

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Mac 10 All,Win XP All

Vote Count: 1

Problem:When we start ColdFusion we are just logging the out stream but not the error stream.So the errors from Tomcat are not getting logged anywhere.

Method:Run the test case at \\blrstore.corp.adobe.com\builds\coldfusion\users\shilpi\ToAsha\hashcollision you will see that the error coldfusion.filter.FormScope$PostParametersLimitExceededException: POST parameter
s exceeds the maximum limit specified in the server. which comes from Tomcat doesnot get logged to start.log or exception.log.

Result:

Expected:We should be able to see the errors from Tomcat

Workaround:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3126106

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:

Attachments:

Comments:

+1, thanks. It'll be helpful to see all the errors. And probably even greater reason now for start.log to have it's own configurable 'maximum size' setting on CF Admin's logging page.
Vote by External U.
20493 | February 29, 2012 01:55:50 AM GMT