On July 16, 2019 4:38:46 PM UTC, "Rémy Maucherat" <r...@apache.org> wrote: >On Tue, Jul 16, 2019 at 6:34 PM Manuel Dominguez Sarmiento ><m...@renxo.com> >wrote: > >> We could find no Java deadlocked threads at all by inspecting >jconsole >> (not with the automatic "find deadlocks" functionality, nor by >inspection >> of a thread dump). We performed several thread dumps WHILE the >deadlock was >> clearly visible on screen (this was very easily reproduceable). >> >> The deadlock is definitely there though and goes away as soon as we >turn >> off "useAsyncIO". >> Since we could not find Java-level deadlocks, we believe the problem >> probably lies in the interaction with native code. >> We are using org.apache.catalina.core.AprLifecycleListener as well as >> Tomcat Native 1.2.23 on Linux. >> We could not find any pointers in the Tomcat Native changelog dealing >with >> similar issues. >> > >Ok, so if you would like to continue investigating please use the user >list. This is not a "deadlock", but rather a request not completing >properly for some reason.
Indeed. Deadlock is probably not exactly the right term. But if the OP can provide a thread dump taken when the issue is occurring that is likely to be helpful in pointing us in the right direction. As a minimum, we'll be able to tell if this is a similar issue to the one previously fixed. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
