RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-19 Thread sinoea kaabi
ource; } } > Date: Thu, 18 Sep 2008 11:56:33 -0400 > From: [EMAIL PROTECTED] > To: users@tomcat.apache.org > Subject: Re: Tomcat 5.5, JNDI Connection Pooling, Active connections keep > increasing > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > sinoe

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keepincreasing....

2008-09-18 Thread sinoea kaabi
18, 2008 5:26 AM > Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active connections > keepincreasing > > > > From: sinoea kaabi [mailto:[EMAIL PROTECTED] > > Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active > > connections keepincreasing > >

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keepincreasing....

2008-09-18 Thread sinoea kaabi
.org > Date: Wed, 17 Sep 2008 22:26:16 -0500 > Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active connections > keepincreasing.... > >> From: sinoea kaabi [mailto:[EMAIL PROTECTED] >> Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active >> connections keepincrea

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-17 Thread sinoea kaabi
This question about static variables seems a bit deeper than I thought, the more I think about it the more confused I get. I could accept the fact that we should create new objects of Dao's, but for getting a datasource or connection it should make sense to have a utility class with static metho

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-17 Thread sinoea kaabi
); >initContext.close(); >return ds; > } catch (final NamingException e) { >e.printStackTrace(); >throw new RuntimeException("Java naming exception when > getting connection from tomcat pool: " + e.getMessage()); >

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-17 Thread sinoea kaabi
a > From: [EMAIL PROTECTED] > To: users@tomcat.apache.org > Subject: Re: Tomcat 5.5, JNDI Connection Pooling, Active connections keep > increasing > Date: Wed, 17 Sep 2008 12:25:17 +0200 > > > - Original Message - > From: "sinoea kaabi" > To: "Tomcat

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-17 Thread sinoea kaabi
p 2008 12:25:17 +0200 > > > - Original Message - > From: "sinoea kaabi" <[EMAIL PROTECTED]> > To: "Tomcat Users List" > Sent: Wednesday, September 17, 2008 11:31 AM > Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep &

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-17 Thread sinoea kaabi
Thanks, First I will try to close resources before returning. Although I am sure that the finally blocks are reached, since I use logging in the last finally block and the log is outputted. try { } finally { connection.close(); Data.logConnection(connection); // this is logged } But I

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-16 Thread sinoea kaabi
eated that you establish. > > > > -Original Message- > From: sinoea kaabi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 16, 2008 9:56 AM > To: Tomcat Users List > Subject: RE: Tomcat 5.5, JNDI Connection Pooling, Active connections > keep increasing > >

RE: Tomcat 5.5, JNDI Connection Pooling, Active connections keep increasing....

2008-09-16 Thread sinoea kaabi
ounds like you're not explicitly killing off the connections you set in > the first place. > > -Original Message- > From: sinoea kaabi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 16, 2008 4:24 AM > To: users@tomcat.apache.org > Subject: Tomcat 5.5, J