Hi,
I have not been able to fix this issue, and can't spend any more time on at
this stage. There appears to be issues with the HarvestScheduler, threads,
hibernate, etc. I won't create an issue for this, as I'm unable to
determine if any other users are also encountering issues with a collection
set up for OAI harvesting (4000+ items) and scheduling of that process. I
have a work around with a scheduled job putting the status back to READY
for the harvested collection entry, that seems to be doing the trick for
our forked DSpace 6.0 installation. I had multiple issues getting the
harvest just to run with DSpace 6.3 against oracle, in tomcat 8/Java 8
environment.
Cheers
Kevin
On Thursday, 1 November 2018 23:49:52 UTC+10, Kev Gunn wrote:
>
> Hi,
>
> We are running a forked (aimsdc) version of DSPACE 6.1, it's about 12 - 18
> months old or so, haven't updated our fork as for now it's doing what we
> need it to do.
>
> However, the scheduled harvest has never worked, it runs once, and then
> gets caught with a status of QUEUED even though the harvest thread has
> completed.
>
> Specific classes involved here are in dspace-api are HarvestScheduler,
> OAIHarvester, HarvestedCollectionServiceImpl and
> HarvestedCollectionDAOImpl
>
> At the end of the method OAIHarvester.runHarvest() an attempt is made to
> update the Harvested_collection DB entry, however the save method is not
> implemented and there is this comment in AbstractHibernateDAO.save()
>
>
> public void save(Context context, T t) throws SQLException {
> //Isn't required, is just here for other DB implementation. Hibernate
> auto keeps track of changes.
> }
>
>
> For us, even though save has been called, the thread winds up without
> error, but these changes are never persisted, and the harvest_status
> remains QUEUED, and hence never runs again.
> There is an attempt to commit changes in the thread managing class which
> is a thread itself - HarvestScheduler.scheduleLoop()
>
> // Commit everything
> try {
> mainContext.complete();
> log.info("Done with iteration " + i);
> } catch (SQLException e) {
> log.error("Exception completing iteration " + i + " - " + e.getMessage(),
> e);
> mainContext.abort();
> }
>
>
> Is anyone experiencing this same issue? Should the save actually be
> implementing a persist as things are happening in different threads?
>
> Log snapshot
> ...
> 2018-11-01 13:57:33,659 INFO org.dspace.harvest.OAIHarvester @ Harvest
> from https://ipubs.aims.gov.au:8543/oai/request successful. The process
> took 37219 milliseconds. Harvested 4819 items.
> 2018-11-01 13:57:33,659 INFO org.dspace.harvest.HarvestThread @ Thread
> for collection 45c9e139-62b0-46da-9cc7-ae93787265c8 completes.
> 2018-11-01 13:57:33,784 INFO org.dspace.harvest.HarvestScheduler @ Done
> with iteration 10
> ...
>
> Cheers
> Kevin
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
