Dear Guido, thanks for the reply. The requests are reaching tomcat, and a thread is always started, if I look at the current threads on the tomcat manager I see the following, there are 4 threads that are processing since 2+ hours:
R ? ? ? ? ? ? S 16 ms 0 KB 0 KB 0:0:0:0:0:0:0:1 0:0:0:0:0:0:0:1 localhost GET /manager/status HTTP/1.1 S 7256779 ms 0 KB 33 KB 0:0:0:0:0:0:0:1 0:0:0:0:0:0:0:1 localhost POST /cloudworx/?method=words&id=17385 HTTP/1.1 S 7274046 ms 0 KB 33 KB 0:0:0:0:0:0:0:1 0:0:0:0:0:0:0:1 localhost POST /cloudworx/?method=words&id=18986 HTTP/1.1 S 7228088 ms 0 KB 33 KB 0:0:0:0:0:0:0:1 0:0:0:0:0:0:0:1 localhost POST /cloudworx/?method=words&id=10560 HTTP/1.1 R ? ? ? ? ? ? S 7290093 ms 0 KB 33 KB 0:0:0:0:0:0:0:1 0:0:0:0:0:0:0:1 localhost POST /cloudworx/?method=words&id=10560 HTTP/1.1 I'm not sure what other metrics would be helpful, but your Unix script wouldn't help much, as I am on a Windows Server 2012 and I would like to avoid installing Cygwin or something similar. Regards, Daniel Am Do., 14. März 2019 um 12:02 Uhr schrieb Jäkel, Guido <g.jae...@dnb.de>: > > Dear Daniel, > > a request is logged in the access log after it has finished. (In addition, on > Tomcat the log is flushed with some delay, but that's not the problem here). > > But if the request is stall while processing, there's no hint in the access > log. Therefore: Is there an application log that may confirm that the request > have reached the application on Tomcat and have start to process? > > On Tomcat, there's also a request scoreboard feature where you may "live > watch" outstanding requests. You may access to it via the Tomcat Host Manager > Application. As a hint, I may also provide you a short (Unix) script to > readout this from the MBean by HTTP via the jmxproxy-Feature of the Manager. > > Greetings > > Guido > > >-----Original Message----- > >From: Daniel Castilla | thin(k)design [mailto:d...@thin-k-design.com] > >Sent: Thursday, March 14, 2019 11:10 AM > >To: users@tomcat.apache.org > >Subject: Crash in http connector random once a day > > > >The strange thing is, those failed requests with no response are > >logged in the tomcat access logs with a 500 http connection error all > >at the same time (although they begun with 1-2 min difference) and > >after 8 to 24 hours (the URL is alway unique, so I know for sure). > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
