I have forwarded this information to Milen Profirovic (Milen,<email address hidden>), who performed the work on GHO-single-war-file packaging. In addition to that, Paul Pimstone sent the following comment:
Milen is away until tomorrow.
Philippe, please talk to John Rawlinson and Steve Moore about this. They had the same issue a couple of weeks ago which we assisted with but they identified and resolved it themselves with a WHO related configuration -- so perhaps this is the same cause.
Another thing to investigate: I have noticed that in the configuration template (config_templates/WEB-INF_web.xml), the caller users the URL OLAP_METADATA_SERVER_PATH=/{_CONF_WAR_NAME}/olapMetaDataServlet (note the lowercase "o" in "olap"), while the servlet-mapping section defines the URL pattern /OlapMetadataServlet (note the uppercase :"O"), This could be OK when Milen was testing on Windows, but the case sensitivity may matter when running on Linux.
I have forwarded this information to Milen Profirovic (Milen,<email address hidden>), who performed the work on GHO-single-war-file packaging. In addition to that, Paul Pimstone sent the following comment:
Milen is away until tomorrow.
Philippe, please talk to John Rawlinson and Steve Moore about this. They had the same issue a couple of weeks ago which we assisted with but they identified and resolved it themselves with a WHO related configuration -- so perhaps this is the same cause.
Another thing to investigate: I have noticed that in the configuration template (config_ templates/ WEB-INF_ web.xml) , the caller users the URL OLAP_METADATA_ SERVER_ PATH=/{ _CONF_WAR_ NAME}/olapMetaD ataServlet (note the lowercase "o" in "olap"), while the servlet-mapping section defines the URL pattern /OlapMetadataSe rvlet (note the uppercase :"O"), This could be OK when Milen was testing on Windows, but the case sensitivity may matter when running on Linux.