Dear all,
We found in our DSpace installation (XMLUI) that JAVA uses a lot of memory
for just a few items added in DSpace.
Also, from time to time DSpace freeze the tomcat process and we have to kill
it.
Do you have some suggestions about this issues?
See bellow Java information from
My experience has been that, when Tomcat freezes and has to be killed,
it's run out of PermGen, which is a different pool than the main
heap. Indeed, tuning up PermGen accounts for most of the time I've
spent making Tomcat run well.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Al 09/02/12 13:37, En/na Gabriel Dina ha escrit:
Dear all,
We found in our DSpace installation (XMLUI) that JAVA uses a lot of
memory for just a few items added in DSpace.
Also, from time to time DSpace freeze the tomcat process and we have to
kill it.
Do you have some suggestions about
I have had this exact problem while running on windows. After switching
to linux I ran into it again and fixed it with the following command:
Export CATALINA_OPTS=-Xms1025m -Xmx1024m -XX:MaxPermSize=512m
Honestly, I do not know what Xms and Xmx really stand for or what their
purpose is. My
All,
To Matt's point, we have a few performance tuning recommendations posted
up in the Wiki Docs at:
https://wiki.duraspace.org/display/DSDOC18/Performance+Tuning+DSpace
This page provides hints on how give DSpace more memory to work with if
you keep encountering out-of-memory issues.
On Thu, 9 Feb 2012, Gabriel Dina wrote:
We found in our DSpace installation (XMLUI) that JAVA uses a lot of memory
for just a few items added in DSpace.
Even in the JSPUI there are memory leaks.
We have a nightly cronjob which restarts Tomcat to address the issue, even
though we fixed
Dear all,
Our error log was referring to the PermGen, so after we have increased the
Java memory up to 2 GB and PermSize/PermGen to 256MB, the Tomcat began to be
more responsive and it stopped to freeze (until now).
I'll let you know how things are going.
Thanks and regards,
Gabriel
I found the docs in the email archive that showed me the solr issue was the
setting for localhost. So I can get to solr via the actual localhost ok.
But I'm still puzzled by the 404 error for SWORD, OAI, LNI.
Pointers?
Thanks.
Bobb Menk
-Original Message-
From: Menk, Robert - 1150 -
On Thu, Feb 9, 2012 at 18:29, Menk, Robert - 1150 - MITLL
bm...@ll.mit.edu wrote:
I found the docs in the email archive that showed me the solr issue was the
setting for localhost. So I can get to solr via the actual localhost ok.
Yes, that's the default configuration.
But I'm still puzzled
That seems to get them to check out as you say. Thanks for the help.
Bobb Menk
-Original Message-
From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84
Sent: Thursday, February 09, 2012 12:55 PM
To: Menk, Robert - 1150 - MITLL
Cc: DSpace-tech@lists.sourceforge.net
Hi Paul,
I think you should be able to do this the filter-media command:
[dspace]/bin/dspace filter-media -f
The -f forces all current text extractions (which are used for full-text
searching) to be trashed and re-created.
B--
On 2/9/2012 at 2:23 PM, in message
I'm not 100% sure, but try running the cleanup script. This removes
bitstreams where bitstream.deleted = true.
Also, did you run index-update or index-init to rebuild your indices? I
always run index-init after I've done something like that, just to be safe.
Best regards,
Sue
Sue
Hi,
So far I have been importing a lot of csv files in to dspace
1.7.2.hoever
However after some time I couldn't import another csv file to the
system.
Here is the error
java.lang.IndexOutOfBoundsException: Index: 18, Size: 18
can someone suggests me on figure out the problem.
13 matches
Mail list logo
