MArtin, you are correct i think, even after destroying/closing the connection. it is still in ESTABLISHED status. We are using DBCP pool... the resource in context is <Resource auth="Container" description="Hcare Database DSN" name="jdbc/merge_emr_billing" scope="Shareable" type="javax.sql.DataSource" url="jdbc:postgresql://1.1.1.180/asasas" driverClassName="org.postgresql.Driver" username="asasas" password="shshsh" maxActive="10" maxIdle="1" minIdle="0" removeAbandoned="true" removeAbandonedTimeout="60" logAbandoned="true" maxWait="6000" minEvictableIdleTimeMillis="60000" timeBetweenEvictionRunsMillis="600000" numTestsPerEvictionRun="300" />
The page is very simple, it will get the connection string, with help of it , it will make connection, run a simple query and destroy the connection in finally block.. all lays in a jsp file.. - Arvind S "Many of lifes failure are people who did not realize how close they were to success when they gave up." -Thomas Edison On Mon, May 25, 2009 at 10:42 PM, Martin Gainty <mgai...@hotmail.com> wrote: > > any activity by DB would be moot if the servlet's connection to client has > already been torn down on 1 side > http://www.mail-archive.com/users@tomcat.apache.org/msg61272.html > > can you run > netstat -an > to verify your connections are NOT in close_wait or time_wait? > > we would need to see all connection params from server.xml, > <application>context.xml, web.xml > jsp and all servlet code > > regards > Martin Gainty > ______________________________________________ > Jogi és Bizalmassági kinyilatkoztatás/Verzicht und > Vertraulichkeitanmerkung/Note de déni et de confidentialité > Ez az > üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy > jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának > készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és > semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek > könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet > ezen üzenet tartalma miatt. > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > > > From: arvindw...@gmail.com > > Date: Mon, 25 May 2009 21:53:02 +0530 > > Subject: Re: maxwait in dbconnetion is not workiing for first time. > > To: users@tomcat.apache.org > > > > can anyone help me in this... i am trapped here ... > > > > > > - Arvind S > > > > > > "Many of lifes failure are people who did not realize how close they were > to > > success when they gave up." > > -Thomas Edison > > > > > > On Tue, May 19, 2009 at 12:57 AM, S Arvind <arvindw...@gmail.com> wrote: > > > > > Martin , i think its not session, since i tried same thing in wget, > first > > > time with network connection is working fine. > > > but without network connection , status is keep on waiting for > response. I > > > think linux wget will have session management or any i think. will be > any > > > other probs.. i cant use session.invalidate , since if the page is > called > > > from main application then the current all session attributes will be > blown > > > away... > > > > > > Arvind S > > > > > > > > > > > > > > > * > > > "Many of lifes failure are people who did not realize how close they > were > > > to success when they gave up." > > > -Thomas Edison* > > > > > > > > > On Mon, May 18, 2009 at 7:05 PM, Martin Gainty <mgai...@hotmail.com > >wrote: > > > > > >> > > >> means your session to TC is still live > > >> suggest attenuate connectionTimeout in connector config in server.xml > > >> > > >> in code you can always session.invalidate() > > >> > > >> > http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#invalidate()<http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#invalidate%28%29> > < > http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSession.html#invalidate%28%29 > > > > >> > > >> Martin Gainty > > >> I have not failed. I've just found 10,000 ways that won't work - > edison > > >> ______________________________________________ > > >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de > confidentialité > > >> > > >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > > >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede > unbefugte > > >> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese > Nachricht > > >> dient lediglich dem Austausch von Informationen und entfaltet keine > > >> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit > von > > >> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes > pas le > > >> destinataire prévu, nous te demandons avec bonté que pour satisfaire > > >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la > copie > > >> de ceci est interdite. Ce message sert à l'information seulement et > n'aura > > >> pas n'importe quel effet légalement obligatoire. Étant donné que les > email > > >> peuvent facilement être sujets à la manipulation, nous ne pouvons > accepter > > >> aucune responsabilité pour le contenu fourni. > > >> > > >> > > >> > > >> > > >> > From: arvindw...@gmail.com > > >> > Date: Mon, 18 May 2009 16:55:30 +0530 > > >> > Subject: maxwait in dbconnetion is not workiing for first time. > > >> > To: users@tomcat.apache.org > > >> > > > >> > This time i have problem in maxwait. To test the maxwait i tried to > > >> > establish the connection and close. > > >> > My dbserver is located outside my system, so for dbconnection > network is > > >> > required as per our Production server model. > > >> > > > >> > So first i established the connection first from the jsp page, it > gets > > >> done. > > >> > After that i plugged-out my network cable and tried to make > connection > > >> by > > >> > that same jsp file, but i didnt get exception , it keep on running. > but > > >> if i > > >> > refreshed the page again after few mins the exception is coming. but > why > > >> not > > >> > in first request itself. I need it in first request itself for my > > >> failover > > >> > model. my maxwait is 1000ms > > >> > > > >> > <Resource auth="Container" description="Database DSN" > > >> name="jdbc/dbname" > > >> > scope="Shareable" type="javax.sql.DataSource" > url="jdbc:postgresql:// > > >> > 1.1.1.180/dbname" driverClassName="org.postgresql.Driver" > > >> username="xxxx" > > >> > password="yyyyy" maxActive="10" maxIdle="1" minIdle="0" > > >> > removeAbandoned="true" removeAbandonedTimeout="60" > logAbandoned="true" > > >> > maxWait="1000" /> > > >> > > > >> > Is it bug or my mistake ? > > >> > > > >> > -Arvind S > > >> > > > >> > > > >> > > > >> > > > >> > * > > >> > "Many of lifes failure are people who did not realize how close they > > >> were to > > >> > success when they gave up." > > >> > -Thomas Edison* > > >> > > >> _________________________________________________________________ > > >> Hotmail® goes with you. > > >> > > >> > http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009 > > >> > > > > > > > > _________________________________________________________________ > Hotmail® has a new way to see what's up with your friends. > > http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009 >