Bugs item #1174342, was opened at 2005-03-31 12:56 Message generated for change (Settings changed) made by tdonohue You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=1174342&group_id=19984
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: iyoung (iyoung) Assigned to: Nobody/Anonymous (nobody) Summary: Potencial Memory Issue for a large collection Initial Comment: I have reported a memory problem in Items Mapper (tracking no. 1173600) yesterday. I then searched for "collection.getItems" in the DSPACE project and found additional java source code containing the similar code under: ItemExport.java PolicySet.java HistoryManager.java ItemMapServlet.java ( I mentioned in my previous bug report) This is or will be a problem as we adding more items to a collection. It appears that the "collection.getItems" gets all items from the collection and then excute "i.next()" which creates two huge arraylist, dublinCore and Bundles in Item.java. I received an out of memory error. In our case, we have almost 19,000 items in one collection, which our librarians prefer to keep this way. Could anyone look into this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=1174342&group_id=19984 ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
