Clearing and indexing datasets fail

33 views
Skip to first unread message

Michel Bamouni

unread,
Feb 19, 2018, 11:27:04 AM2/19/18
to Dataverse Users Community
Hello,

I run the command "curl http://localhost:8080/api/admin/index/clear" which success.
After that, I run the command "curl http://localhost:8080/api/admin/index/" to reindexing all my dataset.
All things go well and I got the message "27 dataverses and 8134 datasets indexed. index all took 816973 milliseconds. Solr index was not cleared before indexing." But indexing fail at the end with the message :
"
javax.validation.ConstraintViolationException: Bean Validation constraint(s) violated while executing Automatic Bean Validation on callback event:'preUpdate'. Please refer to embedded ConstraintViolations for details.
    at org.eclipse.persistence.internal.jpa.metadata.listeners.BeanValidationListener.validateOnCallbackEvent(BeanValidationListener.java:90)
    at org.eclipse.persistence.internal.jpa.metadata.listeners.BeanValidationListener.preUpdate(BeanValidationListener.java:72)
    at org.eclipse.persistence.descriptors.DescriptorEventManager.notifyListener(DescriptorEventManager.java:721)
    at org.eclipse.persistence.descriptors.DescriptorEventManager.notifyEJB30Listeners(DescriptorEventManager.java:691)
    at org.eclipse.persistence.descriptors.DescriptorEventManager.executeEvent(DescriptorEventManager.java:229)
    at org.eclipse.persistence.descriptors.changetracking.DeferredChangeDetectionPolicy.calculateChanges(DeferredChangeDetectionPolicy.java:87)
    at org.eclipse.persistence.descriptors.changetracking.DeferredChangeDetectionPolicy.calculateChangesForExistingObject(DeferredChangeDetectionPolicy.java:56)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:664)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1516)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3168)
    at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:352)
    at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:158)
    at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
    at com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:452)
    at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:854)
    at com.sun.ejb.containers.EJBContainerTransactionManager.completeNewTx(EJBContainerTransactionManager.java:719)
    at com.sun.ejb.containers.EJBContainerTransactionManager.postInvokeTx(EJBContainerTransactionManager.java:503)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4566)
    at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:2074)
    at com.sun.ejb.containers.EjbAsyncTask.call(EjbAsyncTask.java:114)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
"
Can someone has already meet this error? If true how can I solve it

Thanks,

Michel

danny...@g.harvard.edu

unread,
Feb 20, 2018, 8:52:06 AM2/20/18
to Dataverse Users Community
Hi Michel, I think you may be encountering this issue:


There's a workaround of running it in "continue" mode suggested there. Can you give it a shot and let me know if it works for you? If this doesn't work, please let me know how much memory you've allotted to Dataverse, as it may be a memory issue.

- Danny

Michel Bamouni

unread,
Feb 21, 2018, 6:04:49 AM2/21/18
to Dataverse Users Community

Michel Bamouni

unread,
Feb 21, 2018, 6:07:31 AM2/21/18
to Dataverse Users Community
Hi,

In addition to my previous post, when you say the "how much memory you've allotted to Dataverse", you mean the pysical memory of the VM or the Xmx parameter in glassfish domain.xml?

Michel

Brooke, Danny

unread,
Feb 21, 2018, 10:22:16 AM2/21/18
to dataverse...@googlegroups.com
Michel,

Thanks for the followup. This “preUpdate” Constraint Validation is usually an indication that some invalid data is present. Because of the nature of this error, it is very difficult to recover from (and also can be difficult to find the invalid data). 

javax.validation.ConstraintViolationException: Bean Validation constraint(s) violated while executing Automatic Bean Validation on callback event:'preUpdate'. Please refer to embedded ConstraintViolations for details.

I was on the wrong track about the original issue, so you can disregard the question about the memory.

- Danny




--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/fb5a105d-00f0-4f26-973a-eedbadf6c7b0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages