Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 31656 invoked from network); 1 Jan 2003 15:59:00 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 1 Jan 2003 15:59:00 -0000 Received: (qmail 12513 invoked by uid 97); 1 Jan 2003 15:59:58 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 12497 invoked by uid 97); 1 Jan 2003 15:59:57 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 12485 invoked by uid 98); 1 Jan 2003 15:59:56 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3E13102B.9050801@apache.org> Date: Wed, 01 Jan 2003 16:58:35 +0100 From: Remy Maucherat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: SSL hangs on Tomcat 4.1.18 References: <3E0F2929.40400@apache.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Carl Zetterberg wrote: > Xiaojian Wang of infowisesys.com writes: > > "After starting Tomcat , open a navigator to visit any page,then press F5 > to fresh.After a few minutes,a message accured: "All threads are busy, > waiting. Please increase maxThreads or check the servlet status75 75" 75 > is the maxProcess of my setting. It's a normal message that sugguest you > to increst your mxProcessing setting. In normal mode,tomcat accept new > connection after processed the pooled connection. But in SSL mode,it > hang!!!" > > And he suggests a solution: > > "... download the source code jakarta-tomcat-connectors-4.1.18-src on www. > apache.org, change PoolTcpPoint.java at: > Line 515:continue==>break > Line 528:continue==>break > Maybe you also have to change > Line 434 from > if(linger >= 0 ) > socket.setSoLinger( true, linger); > to > //if(linger >= 0 ) > //socket.setSoLinger( true, linger); > because soLinger is OS sensitive.Tell me if you what does soLinger mean > or how to set it :-( > > Recompile and replace the relate class in tomcat-uitl. > > I believe it work well." > > Going to try this when I get to work tomorrow. The report is valid (although a bit hard to understand). Only the change for line 515 is useful (as well as a change of the logging priority line 510 to debug to avoid abusive logging). The if block line 527-528 should be removed (it cannot happen). The soLinger doesn't seem harmful. Remy -- To unsubscribe, e-mail: For additional commands, e-mail: