You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Wayne Baskin (JIRA)" <de...@velocity.apache.org> on 2011/01/28 01:17:43 UTC
[jira] Created: (VELOCITY-796) Velocity #parse not parsing content.
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
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
[jira] Resolved: (VELOCITY-796) Velocity #parse not parsing
content.
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-796.
-----------------------------------
Resolution: Duplicate
It's definitely not #parse that's the problem, if some of the content is parsed. And since it's a spotty occurence and your screenshot shows that all the "unparsed" output is macro calls, Sergiu is right on. It's a race condition in the local macro namespace. See VELOCITY-776 for full explanation and the options available to you for working around it until we get a proper fix.
> 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
[jira] Commented: (VELOCITY-796) Velocity #parse not parsing
content.
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988141#action_12988141 ]
Nathan Bubna commented on VELOCITY-796:
---------------------------------------
In case it isn't clear from my last comment on VELOCITY-776... Your options are:
a) turn on caching for your templates (big performance boost anyway)
b) stop using inline macros, make them global
> 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
[jira] Commented: (VELOCITY-796) Velocity #parse not parsing
content.
Posted by "Sergiu Dumitriu (JIRA)" <de...@velocity.apache.org>.
[ 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
[jira] Updated: (VELOCITY-796) Velocity #parse not parsing content.
Posted by "Wayne Baskin (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wayne Baskin updated VELOCITY-796:
----------------------------------
Attachment: Velocity Screen Shot.jpg
What is interesting is that not all the Velocity code has been output.
Comments and macros have been ignored, as well as a final line which calls a macro.
> 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
>
>
> 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
[jira] Updated: (VELOCITY-796) Velocity #parse not parsing content.
Posted by "Wayne Baskin (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wayne Baskin updated VELOCITY-796:
----------------------------------
Attachment: viewer.png
> 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