Thanks for the response. This is what we're doing now. I was just wondering if there was a better way.
BAL ----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 7:00 PM Subject: Re: Too much log info in b3 > > > On Fri, 10 Jan 2003, Brian Lee wrote: > > > Date: Fri, 10 Jan 2003 18:23:37 -0500 > > From: Brian Lee <[EMAIL PROTECTED]> > > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Too much log info in b3 > > > > I just upgraded my app to the latest 1.1b3 release of struts. Now I am > > getting insane logging regardless of what I set ActionServlet's debug init > > param to in the web.xml. I've tried 0 yet I still get tons of debugging. > > > > The debug parameter is ignored in 1.1. > > > One possibility is that my app does set up a root hierarchy in log4j with a > > DEBUG priority, but I wouldn't think this would affect struts logging. > > > > That would be your cause. You certainly want to set a higher level than > DEBUG for the org.apache.struts (Struts core) and org.apache.commons > (Commons libraries) hierarchies. > > > Any ideas? > > > > Thanks, > > BAL > > Craig > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
