https://bz.apache.org/bugzilla/show_bug.cgi?id=66005
--- Comment #19 from Josef Čejka <jce...@suse.cz> --- I have two customers reporting the same issue on SLES15-SP4 but I can't reproduce it by myself. With additional debug messages like in comment #11 log showed that it crashed when jk_resolve() was reusing jk_apr_pool with address that was correctly initialized in previous jk_resolve call. However in time of reuse the memory pointed to by jk_apr_pool contained "random" data and also "pconf" pool passed to jk_resolve() as "pool" argument had not jk_apr_pool in it's list of children. When I tried to reproduce the pool was never reused because it was called only once during module initialization and every apache ap_config_generation generation caused module was unload/load and it reset the jk_apr_pool variable back to NULL. To fix it I created a patch that creates new pool on every jk_resolve() call as suggested in comment #18. With this customers reported that the issue is fixed. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org