Bug Report: Memory leak in Payara Micro 6.2025.1?

[pioneer2k]

Brief Summary

We have used almost all versions of Payara Micro of the last years with almost the same setup and we had never any problem. But this time we had to rollback from version 6.2025.1 to 6.2024.12 because the new version is using all the available memory of 4GB after some ours. With the old version our application is using around 1.5GB all the time. Please see the diagrams below.
Does anyone else is experiencing this with 6.2025.1?

Expected Outcome

The diagram shows the memory usage with versions 6.2025.1 and 6.2024.12. Before Jan 23 and after Jan 27 the version 6.2024.12 was running and everything was fine. And between these two dates the version 6.2025.1 was running and the memory usage was increasing all the time until we restarted our services. The expectation is that version 6.2025.1 behaves like all versions before.

Current Outcome

See above unter "expected outcome"

Reproducer

We do not have a reproducer and cannot provide our application

Operating System

Alpine Linux

JDK Version

Zulu JDK 21.0.6 and 21.0.5

Payara Distribution

Payara Micro

[artur-mal]

Please provide a reproducer that demonstrates the memory leak in Payara Micro 6.2025.1
This information is crucial for identifying and fixing the issue effectively.

[marcreichman-pfi]

@pioneer2k I came here because I am suddenly experiencing heap warnings from my application which recently upgraded to 2025.1 as well, the regular server though instead of micro. I cannot share any reproducer at this time but we have a well behaved application which hasn't had any real changes except for this upgrade recently.

@artur-mal In lieu of reproduction code, is there a way to get certain snapshots or heap information which could shed some light?

[pioneer2k]

That was my hope that others are experiencing somehow the same. I am unfortunately not able to build a reproducer because our application has massive dependencies to external services that will not run in other environments. And a stripped down application may not have the same issues.

[github-actions]

Greetings,
It's been more than 5 days since we requested more information or an update from you on the details of this issue. Could you provide an update soon, please?
We're afraid that if we do not receive an update, we'll have to close this issue due to inactivity.

[marcreichman-pfi]

Just comparing the diff it looks like virtually no actual code has changed, but plenty of dependency updates have come in. This seems like it might be hard to track down.