Re: [Dspace-tech] FW: Java heap space error when trying to update aCollection
Very interesting. I just changed our web server JVM options from: -Xms128m -Xmx256m To: -Xms128m -Xmx512m and it corrected the heap space error. I'm worried though, because we are getting ready to load thousands more documents into DSpace and I'm wondering at what point we will start getting this error again. I agree with François that it appears DSpace is cycling through every record in the Collection doing something (I'm not sure what since I was just updating the Collection description) and because there are 44,938 records in this Collection and the Java heap space was filled up. Sue From: François Parmentier [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2008 3:53 AM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] Java heap space error when trying to update a Collection Unfortunately, I agree with Susan. We have a 300K items collection that we cannot upgrade (only changing the description is not possible). It happens only on THAT collection (and not on the other ones in the same DSpace 1.4.2). I did not look far inside, but it seems that DSpace loads all the documents of the collection to be updated during the update! I'm not on that problem right now. -- François PARMENTIER / INIST-CNRS OpenSIGLE On Fri, Sep 26, 2008 at 11:13 PM, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] [EMAIL PROTECTED] wrote: Which memory settings might be too low? I'm thinking it has to be related to the increased number of records in our database since this is the first time I've ever seen the error and because it doesn't happen in our test instance (where our source code mirrors our production system). I can't imagine though, what could be happening in edit-communities where all we are trying to do is update one row in the collection table?? From: Mark Diggory [mailto:[EMAIL PROTECTED] On Behalf Of Diggory Mark Sent: Friday, September 26, 2008 5:09 PM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Cc: dspace-tech@lists.sourceforge.net; Smail, James W. (LARC-B702)[NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] Java heap space error when trying to update a Collection This can be caused by something else happening on the server. Basically your instance has used up its JVM heap space and any new calls into the system results in an OutOf Memory error. Of you can restart and try the task again, you may find that the issue is gone, if its still there, then you have an issue that being cause by your request more specifically. Monitor/Search your dspace logs and see if you have more occuarnces of this than this one case. It may either mean: 1.) your memory settings are too low. 2.) something is causing a memory leak, i.e. not releasing its resources or falling into infinite loops. -Mark On Sep 26, 2008, at 1:54 PM, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: I am getting an error while trying to update a Collection (collection name and description) - see below from dspace.log. This is the first time I've seen this error. The strange thing is that it doesn't happen in our Test instance - but our Test instance only has 101 Items in it. We've recently been adding lots of new items to our repository and our Item count is now at 90,490. This is kind of scary, since we have thousands and thousands more items we are planning on adding to DSpace in the next few months. We are currently running 1.4.2 and are planning to implement 1.5 soon. Can anyone help with this error? Thanks, Sue 2008-09-26 16:40:21,210 INFO org.dspace.eperson.PasswordAuthentication @ anonymous:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:authenticate:attempting password auth of [EMAIL PROTECTED] 2008-09-26 16:40:21,240 INFO org.dspace.eperson.PasswordAuthentication @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:authenticate:type=PasswordAuthentication 2008-09-26 16:40:21,270 INFO org.dspace.app.webui.servlet.PasswordServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:login:type=explicit 2008-09-26 16:40:21,288 INFO org.dspace.app.webui.servlet.MyDSpaceServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:view_mydspace: 2008-09-26 16:40:24,141 INFO org.dspace.app.webui.servlet.CommunityListServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:view_community_list: 2008-09-26 16:40:28,218 INFO org.dspace.app.webui.servlet.DSpaceServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119.152.109:view_collection:collection_id=35 2008-09-26 16:43:07,240 WARN
Re: [Dspace-tech] FW: Java heap space error when trying to update aCollection
We run Xmx at the JVM limit of 2048m in our [EMAIL PROTECTED] production. On Sep 29, 2008, at 11:59 AM, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: Very interesting. I just changed our web server JVM options from: -Xms128m –Xmx256m To: -Xms128m -Xmx512m and it corrected the heap space error. I’m worried though, because we are getting ready to load thousands more documents into DSpace and I’m wondering at what point we will start getting this error again. I agree with François that it appears DSpace is cycling through every record in the Collection doing something (I’m not sure what since I was just updating the Collection description) and because there are 44,938 records in this Collection and the Java heap space was filled up. Sue From: François Parmentier [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2008 3:53 AM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] Java heap space error when trying to update a Collection Unfortunately, I agree with Susan. We have a 300K items collection that we cannot upgrade (only changing the description is not possible). It happens only on THAT collection (and not on the other ones in the same DSpace 1.4.2). I did not look far inside, but it seems that DSpace loads all the documents of the collection to be updated during the update! I'm not on that problem right now. -- François PARMENTIER / INIST-CNRS OpenSIGLE On Fri, Sep 26, 2008 at 11:13 PM, Thornton, Susan M. (LARC-B702) [NCI INFORMATION SYSTEMS] [EMAIL PROTECTED] wrote: Which memory settings might be too low? I'm thinking it has to be related to the increased number of records in our database since this is the first time I've ever seen the error and because it doesn't happen in our test instance (where our source code mirrors our production system). I can't imagine though, what could be happening in edit-communities where all we are trying to do is update one row in the collection table….?? From: Mark Diggory [mailto:[EMAIL PROTECTED] On Behalf Of Diggory Mark Sent: Friday, September 26, 2008 5:09 PM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Cc: dspace-tech@lists.sourceforge.net; Smail, James W. (LARC-B702) [NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] Java heap space error when trying to update a Collection This can be caused by something else happening on the server. Basically your instance has used up its JVM heap space and any new calls into the system results in an OutOf Memory error. Of you can restart and try the task again, you may find that the issue is gone, if its still there, then you have an issue that being cause by your request more specifically. Monitor/Search your dspace logs and see if you have more occuarnces of this than this one case. It may either mean: 1.) your memory settings are too low. 2.) something is causing a memory leak, i.e. not releasing its resources or falling into infinite loops. -Mark On Sep 26, 2008, at 1:54 PM, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: I am getting an error while trying to update a Collection (collection name and description) – see below from dspace.log. This is the first time I've seen this error. The strange thing is that it doesn't happen in our Test instance – but our Test instance only has 101 Items in it. We've recently been adding lots of new items to our repository and our Item count is now at 90,490. This is kind of scary, since we have thousands and thousands more items we are planning on adding to DSpace in the next few months. We are currently running 1.4.2 and are planning to implement 1.5 soon. Can anyone help with this error? Thanks, Sue 2008-09-26 16:40:21,210 INFO org.dspace.eperson.PasswordAuthentication @ anonymous:session_id=3DF9C128D08B43905296703AB6278699:ip_addr=198.119. 152.109:authenticate:attempting password auth of [EMAIL PROTECTED] 2008-09-26 16:40:21,240 INFO org.dspace.eperson.PasswordAuthentication @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699 :ip_addr=198.119.152.109:authenticate:type=PasswordAuthentication 2008-09-26 16:40:21,270 INFO org.dspace.app.webui.servlet.PasswordServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699 :ip_addr=198.119.152.109:login:type=explicit 2008-09-26 16:40:21,288 INFO org.dspace.app.webui.servlet.MyDSpaceServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699 :ip_addr=198.119.152.109:view_mydspace: 2008-09-26 16:40:24,141 INFO org.dspace.app.webui.servlet.CommunityListServlet @[EMAIL PROTECTED]:session_id=3DF9C128D08B43905296703AB6278699 :ip_addr=198.119.152.109:view_community_list: 2008-09-26 16:40:28,218 INFO org.dspace.app.webui.servlet.DSpaceServlet @[EMAIL
Re: [Dspace-tech] FW: Java heap space error when trying to update aCollection
Sue, I'm not denying that there is an efficiency problem / bug in DSpace to be bombing out on a minor Collection change just because of the number of Items. But 256 / 512Mb really is virtually nothing these days. I can easily exceed that editing the DSpace source in an IDE. I'll regularly see my web browser running higher than that after I've been using it for a few hours. Admittedly, I'm running 24(?) DSpace instances in my Tomcat server - but it's on an 8Gb machine, running a 64-bit JVM, currently with a max heap of 4Gb. And these servers - with multi-cores and using commodity RAM - are amongst the cheapest you can buy these days. Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: Very interesting. I just changed our web server JVM options from: -Xms128m –Xmx*256*m To: -Xms128m -Xmx*512*m and it corrected the heap space error. I’m worried though, because we are getting ready to load thousands more documents into DSpace and I’m wondering at what point we will start getting this error again. I agree with François that it appears DSpace is cycling through every record in the Collection doing something (I’m not sure what since I was just updating the Collection description) and because there are 44,938 records in this Collection and the Java heap space was filled up. Sue This e-mail is confidential and should not be used by anyone who is not the original intended recipient. BioMed Central Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of BioMed Central Limited. No contracts may be concluded on behalf of BioMed Central Limited by means of e-mail communication. BioMed Central Limited Registered in England and Wales with registered number 3680030 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB This email has been scanned by Postini. For more information please visit http://www.postini.com - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
