I'm pretty sure we don't have a setting like that.

On Mon, Dec 14, 2020 at 8:01 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> All,
>
> We recently suffered an OOME in production because we had a huge SQL
> query return a log of data which, in turn, generated even more HTML
> output for a particular screen.
>
> We got an OOME with ASTNode.render trying to call StringWriter.write
> (which calls StringBuffer's auto-re-sizing) because the output string
> simply grew too much.
>
> We are of course fixing the SQL query to make sure we limit the amount
> of data that can come back, but we'd also like to make sure that
> Velocity doesn't trigger an OOME like this if possible.
>
> Is there a setting for limiting the output buffer size? I haven't yet
> found one in the documentation, so I'm starting to look in the code.
>
> Thanks,
> -chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
> For additional commands, e-mail: dev-h...@velocity.apache.org
>
>

Reply via email to