hey folks, i'm working on the VelocityTools project, and we've run into a bit of an issue with our mutual use of commons-logging. If you read the emails below, you'll see that the combination of Tomcat 5.5.9 and VelocityTools 1.1 (or 1.2-dev) create a nasty little infinite loop.
Apart from abandoning commons-logging, i'm at something of a loss here. Any ideas? We haven't had problems with this on earlier versions of Tomcat (5.0.30 and down). Thanks, nathan 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]
