ok, i know this is a late response. i'm just now recovering from a crazy year and trying to get some things done around here. this one looks nasty. Shinobu, your assessment seems right on. the stack trace in my tomcat console window repeats a mix of commons-logging calls and tomcat and velocity calls to commons-logging. ugh, that ain't nice at all.
i might have to ping the tomcat-user list to see if anyone there has a bright idea... On 6/2/05, Shinobu Kawai <[EMAIL PROTECTED]> wrote: > > I got an OutOfMemoryError. :( > > Looks like commons-logging is part of the cause. It works if you > > remove the commons-logging.properties from the classes directory. > > ## Need to look furthur into this... > > 1. VVS sets Velocity to output logs to the Servlet logger > 2. commons-logging.properties sets logs to commons-logging to be > handled by Velocity. (This was meant for logs by commons-digester.) > > And I guess that Tomcat outputs Servlet logs using commons-logging. > (Haven't checked that, though.) > > Best regards, > -- Shinobu > > -- > Shinobu Kawai <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
