I understand your reasoning on moving to new versions. I shouldn't say we're not willing to move to 2022.12, it is just unfortunate that doing so requires this other big change point (Java 17), when there is this other large problem (OOM Java heap space) we're trying to solve. We could move to 2022.03 LTS right now, but from earlier posts in this thread, it appears as though we'll still have the OOM problem. So perhaps we'll wait until the new 2022.03 LTS with the fixes is released.
Are you able to comment on my other questions:
You say there are multiple things that could be causing the java.lang.OutOfMemoryError: Java heap space error. Do they all eventually lead to "websocket disconnected" clients? which in turn cause the Java heap space error? If so, I can monitor our UAT environment and see if there are any "websocket disconnected" clients.
I'm not convinced that it is programming errors in our solution code, only because we weren't encountering the error with a 2020.06 .war file... unless there are changes within Servoy between 2020.06 and 2022.09 that would 'expose' such solution code and cause the error. Perhaps that's what you're referring to with the fixes in 2022.12?
Additionally, I've uploaded the relevant logging from our servoy application log file in the lead up to the OOM - Java heap space error, in case there are some clues. There are certainly some log messages that I haven't seen before. Perhaps you could take a quick look.
Thanks again.