Dear XWiki team,
We are running XWiki on OpenShift since 2023, and it was a non-trivial task to upgrade it when you roll out a mayor release. Usually, I just slapped a new container version in the yaml, rebooted, migrations were done and we are ready to go.
Despite I fully understand, that 17.0 is a big major update, it is for the first time ever I don’t know how to update XWiki, forcing us to be stick to the LTS branch again.
We have a test XWiki instance which is basically clean and had only OIDC plugin installed for the testing purposes of Entra ID login.
I did everything as usual, but I can’t get it up. Catalina reports memory leak of the process and then tomcat says something like “application ihstance was already stopped”. Please see the log attached.
I tried to update the production too, but behaviour is the same and I don’t know what causes this. May you have any idea?
xwiki-test-d5b9c476c-s7r44-xwiki-test.log (33.5 KB)
Colleagues from XWiki SAS told me it’s not yet stable enough, and suggested to stick to LTS branch too. I am fine with this,
Thank you!
In theory, all it takes is to move to Tomcat 10+ (but moving to Tomcat 10+ itself might not always be that easy, different Debian distribution, etc.).
Note that you seem to have some problem with your glowroot setup.
Hmm there seems to be an unexpected API breakage with the SessionDestroyedEvent with which the OpenID Connect module is not happy. Will fix that regression ASAP, but it should not have much noticeable consequence than those error logs when a session is invalidated (for example at logout).
That’s probably the root cause, maybe the Tomcat 10 memory is not properly configured (the default memory allocated for Tomcat is usually too low for XWiki). What exactly are you using to deploy XWiki ? The docker image ?
Ah, regarding the glowroot I know, but no time to fix it 
But the problem is, we don’t have your OIDC plugin on the production. We use Active Directory Pro plugin there (actually there is a trouble with the migration), and it also fails with the same thread error. Logs are here
Explore-logs-2025-02-03 21_41_31.txt (2.1 MB)
Explore-logs-2025-02-03 21_35_29.txt (186.9 KB)
xwiki-b66c4bbcd-q56hw-xwiki (2).log (27.0 KB)
xwiki-b66c4bbcd-q56hw-xwiki (1).log (8.9 KB)
xwiki-b66c4bbcd-q56hw-xwiki.log (27.0 KB)
As I said, this is our Red Hat OpenShift cluster that we run on our datacenter. I just take your docker image, change the permissions rights to make it work on OpenShift, and then refer it in the deployment. The difference with K8S is t hat OpenShift has more policies and rights controls, this is why I rebuild the image.
Is this OIDC plugin thing that critical that it breaks the whole XWiki???
containers:
- resources:
limits:
cpu: '8'
memory: 7000Mi
requests:
cpu: '2'
memory: 3000Mi
Well, you definitely do according to the stack traces, since the class org.xwiki.contrib.oidc.auth.internal.session.ClientHttpSessionListener is located in the extension org.xwiki.contrib.oidc:oidc-authenticator. It does not mean you are using it as authenticator, but it’s there (and this listener receives events whether or not the authenticator is used, it just does do anything).
As I said, it does not break anything, it just log errors.
03-Feb-2025 20:38:17.069 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms1024m
03-Feb-2025 20:38:17.069 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
Actually, it’s not your problem according to your log since that does not look like the default Tomcat memory configuration. So not sure why you end up with a OOM.