OMG I tried 6.2024.1 just now... Payara's quality is dwindling IMO... First I have to maneuver around them not releasing payara-api packages for month. And now this:
dev_dataverse> Caused by: java.lang.NullPointerException: Cannot invoke "fish.payara.nucleus.microprofile.config.spi.ConfigValueImpl.getSourceOrdinal()" because "resultWithoutProfile" is null
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.resolve(ConfigExpressionResolver.java:112)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.resolveExpression(ConfigExpressionResolver.java:227)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.resolveExpression(ConfigExpressionResolver.java:153)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.getValue(ConfigExpressionResolver.java:135)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.resolve(ConfigExpressionResolver.java:108)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.ConfigExpressionResolver.resolve(ConfigExpressionResolver.java:91)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.searchConfigSources(PayaraConfig.java:352)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.getConfigValue(PayaraConfig.java:251)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.getConfigValue(PayaraConfig.java:229)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.getValue(PayaraConfig.java:224)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.getValueInternal(PayaraConfig.java:200)
dev_dataverse> at fish.payara.nucleus.microprofile.config.spi.PayaraConfig.getOptionalValue(PayaraConfig.java:173)
dev_dataverse> at edu.harvard.iq.dataverse.settings.JvmSettings.lookupOptional(JvmSettings.java:382)
dev_dataverse> at edu.harvard.iq.dataverse.settings.JvmSettings.lookupOptional(JvmSettings.java:341)
dev_dataverse> at edu.harvard.iq.dataverse.util.SystemConfig.getDataverseSiteUrlStatic(SystemConfig.java:265)
dev_dataverse> at edu.harvard.iq.dataverse.DatasetVersion.<init>(DatasetVersion.java:197)
It's causing the whole deployment to fail!!! (Without even giving a non-profiled value)
@Oliver Bertuch I hope you don't mind... I moved this to its own topic.
Great. I was able to reproduce the problem with a simple unit test...
woof
Writing a bug report just now and probably will create a PR to Payara... :see_no_evil:
https://github.com/payara/Payara/pull/6550
In the end, an easy fix. And once more showing the importance of doing proper unit testing
Nice.
By the way if you change Fixes #6549 to - Fixes #6549 you get a nice preview of the title of the issue.
Badger? Mushroom? These tests are great. :grinning:
I didn't write those. I suppose these are references to some comic / cartoon I'm not familiar with
Philip Durbin said:
Badger? Mushroom? These tests are great. :grinning:
It might be a reference to https://en.wikipedia.org/wiki/Badgers_(animation)
British. Yes, probably. :grinning:
Oliver Bertuch said:
Philip Durbin said:
Badger? Mushroom? These tests are great. :grinning:
It might be a reference to https://en.wikipedia.org/wiki/Badgers_(animation)
Who wrote those tests then? :smile: GPT?
Woo-hoo my PR was just merged!
I suppose it will be in 6.2024.4 then
Congrats! :tada:
6.2024.4 has been released today
Oliver Bertuch has marked this topic as resolved.
To test if this release solves the issues with OpenAPI how can we get an image for testing :thinking:
Let me hack on stuff some more and it will be served :stuck_out_tongue:
Philip Durbin has marked this topic as unresolved.
Kids embedded, will hack on stuff now
Will probably attend to the base image versioning first though
I wish I could embed my kids. They stay up all night. Teenagers. :rolling_eyes:
https://www.youtube.com/watch?v=HBmIJFtn_qQ
The lyrics are below... :wink: You might need to put it through DeepL though :smile_cat:
Created the upgrade PR: https://github.com/IQSS/dataverse/pull/10495
I can confirm that my patch does indeed fix the issue during deployment!
So we can make our move :tada:
In the description for this... Upgrade to Payara 6.2024.4+ #10494
I just added this: In containers, can't set DATAVERSE_SITEURL using documented methods #10285
You beat me to it! I was typing the same thing!
:racecar:
I'm going to add a "closes" to the PR
Perfect!
As @Juan Pablo Tosca Villanueva doesn't need 2024.4 for OpenAPI anymore, and as long as @Don Sizemore doesn't tell me the sec issues are really bad ass - should we make the PR to apply the upgrade to the containers only? Just encourage people to upgrade?
(On the other hand: it's been a year without a Payara update for people, so maybe it's good to make them?)
I'm just saying: this doesn't look good.
image.png
(rev2 has 6.2024.4)
Most of the yellow and light yellow ones are caused by Ubuntu 22.04 having an old imagemagick...
This will be resolved once 24.04 is out and we can finally upgrade the Temurin images
Hmm, I think I'd like to upgrade Payara everywhere at once: containers, production, etc.
Mostly I'm just thinking that developers should stay on the same version as production.
This is done now with 6.3.
Oliver Bertuch has marked this topic as resolved.
Last updated: Oct 30 2025 at 05:14 UTC