Dear Robin, Hilton,

Thanks for your quick replies. I will also allocate the memory directly to 
tomcat, instead of setting java_opts as environment variable. 

Thanks, Francis
-----Oorspronkelijk bericht-----
Van: TAYLOR Robin [mailto:[email protected]] 
Verzonden: vrijdag 23 juli 2010 13:01
Aan: Brouns, Francis; '[email protected]'
Onderwerp: RE: Dspace out of memory errors

Hi Francis,

It's the memory allocated to Tomcat rather than the total available to the 
server that is the problem. The memory required by DSpace has increased over 
the years but there are no known memory leaks in 1.5 (there were in earlier 
versions). Since you have nothing else running on the machine allocate another 
gigabyte to Tomcat and see if that helps . We have up to 3G allocated to 
various installations although most are running more than one Dspace.

Cheers, Robin. 

Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808  

> -----Original Message-----
> From: Brouns, Francis [mailto:[email protected]] 
> Sent: 23 July 2010 10:48
> To: '[email protected]'
> Subject: [Dspace-tech] Dspace out of memory errors
> 
> Hi,
> 
> Last week we completed the upgrade of our DSpace 1.4.2 
> instance to DSpace 1.5.2, but now are encountering lots of 
> memory problems, which we did not encounter on our test server.
> 
> DSpace is installed on a SLES11 server, the Oracle database 
> is located at a different machine. We are running Tomcat6 
> (installed via Yast) and Sun Java 1.5 (installed via RPM). We 
> run the daily-digest, filter-media and the stats cronjob. 
> Apart from DSpace no other applications are running on this 
> server. We now assigned 6GB RAM to the server, and increased 
> java_opts to Xmx1024. In addition, Tomcat is restarted every 
> night. At first this seemed to help, but we are still running 
> into memory errors.
> 
> On our previous production server we also encountered these 
> kind of problems, but could solve them by adding additional 
> RAM to the server, increasing heapsize in java_opts and 
> restarting tomcat every night. This time this does not 
> prevent the errors.
> 
> Any tips on where I should look at to figure out what is 
> causing this, are welcome.
> 
> Exception:
> javax.servlet.ServletException: java.lang.OutOfMemoryError: 
> Java heap space
>       at 
> org.apache.jasper.runtime.PageContextImpl.doHandlePageExceptio
> n(PageContextImpl.java:852)
>       at 
> org.apache.jasper.runtime.PageContextImpl.handlePageException(
> PageContextImpl.java:781)
>       at org.apache.jsp.index_jsp._jspService(index_jsp.java:137)
>       at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>       at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.java:374)
>       at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:342)
>       at 
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>       at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
> er(ApplicationFilterChain.java:290)
>       at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
> cationFilterChain.java:206)
>       at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
> rapperValve.java:233)
>       at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardC
> ontextValve.java:191)
>       at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHost
> Valve.java:128)
>       at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
> Valve.java:102)
>       at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
> gineValve.java:109)
>       at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdap
> ter.java:286)
>       at 
> org.apache.coyote.http11.Http11Processor.process(Http11Process
> or.java:845)
>       at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle
> r.process(Http11Protocol.java:583)
>       at 
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.
> java:447)
>       at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.OutOfMemoryError: Java heap space
> 
> Kind regards,
> Francis Brouns
> 
> 
> --------------------------------------------------------------
> ----------------
> This SF.net email is sponsored by Sprint What will you do 
> first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> 
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to