Well, there are probably a few things:
-) If the issue belongs anywhere it is probably in the Tapestry jira.
-) While I can see ognl errors about missing classes I have no idea
what led up to these errors. For all I know you got a
java.lang.OutOfMemory exception in your app and this is the fal
What further information do you require over and above the bug report I
filed?
http://jira.opensymphony.com/browse/OGNL-120
Jesse Kuhnert wrote:
Hmmm... I think I'm going to need a lot more detailed information than
that. I'm sure something is broken but without knowing more it's not
somethin
Hmmm... I think I'm going to need a lot more detailed information than
that. I'm sure something is broken but without knowing more it's not
something I'm going to look in to.
On 9/11/07, Peter Stavrinides <[EMAIL PROTECTED]> wrote:
> Hi Jessie and co,
>
> I upgraded to the snapshot this morning
Hi Jessie and co,
I upgraded to the snapshot this morning at 6:00am GMT, deployed and tested. I
ran JConsole to monitor classes the whole day.. This evening I just had it
crash again 14 hours later. Doesn't appear to be fixed, I get the same errors.
I can see from your example that there may b
Thanks for the quick fix, will give it a try!
Peter
Renat Zubairov wrote:
Thanks Jesse!
Solution of this bug was a clear sign for us to switch to the latests
Tapestry version.
Would be very nice to have a new release ASAP that we can use it in production.
Renat
On 07/09/2007, Jesse Kuhnert
Thanks Jesse!
Solution of this bug was a clear sign for us to switch to the latests
Tapestry version.
Would be very nice to have a new release ASAP that we can use it in production.
Renat
On 07/09/2007, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> Short version:
>
> Some users have brought up wha
That's an awesome bug report... thx for all the hard work Jesse.
P.S. I thought you were supposed to be on vacation!
Jesse Kuhnert wrote:
Short version:
Some users have brought up what appears to be a genuine memory
consumption bug in the new OGNL expression compiling integration with
Tapestry
Short version:
Some users have brought up what appears to be a genuine memory
consumption bug in the new OGNL expression compiling integration with
Tapestry. The good news is that we think(hope) it has now been
addressed and fixed and would urge anyone experiencing any abnormally
high memory usa
