-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index: Index all is failing and not clear why, need better error handling/reporting, skip over failures? #623
Comments
Original Redmine Comment We unfortunately saw the same problem on the demo site this afternoon and this was a quick fix: swap order of methods within indexAll #4062 · 46ddb55 · IQSS/dataverse - 46ddb55 Kevin mentioned he'd be willing to comment so I'm passing this to him. Also, please note that before I swapped the methods, I did a quick test of commenting out dataverseUserServiceBean.findAll() and that at least let the method finish without throwing a EJBTransactionRolledbackExcept and TransactionRolledbackLocalException. |
Original Redmine Comment Philip Durbin wrote:
I still have the data from demo loaded up locally and there's definitely still a bug here. During "index all", exceptions are being thrown when some datasets are indexed when the dataset's "subtree" is being determined. Strangely, if you later index the dataset individually, no exception is thrown. I'm stealing this ticket back. |
Original Redmine Comment Philip Durbin wrote:
I just pushed this... cache calls to dataverseService.findRootDataverse() #4062 · c9151d4 · IQSS/dataverse - c9151d4 ... and it seems to prevent exceptions being throw during the "determine subtree" routine. Strangely, all I'm doing is reducing the number of calls to dataverseService.findRootDataverse() by caching the result (good for #3457 anyway). It prevents exceptions like this:
In the middle of troubleshooting I found a related bug: #4142 Because of this bug (and because newer validation rules are apparently in place on dataverse-demo since data was added), we'll see this if you try an "index all": { |
Original Redmine Comment Philip Durbin wrote:
This commit has been deployed to dataverse-demo. Passing to QA. |
Original Redmine Comment This was fixed. The broader feature of skipping failures and more debugging info is separate. Closing ticket |
Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 4062, https://redmine.hmdc.harvard.edu/issues/4062
Original Date: 2014-06-02
Original Assignee: Kevin Condon
Attaching a db dump where index all fails, from 5/28
Phil:
I don't know what's going on with the data that was on dvn-build
(badindex.sql, attached). I can easily reproduce the exceptions
(javax.ejb.EJBTransactionRolledbackException
javax.ejb.TransactionRolledbackLocalException)
"index all" works fine if I comment out the sections of
IndexServiceBean that call the DataverseUserServiceBean methods
findByUserName and findAll.
Related issue(s): #702
Redmine related issue(s): 4160
The text was updated successfully, but these errors were encountered: