Costas Stergiou wrote:
>
> What do you mean that "I have run out of parsers"? Why this error
> occured only after a significant usage time? Does it have to do with memory
> consumption?
> Is it bad design of my code?
>
> I can update to the 1.0 version if this is a problem that is solved there,
> no problem.
> I just want to know if this is something that I can be sure that it will not
> happen
> again since this is a very critical system.
I saw a few messages go by on this, but I figured I would summarize...
There was a parser leak. When the system ran out, they would never come
back.
The problem has been solved in the 1.0 release. It is possible to
exhaust the pool, but Velocity will create more for you to use and let
you know via the log. We do not grow the parser pool when this happens,
but just create a new one, and let it get GC'd.
There is a configuration parameter that controls the number of parser
pools that are pre-created for you :
parser.pool.size
and the default is 20. You can change this in your properties /
configuration if you want.
The 1.1 release will have the option of letting the parser pool grow.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
