I just upgraded to DSpace 6.3 today and I have not yet been able to get the
oai import to complete. ~400,000 items that I need to import. I am
finding that the process keeps running out of memory.
I had did not have problems running this in DSpace 5.x. I will post back
if I discover something.
Tim:
I checked the max connections in postgres and dspace, and there was a
discrepancy, but after fixing that, I am still having the same problem. I
double checked the hibernate configs, and they are the defaults. So, I
have attached the error trace from my oai indexing job. Perhaps, that will
Thanks, Tim:
I will take a look at the postgres configuration. When we upgraded, we,
also, migrated to a new server and maybe there's a problem with the
postgres settings. I didn't think about that, so I am glad you suggested
it.
If that's not it, I will be happy to send a more detailed trace of
Unfortunately, we don't have enough information to help you resolve this
issue. Please take a look at our guide on Troubleshooting Errors, which
provides useful information about where to find error messages, where to
search for answers, and what to send along to mailing lists for help:
Hello,
At this point in time, DSpace 7 IP based Authentication/Authorization is
expected to function the same as DSpace 6 did. You can find DSpace 6
documentation on IP Authentication at:
https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins#AuthenticationPlugins-IPAuthentication
Hi George,
That is an odd error. It almost sounds like Hibernate is losing access to
the database (maybe a connection timeout or something?).
Could you check your logs to see if there's more information around *when*
and *how* this error occurs. You said it's occurring at different
Hi, Terry:
I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a few
months ago, and ran into trouble immediately with the OAI index. Emilio
Lorenzo and Adan Roman gave me a patch to org.dspace.xoai.app.XOAI.java to
print out records being indexed in verbose mode, and that helped
