"velocimacro.permissions.allow.inline.local.scope" makes VelocityEngine not
threadsafe
--------------------------------------------------------------------------------------
Key: VELOCITY-776
URL: https://issues.apache.org/jira/browse/VELOCITY-776
Project: Velocity
Issue Type: Bug
Components: Engine
Affects Versions: 1.6.4
Environment: Sun java jdk1.6.0_21, Ubuntu 10.04
Reporter: Simon Kitching
The attached unit test shows that when
"velocimacro.permissions.allow.inline.local.scope" is set to true, and multiple
threads use the same VelocityEngine instance then macros sometimes don't get
expanded and the #macroname call remains in the output text.
Notes:
* running test method "testMultipleEvals" (single threaded case) always succeeds
* running test method "testMultiThreadMultipleEvals" always fails
* commenting out the allow.inline.local.scope line makes the multithread test
pass (but of course has other side-effects)
Interestingly, for the multithread case it seems that 1 thread always succeeds
and N-1 threads fail.
--
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]
