Thanks. We'll remove the timeout and sync the maxthreads to the iis.
And if tomcat (java/jsp) itself is reading xml from itself we should take that in account I presume or is java it going on the other connector 8080/80? /regards per jonsson -----Original Message----- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: den 2 oktober 2006 21:00 To: Tomcat Users List Subject: Re: Help on settings jk 1.2.19, tomcat 5.5.12 with IIS 6.0 (own thread) Per Johnsson wrote: > Hi! > > (Now own thread, sorry about the previouse stealing) > Great :) > worker.ajp13w.connection_pool_size=100 > //from the docs: It means: The maximum number of connections from IIS to Tomcat > > worker.ajp13w.connection_pool_timeout=60 Comment (delete) this one. Connection pool timeout is used when you have a connection pool larger then maxThreads in server.xml Regards, Mladen. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ******************************************************************************** This e-mail and the information it contains may be privileged and/or confidential. It is for the intended addressee(s) only. The unauthorised use, disclosure or copying of this e-mail, or any information it contains, is prohibited. If you are not an intended recipient, please contact the sender and delete the material from your computer. ******************************************************************************** --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
