[
https://issues.apache.org/jira/browse/VELOCITY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585045#action_12585045
]
Norbert Pomaroli commented on VELOCITY-514:
-------------------------------------------
We also can reproduce this bug with both velocity-1.4 and velocity-1.5.
I attached a simple test case with a recursive macro (see the two comments
above).
Our test environment:
- Intel(R) Core(TM)2 Duo CPU based platform
- SMP linux kernel (2.6.24)
- Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode)
Maybe you need to run the test multiple times to reproduce the bug.
> 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.3.1, 1.4
> Reporter: Sam Chang
> Fix For: 1.5
>
> Attachments: macroSlammer-1.4.jar, macroSlammer-1.5.jar,
> macroSlammer.jar, nullAST.log, recursive.vm, slammer.vm, VeloMacroTest.java
>
>
> 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]
