Urgent question about okapi-longhorn-configuration.xml in jetty

[Axel Becher]

We are using several versions of Okapi in one jetty docker container. These instances may be used in parallel. It now seems, that frequently project-folders are used by okapi-instances at the same time hinting the "okapi-longhorn-configuration.xml" is not respected. We have put the server-config to /home/jetty/okapi-longhorn-configuration.xml but it seems "<use-unique-working-directory>True</use-unique-working-directory>" is not respected.

Another problem I see is that we use several snapshots of okapi-148 in this container as I assume all those snapshots would use the same working-directory "/home/jetty/Okapi-Longhorn-Files/148" - if the config xml would be respected.

[Marc Mittag]

Dear all,

we solved to problem that okapi-longhorn-configuration.xml is not respected by Jetty.

Yet still all snapshots of one version like okapi-148 share the same path.

Is there any way to get a build number respected as minor version or similar so that it is used in the path?

Thank you very much in advance!

best

Marc

On 25.11.25 21:53, Axel Becher wrote:

We are using several versions of Okapi in one jetty docker container. These instances may be used in parallel. It now seems, that frequently project-folders are used by okapi-instances at the same time hinting the "okapi-longhorn-configuration.xml" is not respected. We have put the server-config to /home/jetty/okapi-longhorn-configuration.xml but it seems "<use-unique-working-directory>True</use-unique-working-directory>" is not respected.

Another problem I see is that we use several snapshots of okapi-148 in this container as I assume all those snapshots would use the same working-directory "/home/jetty/Okapi-Longhorn-Files/148" - if the config xml would be respected.

--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-users/cad06ce8-e57b-4a85-b60c-07189a4068c7n%40googlegroups.com.

[Chase Tingley]

I wonder if the okapi-longhorn-configuration.xml file is not being picked up correctly.  I have a memory that this file is picked up either from the home directory of the running process, or failing that from the file system root

Our deployment also runs multiple longhorn versions out of an embedded jetty process; we load the config from the process home directory, and it does get picked up.  Our configuration looks like this:

<okapi-longhorn-configuration version="1">
    <working-directory>/path/to/home/directory/okapi-workdir</working-directory>
    <use-unique-working-directory>True</use-unique-working-directory>
    <project-id-strategy>UUID</project-id-strategy>
</okapi-longhorn-configuration>

We also run multiple snapshots off the same release, however we label them as internal subreleases (that is, we modify the pom.xml files) to keep them distinct.  This lets "use-unique-working-directory" correctly generate a unique directory structure.  I also do recommend setting project-id-strategy to "UUID" as an additional safety measure.

Lastly, it looks like there's an issue with using "use-unique-working-directory" when the "working-directory" parameter is a relative path.  Denis opened a PR to fix this a couple hours ago.

To view this discussion visit https://groups.google.com/d/msgid/okapi-users/07ec5129-c173-49af-bab5-0e0a2da4b379%40marcmittag.de.