-
Notifications
You must be signed in to change notification settings - Fork 535
Description
What steps does it take to reproduce the issue?
- When does this issue occur?
Only if you use Handle.net as PID. When you create an empty dataset and then add new files to it, you get an exception on the stage when file PID is being registered:
[Payara 6.2025.10] [WARNING] [] [edu.harvard.iq.dataverse.pidproviders.handle.HandlePidProvider] [tid: _ThreadID=105 _ThreadName=http-thread-pool::jk-connector(5)] [timeMillis: 1771588067681] [levelValue: 900] [[
registerNewHandle failed
HandleException (SERVICE_NOT_FOUND) Unable to find service for prefix 0.NA/NULL; prefix resolution response: Error(100): HANDLE NOT FOUND
at net.handle.hdllib.HandleResolver.tryAuthGlobalServiceLookupAndThrowExceptionOnFailure(HandleResolver.java:901)
at net.handle.hdllib.HandleResolver.getServiceInfo(HandleResolver.java:873)
at net.handle.hdllib.HandleResolver.findLocalSites(HandleResolver.java:910)
at net.handle.hdllib.HandleResolver.processRequestGlobally(HandleResolver.java:617)
at net.handle.hdllib.HandleResolver.processRequest(HandleResolver.java:587)
at net.handle.hdllib.HandleResolver.processRequest(HandleResolver.java:595)
at edu.harvard.iq.dataverse.pidproviders.handle.HandlePidProvider.registerNewHandle(HandlePidProvider.java:194)
at edu.harvard.iq.dataverse.pidproviders.handle.HandlePidProvider.createIdentifier(HandlePidProvider.java:403)
at edu.harvard.iq.dataverse.engine.command.impl.AbstractDatasetCommand.registerFileExternalIdentifier(AbstractDatasetCommand.java:274)
at edu.harvard.iq.dataverse.engine.command.impl.AbstractDatasetCommand.registerFilePidsIfNeeded(AbstractDatasetCommand.java:237)
at edu.harvard.iq.dataverse.engine.command.impl.UpdateDatasetVersionCommand.execute(UpdateDatasetVersionCommand.java:267)
at edu.harvard.iq.dataverse.engine.command.impl.UpdateDatasetVersionCommand.execute(UpdateDatasetVersionCommand.java:31)
at edu.harvard.iq.dataverse.EjbDataverseEngineInner.submit(EjbDataverseEngineInner.java:36)
at jdk.internal.reflect.GeneratedMethodAccessor1178.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
...
[Payara 6.2025.10] [INFO] [] [edu.harvard.iq.dataverse.engine.command.impl.AbstractDatasetCommand] [tid: _ThreadID=105 _ThreadName=http-thread-pool::jk-connector(5)] [timeMillis: 1771588067682] [levelValue: 800] [[
Call to globalIdServiceBean.createIdentifier failed: HandleException (SERVICE_NOT_FOUND) Unable to find service for prefix 0.NA/NULL; prefix resolution response: Error(100): HANDLE NOT FOUND]]
This exceptions does not brake the upload process - new will be added to the dataset, but it does not get a PID in the URL, it gets only "fileId". Further publication of the dataset works without errors - file PID will be registered again and you have two correct PIDs, for the dataset and for the file.
When you add a new file to the already published dataset you see the same behaviour as above - again exception at first and then proper behaviour after publication (from draft to the new version).
When I switch PID from Handle.net to the FAKE doi - everything works without exceptions.
- Which page(s) does it occurs on?
It was tested via GUI, page of dataset.
-
What happens?
-
To whom does it occur (all users, curators, superusers)?
all users
- What did you expect to happen?
A new Handle PID for the file should be registered already when the file is added to the dataset, and not only at the publication process. Proper behaviour is already realized for other PID providers.
Which version of Dataverse are you using?
This behaviour is same for versions 6.4-6.9.
Any related open or closed issues to this bug report?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status