Vera Clemens (Jun 12 2025 at 14:39): Vera Clemens (Jun 12 2025 at 14:39):Hi, I am encountering a weird error I am not sure how to fix. If someone here had an idea, I would be very grateful.
I am building my own custom Dataverse app image off my own branch, which is based on the current v6.6 master branch, plus some of my own commits. Until today, this was working OK, but now I the containers I start using my custom image fail with the following error:
[#|2025-06-12T14:11:06.108+0000|SEVERE|Payara 6.2025.2|javax.enterprise.system.core|_ThreadID=29;_ThreadName=RunLevelControllerThread-1749737428556;_TimeMillis=1749737466108;_LevelValue=1000;|
Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.NoSuchFieldError: API_BLOCKED_POLICY|#]
[#|2025-06-12T14:11:06.109+0000|WARNING|Payara 6.2025.2|fish.payara.boot.runtime.BootCommand|_ThreadID=29;_ThreadName=RunLevelControllerThread-1749737428556;_TimeMillis=1749737466109;_LevelValue=900;|
Boot Command deploy failed PlainTextActionReporterFAILUREDescription: deploy AdminCommandError occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.NoSuchFieldError: API_BLOCKED_POLICY. Please see server.log for more details.
I've actually seen this error before. I built my custom app image using the unstable base image, which apparently included a change that introduced API_BLOCKED_POLICY (which is not present in v6.6, so it's also not present in my branch). I solved it by setting -Dbase.image=gdcc/base:6.6-noble (instead of default gdcc/base:unstable).
But today I built some new images and they're failing with that error again. I saw that the base:6.6-noble image has recently been pushed (3 days ago), and thought maybe there was a mistake made with that push. But now I've even tried to build my image with -Dbase.image=gdcc/base:6.6-noble-r0 because that hasn't had any pushes in 2 months, and I'm still getting the error. :sweat:
As I said, if anyone had an idea what's causing it, I'd be very grateful! Thanks!
Oliver Bertuch (Jun 15 2025 at 02:59):Not sure what's going on here. Some notes: the -rX images are the fixed tags, so their content will not change once created. Which JDK version are you using to build the images? We've seen weird stuff happening due to this and this might be another one.
Oliver Bertuch (Jun 15 2025 at 03:02):I am not sure what you are referring to when you mention API_BLOCKED_POLICY. To my knowledge, that's not an env var the base image defines?!
Vera Clemens (Jun 16 2025 at 08:27):I believe API_BLOCKED_POLICY refers to this newly introduced JvmSetting: https://github.com/IQSS/dataverse/blob/develop/src/main/java/edu/harvard/iq/dataverse/api/filter/ApiBlockingFilter.java#L81
Vera Clemens (Jun 16 2025 at 08:27):It's present on develop, but not on master/my branch.
Vera Clemens (Jun 16 2025 at 08:28):My JDK version is this: openjdk version "17.0.15" 2025-04-15
Vera Clemens (Jun 16 2025 at 09:19):OK, seems like I fixed it by setting -Dbase.image.tag=6.6-noble. It seems like -Dbase.image=gdcc/base:6.6-noble wasn't correct.
Philip Durbin 🚀 (Jun 16 2025 at 11:53):Yes, it was added recently, in #11454.
Philip Durbin 🚀 (Jun 16 2025 at 19:48):@Vera Clemens have you pushed your branch anywhere? Should we try it?
Oliver Bertuch (Jun 18 2025 at 21:17):I suppose the environment variable needs to be DATAVERSE_API_BLOCKED_POLICY as it uses mpconfig.
Oliver Bertuch (Jun 18 2025 at 21:18):Not sure why base.image wouldn't work for you though.
Last updated: Oct 30 2025 at 05:14 UTC