Costas Stergiou wrote:
>
> Actually, once this error occured, nothing worked after that. I had to
> restart tomcat. I don't really have a large number of concurrent users,
> I only have quite big templates.. (many many loops, etc).
> I think that this pool may have a leak somewhere, e.g. something is not
> returned/released correctly.
The parser fix has been tested under heavy load and appears
to work correctly. The SimplePool class is 100 lines long, and
if you have many loops (possibly with some #parse directives in them?)
then it is possible with older versions of velocity that you will
run out of parsers.
> Also, once this error occured, it appeared in all templates (even the
> simplest ones, e.g. navigations (in Turbine world).
>
> The point I am worried so much is that we now build an application
> based on velocity that is expected to have thousands of concurrent
> users (it may grow too popular) and it's all based on Turbine+Velocity.
> It is important to know if there is any problem here (the investmenet
> is very big).
I wouldn't get too worried, as far as I know you are only the second
person to report the "running out of parsers" problem. Even with that
problem your app ran for a month :-) But seriously, I think if you try
the new version you'll find that your problem is fixed and your app
should run without a problem.
We can only try to make Velocity bullet-proof but we need all the
eyeballs we can get. We can never guarantee that things will always
be perfect, that's just not the way this works ...
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://tambora.zenplex.org
