Error when trying to create a new Dataset (NullPointerException)

[faborg]

When I try to create a new Dataset, after clicking on "Save Dataset" the form is grayed out and no data is saved. Is this a bug? Help would be highly appreciated.

The payara-log contains the following exception:

[2024-05-13T13:25:57.553+0000] [Payara 6.2024.4] [SEVERE] [] [jakarta.enterprise.resource.webcontainer.faces.context] [tid: _ThreadID=71 _ThreadName=http-thread-pool::http-listener-1(4)] [timeMillis: 1715606757553] [levelValue: 1000] [[
  java.lang.NullPointerException: Cannot invoke "edu.harvard.iq.dataverse.GlobalId.asString()" because the return value of "edu.harvard.iq.dataverse.Dataset.getGlobalId()" is null
java.lang.NullPointerException: Cannot invoke "edu.harvard.iq.dataverse.GlobalId.asString()" because the return value of "edu.harvard.iq.dataverse.Dataset.getGlobalId()" is null
	at edu.harvard.iq.dataverse.DatasetPage.returnToDraftVersion(DatasetPage.java:4070)
	at edu.harvard.iq.dataverse.DatasetPage.save(DatasetPage.java:3920)
	at jdk.internal.reflect.GeneratedMethodAccessor1425.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.glassfish.expressly.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:186)
	at org.glassfish.expressly.parser.AstValue.invoke(AstValue.java:253)
	at org.glassfish.expressly.MethodExpressionImpl.invoke(MethodExpressionImpl.java:248)
	at org.jboss.weld.module.web.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)
	at org.jboss.weld.module.web.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
	at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:70)
	at com.sun.faces.application.ActionListenerImpl.getNavigationOutcome(ActionListenerImpl.java:74)
	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:62)
	at jakarta.faces.component.UICommand.broadcast(UICommand.java:205)
	at jakarta.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:858)
	at jakarta.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1332)
	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:56)
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:72)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:159)
	at jakarta.faces.webapp.FacesServlet.executeLifecyle(FacesServlet.java:691)
	at jakarta.faces.webapp.FacesServlet.service(FacesServlet.java:449)
	at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1554)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:331)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
	at org.glassfish.tyrus.servlet.TyrusServletFilter.doFilter(TyrusServletFilter.java:83)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:253)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:226)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:253)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:166)
	at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:757)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:577)
	at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:158)
	at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:372)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:239)
	at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
	at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
	at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
	at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
	at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
	at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
	at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
	at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
	at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
	at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)
	at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:51)
	at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:510)
	at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:82)
	at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:83)
	at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:101)
	at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
	at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
	at java.base/java.lang.Thread.run(Thread.java:840)
]]

[faborg]

I have installed:

• Dataverse 6.2
• Payara 6.2024.4
• openjdk 17.0.11 2024-04-16
• OpenJDK Runtime Environment (build 17.0.11+9-Debian-1deb12u1)
• OpenJDK 64-Bit Server VM (build 17.0.11+9-Debian-1deb12u1, mixed mode, sharing)

[pdurbin]

java.lang.NullPointerException: Cannot invoke "edu.harvard.iq.dataverse.GlobalId.asString()" because the return value of "edu.harvard.iq.dataverse.Dataset.getGlobalId()" is null
	at edu.harvard.iq.dataverse.DatasetPage.returnToDraftVersion(DatasetPage.java:4070)

Yes, sure enough, getGlobalId must be null:

https://github.com/IQSS/dataverse/blob/v6.2/src/main/java/edu/harvard/iq/dataverse/DatasetPage.java#L4070

@faborg thanks for the details about your installation. Is it a new installation? Did you upgrade from Dataverse 6.1? Which PID provider are you using (out of the box, DataCite is selected).

[qqmyers]

We definitely haven't seen this in 6.2 yet. The only thing different in your setup is a later Payara - the Guides talk about 6.2023.8 and I've run 6.2023.11 without issue. Any details to help us reproduce this would be very welcome.

[pdurbin]

Another report just came in: https://dataverse.zulipchat.com/#narrow/stream/378866-troubleshooting/topic/grayed.20out.20when.20trying.20to.20save.20dataset/near/438440374

[faborg]

It's a fresh install (locally in VMs) and I'm using a FAKE DOI Provider.

[qqmyers]

Is your FAKE provider configured with the new multi-pid-provider JVM/micro-profile options or the original/legacy single-pid-provider database settings?

[alteronth]

How do we switch between multi and single? I encountered the same issue when trying to save dataset right after traditional installation following the guide?

[qqmyers]

I think new installs by default should be using the settings described in https://guides.dataverse.org/en/latest/installation/config.html#dataverse-pid-type. If you can see those when you do a bin/asadmin list-jvm-options from your /usr/local/payara6 dir, you should be using the new multi-pid way. If you have http://localhost:8080/api/admin/settings/ :DoiProvider and related things set, you have the legacy settings. Those shouldn't be needed and should be ignored if you have the multi-pid setup in place (although they would be used if the multi-pid settings are invalid - do you see anything in the log about legacy settings when you start up?)

I'm asking so I know how to try and reproduce your issue - the code for new and legacy settings are different so it's possible we have a problem with one and not the other. We could also have an issue in the build script for first time setups.

[cmbz]

2024/05/15
Prioritized following discussion with @pdurbin. Initial sizing of 10 for investigation. Solving problem may require additional time.