On 19/11/2020 15:55, Eric Robinson wrote: >> From: Mark Thomas <ma...@apache.org> >> Sent: Thursday, November 19, 2020 4:34 AM >> To: users@tomcat.apache.org >> Subject: Re: Weirdest Tomcat Behavior Ever? >> >> On 18/11/2020 16:28, Mark Thomas wrote: >>> On 18/11/2020 15:41, Eric Robinson wrote: >> >> <snip/> >> >>>> I tested it and we're now capturing file descriptor operations. >> >> <snip/> >> >>> I am very curious as to what we are going to see in these logs. >> >> Good news. We are a step closer to figuring out what is going on. >> >> The new strace logs show the file descriptor associated with the socket being >> closed. That means that the socket close MUST be coming from within the >> JVM. The key lines in the strace output that show this are (I've removed >> unrelated events from between these entries): >> >> 19166 15:24:21.108653 (+ 0.000020) dup2(50, 336 <unfinished ...> >> 19166 15:24:21.108722 (+ 0.000017) <... dup2 resumed>) = 336 >> 19166 15:24:21.108778 (+ 0.000027) close(336 <unfinished ...> >> 19166 15:24:21.109015 (+ 0.000152) <... close resumed>) = 0 >> >> Has the Tomcat instance on the machine you obtained the last set of logs >> from been restarted since you obtained the logs? If not it should be possible >> to identify the thread that triggered the socket close as follows: >> > > Sounds promising! > > Unfortunately, the tomcats get restarted every night, so I'll have to watch > closely for the error to happen today and I will do a thread dump as close as > possible to the time of the error.
Sounds good. Tx. My guess based on what I saw in the strace is that the thread will be something database related. Which database and which database driver (version number etc) is in use? In particular, are there any native components to the JDBC driver? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
