You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Azhaguramanhjam, Ramkumar " <ra...@citi.com> on 2009/02/04 16:39:23 UTC
Memory Leak and Trinidad Pagination
Hi
This is regarding the usage of memory (Page Flow Scope) in Trinidad
Pagination.I have a Custom Implementation by which each time it goes to
database to fetch records but I see a problem as mentioned below
Iam checking the memory leaks in session when I use the pagination. On
each click of Next/Previous or Range Change
iam seeing an increase of 21 bytes of memory. I think for each action a
token is put on a HashMap. This is never cleaned up until the session is
invalidated(user logs off).
Can this thing be cleaned up?
On First Click of Next:(memory uage -537 bytes)
org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items:
'{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
AttributeComponentChange@1e2e1e2e]}}' 537
After clicking Next twice iam seeing memory usage got increased by 42
bytes (now 579 bytes)
org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items:
'{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
AttributeComponentChange@1e2e1e2e, org.apache.myfaces.trinidad.change.
AttributeComponentChange@2b5c2b5c, org.apache.myfaces.trinidad.change.
AttributeComponentChange@5f3a5f3a]}}' 579
Note:
Here :_id4 represents the
org.apache.myfaces.trinidad.component.core.data.CoreTable
Thanks
Ramkumar A
Phone:410-986-4672
RE: Memory Leak and Trinidad Pagination
Posted by "Azhaguramanhjam, Ramkumar " <ra...@citi.com>.
Is there anyway I can get the pageflowscope objects for a particular
request?
_____
From: Blake Sullivan [mailto:blake.sullivan@oracle.com]
Sent: Wednesday, February 04, 2009 10:53 AM
To: MyFaces Development
Subject: Re: Memory Leak and Trinidad Pagination
This is because the current ChangeManager implementation doesn't
collapse AttributeComponentChanges for a change to the same attribute on
the same component.
-- Blake Sullivan
Azhaguramanhjam, Ramkumar said the following On 2/4/2009 7:39 AM PT:
Hi
This is regarding the usage of memory (Page Flow Scope) in Trinidad
Pagination.I have a Custom Implementation by which each time it goes to
database to fetch records but I see a problem as mentioned below
Iam checking the memory leaks in session when I use the pagination. On
each click of Next/Previous or Range Change
iam seeing an increase of 21 bytes of memory. I think for each action a
token is put on a HashMap. This is never cleaned up until the session is
invalidated(user logs off).
Can this thing be cleaned up?
On First Click of Next:(memory uage -537 bytes)
org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items:
'{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
AttributeComponentChange@1e2e1e2e]}}' 537
After clicking Next twice iam seeing memory usage got increased by 42
bytes (now 579 bytes)
org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1 items:
'{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
AttributeComponentChange@1e2e1e2e, org.apache.myfaces.trinidad.change.
AttributeComponentChange@2b5c2b5c, org.apache.myfaces.trinidad.change.
AttributeComponentChange@5f3a5f3a]}}' 579
Note:
Here :_id4 represents the
org.apache.myfaces.trinidad.component.core.data.CoreTable
Re: Memory Leak and Trinidad Pagination
Posted by Blake Sullivan <bl...@oracle.com>.
This is because the current ChangeManager implementation doesn't
collapse AttributeComponentChanges for a change to the same attribute on
the same component.
-- Blake Sullivan
Azhaguramanhjam, Ramkumar said the following On 2/4/2009 7:39 AM PT:
>
> Hi
>
> This is regarding the usage of memory (Page Flow Scope) in Trinidad
> Pagination.I have a Custom Implementation by which each time it goes
> to database to fetch records but I see a problem as mentioned below
>
> Iam checking the memory leaks in session when I use the pagination. On
> each click of Next/Previous or Range Change
>
> iam seeing an increase of 21 bytes of memory. I think for each action
> a token is put on a HashMap. This is never cleaned up until the
> session is invalidated(user logs off).
>
> Can this thing be cleaned up?
>
> On First Click of Next:(memory uage -537 bytes)
>
> org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1
> items:
> '{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
> AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
> AttributeComponentChange@1e2e1e2e]}}' 537
>
> After clicking Next twice iam seeing memory usage got increased by 42
> bytes (now 579 bytes)
>
> org.apache.myfaces.trinidadinternal.Change (java.util.HashMap) 1
> items:
> '{/jsf/zipPaginate.jspx={_id4:_id4=[org.apache.myfaces.trinidad.change.
> AttributeComponentChange@5dea5dea, org.apache.myfaces.trinidad.change.
> AttributeComponentChange@1e2e1e2e, org.apache.myfaces.trinidad.change.
> AttributeComponentChange@2b5c2b5c, org.apache.myfaces.trinidad.change.
> AttributeComponentChange@5f3a5f3a]}}' 579
>
>
>
> Note:
>
> Here :_id4 represents the
> org.apache.myfaces.trinidad.component.core.data.CoreTable
>
>
>
> Thanks
>
> Ramkumar A
>
> Phone:410-986-4672
>
>
>