[
https://issues.apache.org/jira/browse/VELOCITY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Chang updated VELOCITY-514:
-------------------------------
Attachment: nullAST.log
macroSlammer.jar
Attached macroSlammer.jar which reproduces the errors by queuing up multiple
threads to render from a velocity template file.
Also attached nullAST.log with the errors
Requirements:
Java 1.5
Multiple CPU's
To run:
java -jar macroSlammer.jar
This will create velocity.log which contains the error. You may need to run it
several times to reproduce.
(I found it to be reproduceable atleast 1 in 2 tries)
> Rendering a template with inline macro concurrently causes VM error : Null AST
> ------------------------------------------------------------------------------
>
> Key: VELOCITY-514
> URL: https://issues.apache.org/jira/browse/VELOCITY-514
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.4
> Reporter: Sam Chang
> Attachments: macroSlammer.jar, nullAST.log
>
>
> If a template with inline macro is rendered concurrently it prints the
> following errors in the log:
> ERROR [velocity] VM #myInlineMacro: error : too few arguments to macro.
> Wanted 3 got 0
> ERROR [velocity] VM error : myInlineMacro. Null AST
> and where the expected output of the inline macro is, it has the string
> values of the arguments passed to the macro in brackets
> eg:
> #myInlineMacro('Arg1' 'arg2' 'arg3')
> gives the following on above error
> (Arg1 arg2 arg3)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
