You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Sergiu Dumitriu (JIRA)" <de...@velocity.apache.org> on 2011/01/28 11:57:43 UTC

[jira] Commented: (VELOCITY-796) Velocity #parse not parsing content.

    [ https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988029#action_12988029 ] 

Sergiu Dumitriu commented on VELOCITY-796:
------------------------------------------

We've encountered this occasionally for a long time (1.6, and I think 1.5 as well), but it was pretty rare, and a refresh usually solved the problem until the next time. If I remember correctly, I think I did a little debugging a while ago and the problem was with parallel requests trying to add the same macro namespace in the macro cache.

> Velocity #parse not parsing content.
> ------------------------------------
>
>                 Key: VELOCITY-796
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-796
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.7
>         Environment: Linux Server running Apache Web Server  in front of a JBoss 5 Application Server
>            Reporter: Wayne Baskin
>         Attachments: Velocity Screen Shot.jpg, viewer.png
>
>
> The issue is occuring randomly and could be load related.
> The issue has only appeared since upgrading to Version 1.7.
> The parse element will display all Velccity code it was suppose to parse.
> I have a screen shot if required.

-- 
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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org