I am actually using Velocity 1.6.3.  I guess it is the same.  You
mentioned check out from trunk which is why I am asking.

Thanks,
Jason Tesser
dotCMS Lead Development Manager
1-305-858-1422



On Mon, Sep 13, 2010 at 10:24 AM, Nathan Bubna <nbu...@gmail.com> wrote:
> yes, assuming you've checked out the Velocity Engine trunk and put
> javacc 5 somewhere on your computer, you just need to set the
> javacc.home property in your build.properties to point to javacc and
> then do the "ant parser" task.  After that, i usually have to put an
> "import org.apache.velocity.runtime.parser.node.Node;" line back into
> the top of the JJTParserState.java class, which is an obnoxious little
> thing that i've meant to fix for years and never gotten around too
> (sorry).
>
> let me know how it goes.  i haven't tried JavaCC 5 out yet.
>
> On Mon, Sep 13, 2010 at 7:10 AM, Jason Tesser <jasontes...@gmail.com> wrote:
>> Nathan how do I build the parser?
>>
>> Is there an ant task for it or something?
>>
>> I actually already increased my pool to 100
>>
>> Thanks,
>> Jason Tesser
>> dotCMS Lead Development Manager
>> 1-305-858-1422
>>
>>
>>
>> On Mon, Sep 13, 2010 at 10:07 AM, Nathan Bubna <nbu...@gmail.com> wrote:
>>> On Mon, Sep 13, 2010 at 6:56 AM, Jason Tesser <jasontes...@gmail.com> wrote:
>>>> I have a bunch of parses happening from 90 or so threads.  Actually it
>>>> starts at 15 then grows.
>>>>
>>>> The issue is everytime I pause a java thread or do a threaddump I
>>>> notice that they are all stuck in the Parser line 3391
>>>>
>>>> if (jj_la == 0 && jj_scanpos == jj_lastpos) throw jj_ls;
>>>
>>> that seems like a random line to be so consistently stuck at.
>>>
>>>> Is this normal?  Any config or anything I could change here to help.
>>>> My files are taking so long to parse pretty much the whole system
>>>> hangs.
>>>
>>> You could try boosting the parser.pool.size property.   But mostly
>>> this is JavaCC produced code, so we don't really have any config hooks
>>> down into it.  If you're feeling up to a little hacking, you could try
>>> rebuilding Velocity with a JavaCC 5.0 generated parser.  The current
>>> release (1.6.4) was built with JavaCC 4.1.  They may have improved
>>> something that can help...
>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
>>>> For additional commands, e-mail: user-h...@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
>>> For additional commands, e-mail: user-h...@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
>> For additional commands, e-mail: user-h...@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
> For additional commands, e-mail: user-h...@velocity.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org

Reply via email to