Skip to content
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

Create Identifiers: Creating dataset when cannot contact authority service results in unpublishable dataset. #3869

Closed
kcondon opened this issue May 31, 2017 · 0 comments
Assignees
Labels
Type: Bug a defect

Comments

@kcondon
Copy link
Contributor

kcondon commented May 31, 2017

This only affects EZID.

  1. Alter credentials to be invalid so that id cannot be registered on dataset create (simulates service unavailable)
  2. Create dataset
  3. Restore credentials
  4. Publish dataset, see error about being unable to contact remote service in UI but log indicates identifier does not exist:

[2017-05-31T11:11:14.608-0400] [glassfish 4.1] [WARNING] [] [edu.harvard.iq.dataverse.DOIEZIdServiceBean] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1496243474608] [levelValue: 900] [[
alreadyExists failed]]

[2017-05-31T11:11:14.608-0400] [glassfish 4.1] [WARNING] [] [edu.harvard.iq.dataverse.DOIEZIdServiceBean] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1496243474608] [levelValue: 900] [[
String edu.ucsb.nceas.ezid.EZIDException: bad request - no such identifier]]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug a defect
Projects
None yet
Development

No branches or pull requests

3 participants