aspose file tools*
The moose likes Struts and the fly likes Memory Out of bounds Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Frameworks » Struts
Bookmark "Memory Out of bounds" Watch "Memory Out of bounds" New topic
Author

Memory Out of bounds

az ziz
Ranch Hand

Joined: Dec 17, 2008
Posts: 50
dear all,

i have a customized RequestProcessor which will clone (for backup) each of the bean generated for the request and keep it in the session in an arraylist. to the maximum only 2 cloned beans can exists, others are removed periodically from the arraylist. this customrequestprocessor works to the core of the project arch to keep the beans for a special situation. our project's transaction pages uses various beans and VOs to store data and they keep the beans in the session for managing the data along different pages. the beans and VOs may have more data compared to the ActionForm bean, as this may contain only the field values of the pages.

The question is,
is the cloning of the ActionForm bean was the main reason that causes the outofmemory exeception? the exception is thrown whenever the deployment is done in the server. every time the server needs to be restarted manually for this problem?

I use BeanUtils for cloning and property copying.

can the reason be, as the customrequestprocessor was working to the core, there might be some request that are being served by the processor, in the mean time when a new class file was over written in the name of deployment, the server crashes. or something similar to this. i also have found this situation when i manually replace the customrequestprocessor class file in the server rather deploying while anyone (testing?) working on our web application.

Thanks

Vijay Veeraraghavan
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

The question is, is the cloning of the ActionForm bean was the main reason that causes the outofmemory exeception?

I'm not sure how we could answer that question without any more information. I seriously doubt it, but not knowing anything about your request processor, the size of the beans, etc. it's impossible to say.

Since the error happens only on redeployment it's very unlikely.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Memory Out of bounds
 
Similar Threads
Urgent: Howz stateful diff frm entity beans
HttpSession vs Stateful Session EJB
My SCEA Part 1Study Notes
Creating a custom scope... (kinda long)
performance issue with large collections of data