You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Aaron Mulder <am...@alumni.princeton.edu> on 2006/08/01 00:49:19 UTC
1.1.1-SNAPSHOT Memory Problems
Jeff just noted that Liferay seems to take an abnormal amount of memory to run.
I just redeployed the console twice and got an OutOfMemoryError.
When working on the console for 1.1, I could redeploy dozens of times.
I think we've introduced a pretty serious memory problem between 1.1
and now. I know we're close to the deadline, but I think we ought to
investigate this before shipping 1.1.1.
Thanks,
Aaron
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by Jeff Genender <jg...@apache.org>.
Nice work Kevan. I got Liferay enterprise to run fine now ;-)
Jeff
Kevan Miller wrote:
>
> On Jul 31, 2006, at 10:45 PM, Matt Hogstrom wrote:
>
>> Concur...blocked.
>>
>> Aaron Mulder wrote:
>>> Jeff just noted that Liferay seems to take an abnormal amount of
>>> memory to run.
>>> I just redeployed the console twice and got an OutOfMemoryError.
>>> When working on the console for 1.1, I could redeploy dozens of times.
>>> I think we've introduced a pretty serious memory problem between 1.1
>>> and now. I know we're close to the deadline, but I think we ought to
>>> investigate this before shipping 1.1.1.
>
> OK. I've found the cause -- it's RC 425160
> (http://svn.apache.org/viewvc?view=rev&revision=425160). Looks like we
> were running out of PermGen space. This change roughly double the number
> of classes created by G on startup. I could only deploy/undeploy
> DayTrader once. After reverting the change, I've run well over 100
> deploy/undeploy cycles. We're leaking two instances of
> 'EDU.oswego.cs.dl.util.concurrent.LinkedNode' per deploy/undeploy, but
> that's only 32 bytes...
>
> I haven't confirmed, but I saw evidence that it was at least part of the
> DWR leaks that Jeff G reported.
>
> Here's the Jira associated with the above change --
> http://issues.apache.org/jira/browse/GERONIMO-2204
>
> Since the change is optional, I'm reverting the commit. I think we can
> safely leave out of 1.1.1. Can discuss how we want to fix, later...
>
> --kevan
>
>
>
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by Kevan Miller <ke...@gmail.com>.
On Jul 31, 2006, at 10:45 PM, Matt Hogstrom wrote:
> Concur...blocked.
>
> Aaron Mulder wrote:
>> Jeff just noted that Liferay seems to take an abnormal amount of
>> memory to run.
>> I just redeployed the console twice and got an OutOfMemoryError.
>> When working on the console for 1.1, I could redeploy dozens of
>> times.
>> I think we've introduced a pretty serious memory problem between 1.1
>> and now. I know we're close to the deadline, but I think we ought to
>> investigate this before shipping 1.1.1.
OK. I've found the cause -- it's RC 425160 (http://svn.apache.org/
viewvc?view=rev&revision=425160). Looks like we were running out of
PermGen space. This change roughly double the number of classes
created by G on startup. I could only deploy/undeploy DayTrader once.
After reverting the change, I've run well over 100 deploy/undeploy
cycles. We're leaking two instances of
'EDU.oswego.cs.dl.util.concurrent.LinkedNode' per deploy/undeploy,
but that's only 32 bytes...
I haven't confirmed, but I saw evidence that it was at least part of
the DWR leaks that Jeff G reported.
Here's the Jira associated with the above change -- http://
issues.apache.org/jira/browse/GERONIMO-2204
Since the change is optional, I'm reverting the commit. I think we
can safely leave out of 1.1.1. Can discuss how we want to fix, later...
--kevan
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Concur...blocked.
Aaron Mulder wrote:
> Jeff just noted that Liferay seems to take an abnormal amount of memory
> to run.
>
> I just redeployed the console twice and got an OutOfMemoryError.
>
> When working on the console for 1.1, I could redeploy dozens of times.
> I think we've introduced a pretty serious memory problem between 1.1
> and now. I know we're close to the deadline, but I think we ought to
> investigate this before shipping 1.1.1.
>
> Thanks,
> Aaron
>
>
>
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by Kevan Miller <ke...@gmail.com>.
Agreed. I'm seeing problems during TCK runs, also. We've obviously
regressed somewhere. I'm pretty sure it's happened in the last two
weeks (or at least one of the problems was created in the last two
weeks).
I've already started looking at the Jira Jeff raised -- GERONIMO-2240.
--kevan
On Jul 31, 2006, at 6:56 PM, Jeff Genender wrote:
> Yep..I concur...this is a nasty one and we need to see whats up. This
> is a blocker IMHO..
>
> Jeff
>
> Aaron Mulder wrote:
>> Jeff just noted that Liferay seems to take an abnormal amount of
>> memory
>> to run.
>>
>> I just redeployed the console twice and got an OutOfMemoryError.
>>
>> When working on the console for 1.1, I could redeploy dozens of
>> times.
>> I think we've introduced a pretty serious memory problem between 1.1
>> and now. I know we're close to the deadline, but I think we ought to
>> investigate this before shipping 1.1.1.
>>
>> Thanks,
>> Aaron
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Yeah, a blocker. As a sanity check, do we get the same problem off of
trunk?
Regards,
Alan
Jeff Genender wrote:
> Yep..I concur...this is a nasty one and we need to see whats up. This
> is a blocker IMHO..
>
> Jeff
>
> Aaron Mulder wrote:
>
>> Jeff just noted that Liferay seems to take an abnormal amount of memory
>> to run.
>>
>> I just redeployed the console twice and got an OutOfMemoryError.
>>
>> When working on the console for 1.1, I could redeploy dozens of times.
>> I think we've introduced a pretty serious memory problem between 1.1
>> and now. I know we're close to the deadline, but I think we ought to
>> investigate this before shipping 1.1.1.
>>
>> Thanks,
>> Aaron
>>
Re: 1.1.1-SNAPSHOT Memory Problems
Posted by Jeff Genender <jg...@apache.org>.
Yep..I concur...this is a nasty one and we need to see whats up. This
is a blocker IMHO..
Jeff
Aaron Mulder wrote:
> Jeff just noted that Liferay seems to take an abnormal amount of memory
> to run.
>
> I just redeployed the console twice and got an OutOfMemoryError.
>
> When working on the console for 1.1, I could redeploy dozens of times.
> I think we've introduced a pretty serious memory problem between 1.1
> and now. I know we're close to the deadline, but I think we ought to
> investigate this before shipping 1.1.1.
>
> Thanks,
> Aaron