So made the updates, added the missing configuration, and the harvest ran,
but now I encounter a thread related hibernate error reported in this
post: https://groups.google.com/forum/#!topic/dspace-tech/37HCRaCyePw
Does the scheduled harvest work in DSpace 6.3? Can anyone confirm that for
me please?
Log snap shot
2018-11-05 10:16:22,553 ERROR org.dspace.harvest.OAIHarvester @ Error
occurred while generating an OAI response: possible non-threadsafe access
to session null
org.hibernate.AssertionFailure: possible non-threadsafe access to session
at
org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:92)
at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:395)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:387)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:303)
at
org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:349)
at
org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:56)
at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1195)
at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.hibernate.context.internal.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:352)
at com.sun.proxy.$Proxy108.flush(Unknown Source)
at
org.dspace.core.HibernateDBConnection.commit(HibernateDBConnection.java:83)
at org.dspace.core.Context.commit(Context.java:435)
at org.dspace.harvest.OAIHarvester.intermediateCommit(OAIHarvester.java:436)
at org.dspace.harvest.OAIHarvester.runHarvest(OAIHarvester.java:367)
at org.dspace.harvest.HarvestThread.runHarvest(HarvestThread.java:61)
at org.dspace.harvest.HarvestThread.run(HarvestThread.java:45)
at java.lang.Thread.run(Unknown Source)
2018-11-05 10:16:22,623 INFO
org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl @ HHH000010: On
release of batch it still contained JDBC statements
2018-11-05 10:16:22,623 WARN
org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ SQL Error: 1, SQLState:
23000
2018-11-05 10:16:22,624 ERROR
org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ ORA-00001: unique
constraint (DSPACE_EXT.SYS_C00147126) violated
2018-11-05 10:16:22,624 WARN
org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ SQL Error: 1, SQLState:
23000
2018-11-05 10:16:22,624 ERROR
org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ ORA-00001: unique
constraint (DSPACE_EXT.SYS_C00147126) violated
2018-11-05 10:16:22,628 ERROR
org.hibernate.engine.jdbc.batch.internal.BatchingBatch @ HHH000315:
Exception executing batch [could not execute batch]
2018-11-05 10:16:22,633 ERROR org.dspace.harvest.HarvestThread @ Runtime
exception in thread: Thread[Thread-24,5,main]
2018-11-05 10:16:22,633 ERROR org.dspace.harvest.HarvestThread @ failed to
lazily initialize a collection of role:
org.dspace.content.Community.parentCommunities, could not initialize proxy
- no Session null
2018-11-05 10:16:22,633 INFO org.dspace.core.Context @ complete() was
called on a closed Context object. No changes to commit.
2018-11-05 10:16:22,633 INFO org.dspace.core.Context @ commit() was called
on a closed Context object. No changes to commit.
2018-11-05 10:16:22,633 INFO org.dspace.harvest.HarvestThread @ Thread for
collection b2411369-fca4-44f3-ab14-4af19a562e9a ends - Harvested
Collection: HarvestedCollection{id=1,
collection=org.dspace.content.Collection@7fa79a09,
oaiSource='https://ipubs.aims.gov.au:8543/oai/request',
oaiSetId='col_11068_2', harvestType=1, harvestStatus=-1,
harvestStartTime=Mon Nov 05 10:08:48 AEST 2018, lastHarvested=null,
harvestMessage='Runtime error occurred while generating an OAI response',
metadataConfigId='dim'}
2018-11-05 10:16:22,633 INFO org.dspace.harvest.HarvestThread @ Thread for
collection b2411369-fca4-44f3-ab14-4af19a562e9a completes.
2018-11-05 10:16:23,280 INFO org.dspace.harvest.HarvestScheduler @ Done
with iteration 7
Cheers
On Wednesday, 12 September 2018 16:42:34 UTC+10, euler wrote:
>
> Dear All,
>
> I'm having trouble using the automatic harvest scheduler both in the XMLUI
> and in the command line. The version of DSpace the server is running on is
> 6.3. When I use the command line (dspace harvest -S), the command line
> returned the following error:
>
> Starting harvest loop... running.
> org.dspace.core.exception.DatabaseSchemaValidationException: The schema
> validator returned: null
> at org.dspace.core.Context.init(Context.java:170)
> at org.dspace.core.Context.<init>(Context.java:126)
> at
> org.dspace.harvest.HarvestScheduler.scheduleLoop(HarvestScheduler.java:149)
> at
> org.dspace.harvest.HarvestScheduler.run(HarvestScheduler.java:140)
> at java.lang.Thread.run(Unknown Source)
> Exception in thread "Thread-4"
> org.dspace.core.exception.DatabaseSchemaValidationException: The schema
> validator returned: null
> at org.dspace.core.Context.init(Context.java:170)
> at org.dspace.core.Context.<init>(Context.java:126)
> at
> org.dspace.harvest.HarvestScheduler.scheduleLoop(HarvestScheduler.java:234)
> at
> org.dspace.harvest.HarvestScheduler.run(HarvestScheduler.java:140)
> at java.lang.Thread.run(Unknown Source)
>
>
> The log showed the message below after running the command dspace harvest
> -S:
>
> 2018-09-12 13:14:57,708 FATAL org.dspace.core.Context @ Cannot obtain the
> bean which provides a database connection. Check previous entries in the
> dspace.log to find why the db failed to initialize. The schema validator
> returned: null
> 2018-09-12 13:14:57,709 ERROR org.dspace.harvest.HarvestScheduler @
> Exception on iteration: 0
> 2018-09-12 13:14:57,713 FATAL org.dspace.core.Context @ Cannot obtain the
> bean which provides a database connection. Check previous entries in the
> dspace.log to find why the db failed to initialize. The schema validator
> returned: null
>
> When using the Harvesting tab in the XMLUI control panel, after clicking
> Start Harvester, the page returned this message:
>
> failed to lazily initialize a collection of role:
> org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no
> Session
>
> Although when I press the back button of the browser, the status says that
> the scheduler is waiting for collections to harvest. It seems that the
> automatic scheduler from the UI is now running although it didn't harvest
> any new items from the collections that I've set up for harvesting because
> I have been receiving email messages from the server informing me of a
> Harvest error. Below is the content of the harvest error message:
>
> Collection 5bee1194-648c-4136-8671-ddc43fc3f85f failed on harvest:
>
> Date: 9/11/18 6:25 PM
> Status Flag: -1
>
> We need at least an eperson or a group in order to create a resource
> policy.
>
> Exception:
> java.lang.IllegalArgumentException: We need at least an eperson or a
> group in order to create a resource policy.
> at org.dspace.authorize.AuthorizeServiceImpl.createResourcePolicy(
> AuthorizeServiceImpl.java:777)
> at org.dspace.authorize.AuthorizeServiceImpl.addPolicy(
> AuthorizeServiceImpl.java:533)
> at org.dspace.content.WorkspaceItemServiceImpl.create(
> WorkspaceItemServiceImpl.java:99)
> at org.dspace.harvest.OAIHarvester.processRecord(
> OAIHarvester.java:539)
> at org.dspace.harvest.OAIHarvester.runHarvest(
> OAIHarvester.java:367)
> at org.dspace.harvest.HarvestThread.runHarvest(
> HarvestThread.java:57)
> at org.dspace.harvest.HarvestThread.run(HarvestThread.java:41)
> at java.lang.Thread.run(Unknown Source)
>
> So I would like to ask for help if anyone have ever encountered the errors
> above and how did you resolve it? I tried to harvest the collection that is
> giving me these errors in the dspace demo site using the same harvest_type
> and metadata_format and the harvest is successful. I just want to harvest
> automatically so that I don't have to run the harvest manually.
>
> Thanks in advance,
> euler
>
--
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.