You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Nathan Bubna <nb...@gmail.com> on 2005/08/20 01:06:15 UTC
Re: SEVERE: Error deploying web application archive simple.war
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 <sh...@gmail.com> 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 <sh...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
problems w/Tomcat 5.5.9 and VelocityTool project's use of commons-logging
Posted by Nathan Bubna <nb...@gmail.com>.
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 <sh...@gmail.com> 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 <sh...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Fwd: SEVERE: Error deploying web application archive simple.war
Posted by Nathan Bubna <nb...@gmail.com>.
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 <sh...@gmail.com> 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 <sh...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org