Hello and thanks for looking into the issue. Yes I see these logs when redeploying the war:
2025-02-25 08:53:57,076 [Catalina-utility-2] DEBUG o.a.s.i.e.StrutsExecutorProvider - Shutting down executor 2025-02-25 08:53:57,077 [Catalina-utility-2] DEBUG o.a.s.i.e.StrutsExecutorProvider - Shutting down executor 2025-02-25 08:53:57,077 [Catalina-utility-2] DEBUG c.o.x.c.ConfigurationManager - Destroying all providers. In these days I continued to investigate the problem I think it’s more related to wildfly XNIO that is not shutting down correctly (even if we call the shutdown method in a web context listener) and this may cause struts classes to stay in memory. So it may be a XNIO issue rather than a struts issue. If you have any hint on what to look into it would be greatly appreciated. Thanks > On 24 Feb 2025, at 15:15, Lukasz Lenart <lukaszlen...@apache.org> wrote: > > sob., 22 lut 2025 o 13:16 Ing. Andrea Vettori <a.vett...@b2bires.com> > napisał(a): >> Hope someone can give me an hint on what to look into. I tried to navigate >> the two objects with the memory analyzer but it’s too difficult to >> understand what’s going on. > > Could you increase log level to DEBUG and check if you see "Destroying > all providers." in logs just before redeploy? > > > Regards > Łukasz > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org >
