v6.2 - accessing dataset throws exception

16 views
Skip to first unread message

jeyala...@yahoo.com

unread,
Jun 12, 2026, 3:03:35 AM (2 days ago) Jun 12
to Dataverse Users Community
Hi!
    After upgrading to v6.2, we couldn't access any dataset. It throws:
jakarta.servlet.ServletException: /dataset.xhtml @595,164 rendered="#{settingsWrapper.makeDataCountDisplayEnabled and DatasetPage.doi}": The class 'edu.harvard.iq.dataverse.DatasetPage' does not have the property 'doi'.

Screenshot 2026-06-12 141615.png
 
Please find attached the logs.

The instructions given in release notes are followed correctly. In v6.2, edu.harvard.iq.dataverse.DatasetPage' do not have doi property only. 

Initially I used legacy single PID configuration only and got the above error.

Then I configured for Multiple PID configuration as follows:
         <jvm-options>-Ddataverse.pid.providers=datacite1</jvm-options>
         <jvm-options>-Ddataverse.pid.default-provider=datacite1</jvm-options>
        <jvm-options>-Ddataverse.pid.datacite1.type=datacite</jvm-options>
         <jvm-options>-Ddataverse.pid.datacite1.label=DataCite</jvm-options>
         <jvm-options>-Ddataverse.pid.datacite1.authority=10.20405</jvm-options>
        <jvm-options>-Ddataverse.pid.datacite1.shoulder=FK2/</jvm-options>
         <jvm-options>-Ddataverse.pid.datacite1.datacite.mds-api-url=https://mds.test.datacite.org</jvm-options>
         <jvm-options>-Ddataverse.pid.datacite1.datacite.rest-api-url=https://api.test.datacite.org</jvm-options>
         <jvm-options>-Ddataverse.pid.datacite1.datacite.username=*</jvm-options>
 <jvm-options>-Ddataverse.pid.datacite1.datacite.password=${ALIAS=doi_password_alias}</jvm-options>

But still getting the same error.

Please advise.
Thanks,
Jeya
error_log.txt
Reply all
Reply to author
Forward
0 new messages