On 23/07/2025 15:36, Daniel Sheridan wrote:
<snip/>
Hi Rainer,
it might be a search for non-existing classes or resources
The JARs are being scanned for specific classes during the delay, but they are
classes that should already be loaded in, which is the confusing bit.
I've got the highest log level set on org.apache.catalina.loader and
org.apache.catalina.webresources already, but no signs of the classes being
unloaded at any point before the delay occurs unfortunately.
Can we see the full stack trace for the first time one of these classes
is loaded and any subsequent loads of the same class.
Possible causes include:
- same class being loaded by different class loaders
- some transformation is taking place so each load is actually creating
a different class
- something else I haven't thought of yet
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
