Bug 111589 - Setting log4j level on c.a.web.BaseServlet to DEBUG breaks everything
Summary: Setting log4j level on c.a.web.BaseServlet to DEBUG breaks everything
Keywords:
Status: CLOSED DUPLICATE of bug 111040
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-05 19:32 UTC by Matthew Booth
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Matthew Booth 2003-12-05 19:32:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4)
Gecko/20030701 Epiphany/1.0

Description of problem:
When you turn the log4j level of com.arsdigita.web.BaseServlet to
DEBUG, every page is returned with and error and:

CCM issue report code: null

null


Version-Release number of selected component (if applicable):
Rickshaw

How reproducible:
Always

Comment 1 Jon Orris 2003-12-05 20:19:39 UTC
Matt,
Is there anything in the webserver/ccm logs? This may be a duplicate
of bug 111040


Comment 2 Matthew Booth 2003-12-06 09:24:38 UTC
Yes, this is a duplicate. The same stack trace is output is sent to
error.log. For some reason nothing is sent to the regular logs.
Presumably that's a different bug :)

Comment 3 Richard Li 2003-12-06 12:23:56 UTC

*** This bug has been marked as a duplicate of 111040 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:00:18 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.