I checked the stuck and i got to a few conclusions: after tomcat stops receiving messages it will receive some kinds and some not: 1. if i use http client and write a string directly the tomcat will receive the data 2. if i use http client and write a stream, the tomcat will not receive the data 3. if i use wget and send a message to tomcat it will receive data
which means, that after tomcat works with a load of data it gets stuck to streams and not to strings (maybe related to the fact that i use nio connector??) Does any one have any idea on this problem with tomcat???? any help will be highly appreciated. Thanks, Michal Peter Crowther wrote: > >> From: Christopher Schultz [mailto:[EMAIL PROTECTED] >> acceptCount="200" just means that the socket will accept 200 >> clients /in >> addition/ to those currently being served by RequestProcessor threads. >> The only way to "see" those waiting clients would be to query >> the socket itself (maybe only available at the C-library level?). > > Rarely even that - these connections are held "in limbo" in the kernel. > There are sometimes ways of examining the next request in the queue (to > see whether you want to accept it or reject it), but I'm not aware of a > general way of examining *all* requests in an accept queue. I'd love to > hear about any that exist, as in the past I've needed to monitor these! > > - Peter > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tomcat-request-processing-gets-stuck-tp20526036p20835816.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
