Just to let you know, I've deployed the wicket7.x version of the Wicket
jQuery UI demo webapp on my tomcat server about 2 weeks ago... Everything
is working fine, no leak at all so far!
So I think it's safe to say the leak is coming from wicket 8.x. I saw the
comments about the log4j issue and the PageStore issue (but this one was
reported for wildfly IIRC).
Was the log4j issue affecting the wicket8.x branch only? Is there anything
I can test these days on my wicket8.x version?

Thanks in advance :)
Sebastien.

Reply via email to