Possible solutions for the UnsupportedCallbackException problem when running two instances of Oxalis-NG WAR under the same Tomcat 11 server

[aleksander-oven]

I set up two identically configured Oxalis-NG instances under Tomcat 11, each under its own URL endpoint: /ap1 and /ap2. However, it turns out that only /ap1 behaves as expected. When sending a document to the /ap2 endpoint, Oxalis-NG throws an UnsupportedCallbackException.

After some investigating, it seems that the nature of this problem has already been described here more than 2 years ago, in detail! I can confirm from reported stacks that this is most likely still the same problem with Oxalis-NG.

What is the recommended solution for a scenario, where we want to run two Oxalis-NG instances, one configured with a Peppol TEST certificate and the other with a Peppol PROD certificate, in parallel?

NOTE: I'm not a Java developer.

[aleksander-oven]

After learning a bit more about Tomcat webapps basics and shared loading, I decided it would be best if I configured /ap1 and /ap2 as separate Tomcat services according to documentation.

It took some time to get everything in place, but I managed to avoid the shared loading problem altogether! My /ap1 and /ap2 are now hosted in separate processes, with separate configuration, and each with its own JVM.

I'm still unsure if this is the recommended way, but at least it works for me without hacking around the Java code.

I'll leave the discussion open, in case anyone else can add anything.