-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Konstantin,
On 12/22/2010 11:56 AM, Konstantin Kolinko wrote: > If closing the result set requires reading it in full (as JTDS does), > it can take significant time. Especially if the queries are something like SELECT * FROM huge_table > You should take thread dumps to see what the threads are doing and > what they are waiting for. (Three thread dumps taken several seconds > apart). I would also inspect the queries that are in progress when these connections appear to hang. We had a problem with Oracle long ago where the table indexes had just become horribly fragmented and performance slowed to a crawl. In an act of desperation, someone ran "OPTIMIZE TABLE" on one of the tables involved in particularly slow queries and basically everything got better. From then on out, we called that "turning off the 'suck' bit" on Oracle. :) I would definitely like to see what queries are running on the server and what their status is. The problem is certainly /not/ Tomcat, here: threads are stuck in a 3rd-party library connecting to a 3rd-party database. Tomcat just happens to be in the stack trace because that's the DBCP in use: the driver appears to be hanging, not Tomcat's DBCP. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0SNXUACgkQ9CaO5/Lv0PDAUQCfWgdgZY61qly2Z0xDP4vhZcbX OyYAn14lv4chUAmiD4h4z3jqgDPxOGda =Fqs8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
