Two comments below. fillup
>> Are you closing your Oracle connections? Are there too many open connections? > I am using an Oracle implementation of connection pool. Every user that log on > system get an connection from that pool. The connection will not br released > until this user close the browser window, or > the tomcat session gets timeout (30 minutes). > Tomcat is hanging with 130 (more or less) connections out of the pool (about > 110 users). This is the wrong way to use a connection pool, unless you have a very narrow set of specific theoretical requirements, which I still have never seen in practice. Each REQUEST should be grabbing a connection and returning it to the pool, not each SESSION. Using it for sessions in fact makes your pool worse and slower than just opening a new connection for each request with zero pooling. You're using the pool in the wrong way. > >> >> I have had this problem before where my db connected application had not >> committed it's transaction and ended up hanging tomcat. Always check to see >> that your resources are being released and > not halting other requests. > Our methods that use/need transaction (doing updates or deletes) always do > commit or rollback, BUT, for connections that only do "select" querys, commit > or rollback are never called. MAY THIS BE > A PROBLEM???? Remember that an connection is associated with the user > (browser) session... see Connection.setAutoCommit( ) > > > >> >> Since you're using Oracle, check the V$SESSION view to make sure you don't >> have more active connections than you believe you should have. Check the >> v$session_wait to make sure nothing is > blocked. I'll bet a t-shirt that it's a db problem. If you can't get to those > views, ask your friendly dba to help. > I am already doing this for a long time, and we are not having this problem. > > > > Well, just to inform about our situation: > our application is already in production, and there is about 300 users TRYING > to use-it... Another thing, our company depends 100% of this software. > > More about our structure: > we are using an arrowpoint cluster with 2 Sun UltraSparc (see descriptions > below). And fortunetly, wen tomcat hangs in one machine, the users can go the > another tomcat. BUT, at every tomcat stop, > all users of that machine have to re-login into the another tomcat (because > the user loose his session). > > > Any other help? Any idea?? > > Please, we are almost givin up of tomcat and changing to another payed > solution (like Websphere, JRun, ...) > > PS: we are trying to solve this problem since 4 months ago!!! We arealdy tried > A LOT of alternatives solutions... We neen and serius help. > > > > thank you all in advance, > > > Wagner Danda > [EMAIL PROTECTED] > Sun Java Certified Programmer for the Java 2 [tm] > >> >>>>> [EMAIL PROTECTED] 05/28/02 07:24PM >>> >> Here, we have the same problem!!! What can it be? >> >> Our configuration: >> >> - SunOS 5.8; >> - Solaris 8; >> - Dual UltraSparc 400Mhz; >> - J2SE SUN 1.4; >> - Tomcat 4.0.3; >> - We are using -Xmx1024 -Xms512; >> - MaxProcessors=250, MinProcessors=10, acceptCount=250; >> - Oracle Thin JDBC; >> >> PS 1: we are not having the "classic" OutOfMemory error. Tomcat just >> hangs-up with no reason. >> PS 2: We already used OptimizeIt to tune the application. >> PS 3: Tomcat stops even with a low rate of usage. >> >> Wagner Danda >> >>> ---------- Mensagem original ----------- >>> >>> De : "Rui Oliveira" <[EMAIL PROTECTED]> >>> Para : <[EMAIL PROTECTED]> >>> Cc : >>> Data : Tue, 28 May 2002 18:54:36 +0100 >>> Assunto : Tomcat Hangs-UP... >>> >>> Hello, >>> >>> >>> >>> I have a Tomcat Server running on Solaris as JSP and WEB server. Aft >> er >>> executing for a while, the Tomcat just Hangs-UP and the only way of >>> restarting it is to kill the Tomcat process. >>> >>> >>> >>> My configuration is the following: >>> >>> >>> >>> - SunOS 5.8 >>> >>> - Solaris 8 >>> >>> - JRE 1.3.1_03 >>> >>> - Tomcat 4.0.3 >>> >>> >>> >>> Does anyone have a clue on what is the problem? >>> >>> >>> >>> >>> >>> Regards >>> >>> Rui Oliveira >>> >>> >>> >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> >> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
