Hello everyone,
During the process of updating dataverse.no from 5.13 to 5.14 we have a question about AJP connection in version 5.14.
We are using Shibboleth as described in the documentation[Shibboleth — Dataverse.org]. (ajp on port 8009) However, the Shibboleth proxy gets the following error message.
The timeout specified has expired: [client ...:38708] AH00878: read response failed from ...:8009 (dataverse)
The website on port 8080 works. My question is, how can I get the ajp to work in this version 5.14 dataverse.
Has anything changed in the ajp connection?
Thank you in advance for your time.
Hmm, I'm not aware of anything changing :thinking:
I have updated the whole thing from 5.13 to 5.14 and then the communication does not work. If we go back from 5.14 to 5.13 ajp works. So there is a change in the setting of ajp. Has anyone tested ajp in version 5.14 with a proxy?
At Harvard Dataverse we use Apache as a proxy. I assume you're using mod_shib and Apache. Are you also using an additional proxy? If so, which one?
Yes,
...
ProxyPass "/" "ajp://dataverse:8009/" timeout=600
ProxyPassReverse "/" "ajp://dataverse:8009/" timeout=600
...
I have not changed the Shib Proxy server and version 5.13 works and the other version 5.14 does not work.
How can I see what is working on ajp? I have no idea how to debug this service.
We use the same. (Apache and mod_shib.)
The main issue we are are having is that payara dose not seams to be answering on the ajp protocol in V5.14.
It's very strange. Are you using the version of Payara mentioned in the Dataverse 5.14 Installation Guide?
we are using :
Version = Payara Server 5.2022.5 #badassfish (build 492)
This should be the latest compatible version.
At https://guides.dataverse.org/en/5.14/installation/prerequisites.html#payara I see "Payara 5.2022.3 is recommended." Would you be able to try that version?
Thank you very much! That was the problem. :+1: :smile:
Last updated: Oct 30 2025 at 06:21 UTC