Stream: containers

Topic: DATAVERSE_HTTP_TIMEOUT not having an effect

Philip Durbin 🚀 (Feb 11 2025 at 20:41):

I'm playing around with DATAVERSE_HTTP_TIMEOUT in my compose file like this:

       DATAVERSE_SPI_EXPORTERS_DIRECTORY: "/dv/exporters"
       DATAVERSE_HTTP_TIMEOUT: "123"
       # These two oai settings are here to get HarvestingServerIT to pass
       dataverse_oai_server_maxidentifiers: "2"

Philip Durbin 🚀 (Feb 11 2025 at 20:41):

However, it doesn't seem to be working. Or perhaps I don't know how to check the value at runtime?

Philip Durbin 🚀 (Feb 11 2025 at 20:42):

I tried getting the value like this:

payara@dataverse:~$ /opt/payara/appserver/bin/asadmin get server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds
Enter admin user name> admin
Enter admin password for user "admin">
server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds=${MPCONFIG=dataverse.http.timeout:900}
Command get executed successfully.
payara@dataverse:~$

Philip Durbin 🚀 (Feb 11 2025 at 20:42):

I was expecting (or at least hoping) it would say "123" but instead it says "${MPCONFIG=dataverse.http.timeout:900}"

Philip Durbin 🚀 (Feb 11 2025 at 20:43):

Am I doing this wrong? If I set a tunable, how can I check its value afterward?

Philip Durbin 🚀 (Feb 12 2025 at 13:50):

I'm asking because in #11210 I'm adding a new tunable called DATAVERSE_COOKIE_SAME_SITE_VALUE that isn't working. That is, when I try to use it in the compose file, it has no effect. :disappointed:

Philip Durbin 🚀 (Feb 12 2025 at 13:50):

Some discussion here: https://github.com/IQSS/dataverse/pull/11210/files#r1951621318

Philip Durbin 🚀 (Feb 12 2025 at 16:51):

I ended up deleting DATAVERSE_COOKIE_SAME_SITE_VALUE. I couldn't get it to work.

Last updated: Oct 30 2025 at 05:14 UTC