Re: Tomcat jdbc settings

2006-03-11 Thread Mark Thomas 
When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this  makes your new message appear as part
of the old thread. This makes it harder for other users to find
relevant information when searching the lists.

This is known as thread hijacking and is behaviour that is frowned
upon on this list. Frequent offenders will be removed from the list.
It should also be noted that many list subscribers automatically
ignore any messages that hijack another thread.

The correct procedure is to create a new message with a new subject.
This will start a new thread.

Mark
tomcat-user-owner




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat jdbc settings

2006-03-10 Thread Edward Quick 

Hi,

I have set up Tomcat 4.1.31 with a JDBC pool using the settings below. 
However I 'm a bit confused about my the way this works.


1. InitialSize is set to 5 yet I don't see any connections started after 
Tomcat is bounced.

2. Some of the older connections are not getting cleared down.
3. Although maxIdle is set to 5, I still get more than 5 idle connections.

I have referred to the documentation on:
http://jakarta.apache.org/commons/dbcp/configuration.html

and tried to set accordingly as below. Could someone with more experience 
comment on these please, and recommend any changes I need to make?


Many thanks,

Ed.

   Context path=/POL docBase=/b7/apache/b7uat08/webapps/POL 
debug=0

   Logger className=org.apache.catalina.logger.FileLogger
prefix=POL. suffix=.log timestamp=true/

   Resource name=jdbc/pol auth=Container 
type=javax.sql.DataSource/


   ResourceParams name=jdbc/pol
   parameter
   namefactory/name
   
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value

   /parameter
   parameter
   nameusername/name
   valuexxx/value
   /parameter
   parameter
   namepassword/name
   valuexxx/value
   /parameter
   parameter
   namedriverClassName/name
   value/value
   /parameter
   parameter
   namedriverClassName/name
   valueoracle.jdbc.OracleDriver/value
   /parameter
   parameter
   nameurl/name
   
valuejdbc:oracle:thin:@sunlhrd36.abc.com:1538:ZJUPT/value

   /parameter
   parameter
   namemaxActive/name
   value10/value
   /parameter
   parameter
   nameinitialSize/name
   value5/value
   /parameter
   parameter
   nameminIdle/name
   value2/value
   /parameter
   parameter
   namemaxIdle/name
   value5/value
   /parameter
   parameter
   namemaxWait/name
   value1/value
   /parameter
   parameter
   namevalidationQuery/name
   valueselect 1 from dual/value
   /parameter
   parameter
   nametestOnBorrow/name
   valuetrue/value
   /parameter
   parameter
   nametestOnReturn/name
   valuefalse/value
   /parameter
   parameter
   nametestWhileIdle/name
   valuetrue/value
   /parameter
   parameter
   nameminEvictableIdleTimeMillis/name
   value6/value
   /parameter
   parameter
   nametimeBetweenEvictionRunsMillis/name
   value12/value
   /parameter
   parameter
   namenumTestsPerEvictionRun/name
   value10/value
   /parameter

   parameter
   nameremoveAbandoned/name
   valuetrue/value
   /parameter
   parameter
   nameremoveAbandonedTimeout/name
   value5/value
   /parameter
   parameter
   namelogAbandoned/name
   valuetrue/value
   /parameter
   /ResourceParams
   /Context



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat jdbc settings

2006-03-10 Thread Tim Lucia 
In my experience, using 8i and the thin driver, bouncing tomcat always
clears all connections to the DB.  Reloading the app will not necessarily
clear connections, as the old app is still in PermGen, waiting for garbage
collection.  Once collected, however, the connections will get cleaned up.



-Original Message-
From: Edward Quick [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 10, 2006 3:46 AM
To: users@tomcat.apache.org
Subject: Tomcat jdbc settings

Hi,

I have set up Tomcat 4.1.31 with a JDBC pool using the settings below. 
However I 'm a bit confused about my the way this works.

1. InitialSize is set to 5 yet I don't see any connections started after 
Tomcat is bounced.
2. Some of the older connections are not getting cleared down.
3. Although maxIdle is set to 5, I still get more than 5 idle connections.

I have referred to the documentation on:
http://jakarta.apache.org/commons/dbcp/configuration.html

and tried to set accordingly as below. Could someone with more experience 
comment on these please, and recommend any changes I need to make?

Many thanks,

Ed.

Context path=/POL docBase=/b7/apache/b7uat08/webapps/POL 
debug=0
Logger className=org.apache.catalina.logger.FileLogger
 prefix=POL. suffix=.log timestamp=true/

Resource name=jdbc/pol auth=Container 
type=javax.sql.DataSource/

ResourceParams name=jdbc/pol
parameter
namefactory/name

valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
nameusername/name
valuexxx/value
/parameter
parameter
namepassword/name
valuexxx/value
/parameter
parameter
namedriverClassName/name
value/value
/parameter
parameter
namedriverClassName/name
valueoracle.jdbc.OracleDriver/value
/parameter
parameter
nameurl/name

valuejdbc:oracle:thin:@sunlhrd36.abc.com:1538:ZJUPT/value
/parameter
parameter
namemaxActive/name
value10/value
/parameter
parameter
nameinitialSize/name
value5/value
/parameter
parameter
nameminIdle/name
value2/value
/parameter
parameter
namemaxIdle/name
value5/value
/parameter
parameter
namemaxWait/name
value1/value
/parameter
parameter
namevalidationQuery/name
valueselect 1 from dual/value
/parameter
parameter
nametestOnBorrow/name
valuetrue/value
/parameter
parameter
nametestOnReturn/name
valuefalse/value
/parameter
parameter
nametestWhileIdle/name
valuetrue/value
/parameter
parameter
nameminEvictableIdleTimeMillis/name
value6/value
/parameter
parameter
nametimeBetweenEvictionRunsMillis/name
value12/value
/parameter
parameter
namenumTestsPerEvictionRun/name
value10/value
/parameter

parameter
nameremoveAbandoned/name
valuetrue/value
/parameter
parameter
nameremoveAbandonedTimeout/name
value5/value
/parameter

RE: Tomcat jdbc settings

2006-03-10 Thread Edward Quick 

Thanks Tim.

I have also noticed that bouncing the tomcat clears the connections. So are 
you saying java's garbage collection will clear the old connections out? 
Does this mean my settings below are redundant?


Ed.


In my experience, using 8i and the thin driver, bouncing tomcat always
clears all connections to the DB.  Reloading the app will not necessarily
clear connections, as the old app is still in PermGen, waiting for garbage
collection.  Once collected, however, the connections will get cleaned up.



-Original Message-
From: Edward Quick [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 3:46 AM
To: users@tomcat.apache.org
Subject: Tomcat jdbc settings

Hi,

I have set up Tomcat 4.1.31 with a JDBC pool using the settings below.
However I 'm a bit confused about my the way this works.

1. InitialSize is set to 5 yet I don't see any connections started after
Tomcat is bounced.
2. Some of the older connections are not getting cleared down.
3. Although maxIdle is set to 5, I still get more than 5 idle connections.

I have referred to the documentation on:
http://jakarta.apache.org/commons/dbcp/configuration.html

and tried to set accordingly as below. Could someone with more experience
comment on these please, and recommend any changes I need to make?

Many thanks,

Ed.

Context path=/POL docBase=/b7/apache/b7uat08/webapps/POL
debug=0
Logger className=org.apache.catalina.logger.FileLogger
 prefix=POL. suffix=.log timestamp=true/

Resource name=jdbc/pol auth=Container
type=javax.sql.DataSource/

ResourceParams name=jdbc/pol
parameter
namefactory/name

valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
nameusername/name
valuexxx/value
/parameter
parameter
namepassword/name
valuexxx/value
/parameter
parameter
namedriverClassName/name
value/value
/parameter
parameter
namedriverClassName/name
valueoracle.jdbc.OracleDriver/value
/parameter
parameter
nameurl/name

valuejdbc:oracle:thin:@sunlhrd36.abc.com:1538:ZJUPT/value
/parameter
parameter
namemaxActive/name
value10/value
/parameter
parameter
nameinitialSize/name
value5/value
/parameter
parameter
nameminIdle/name
value2/value
/parameter
parameter
namemaxIdle/name
value5/value
/parameter
parameter
namemaxWait/name
value1/value
/parameter
parameter
namevalidationQuery/name
valueselect 1 from dual/value
/parameter
parameter
nametestOnBorrow/name
valuetrue/value
/parameter
parameter
nametestOnReturn/name
valuefalse/value
/parameter
parameter
nametestWhileIdle/name
valuetrue/value
/parameter
parameter
nameminEvictableIdleTimeMillis/name
value6/value
/parameter
parameter
nametimeBetweenEvictionRunsMillis/name
value12/value
/parameter
parameter
namenumTestsPerEvictionRun/name
value10/value
/parameter

parameter
nameremoveAbandoned/name
valuetrue/value
/parameter
parameter

RE: Tomcat jdbc settings

2006-03-10 Thread Tim Lucia 
No, I am not saying that.  I am saying that the connections, being returned
to the pool on connection.close(), remain open as long as they are not
garbage.  When a context is reloaded, the previous context hangs around for
a while.  That context holds reference(s) to the pool, which in turn holds
reference(s) to open connections.  Once the context is gc'd, then the
cascade effect is to close the connections.

Bouncing the entire tomcat server will always close all the connections,
because all contexts are shut down and garbage collected.

Tim

P.s. See this:

http://marc.theaimsgroup.com/?l=tomcat-userm=114001512903342w=2

(which still has no answer, BTW.  Anyone have one?  I'd be happy enough to
be able to manually shut down the pool on my
ServletContextListener.contextDestroyed())


-Original Message-
From: Edward Quick [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 10, 2006 7:50 AM
To: users@tomcat.apache.org
Subject: RE: Tomcat jdbc settings

Thanks Tim.

I have also noticed that bouncing the tomcat clears the connections. So are
you saying java's garbage collection will clear the old connections out? 
Does this mean my settings below are redundant?

Ed.

In my experience, using 8i and the thin driver, bouncing tomcat always 
clears all connections to the DB.  Reloading the app will not 
necessarily clear connections, as the old app is still in PermGen, 
waiting for garbage collection.  Once collected, however, the connections
will get cleaned up.



-Original Message-
From: Edward Quick [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 3:46 AM
To: users@tomcat.apache.org
Subject: Tomcat jdbc settings

Hi,

I have set up Tomcat 4.1.31 with a JDBC pool using the settings below.
However I 'm a bit confused about my the way this works.

1. InitialSize is set to 5 yet I don't see any connections started 
after Tomcat is bounced.
2. Some of the older connections are not getting cleared down.
3. Although maxIdle is set to 5, I still get more than 5 idle connections.

I have referred to the documentation on:
http://jakarta.apache.org/commons/dbcp/configuration.html

and tried to set accordingly as below. Could someone with more 
experience comment on these please, and recommend any changes I need to
make?

Many thanks,

Ed.

 Context path=/POL docBase=/b7/apache/b7uat08/webapps/POL
debug=0
 Logger className=org.apache.catalina.logger.FileLogger
  prefix=POL. suffix=.log timestamp=true/

 Resource name=jdbc/pol auth=Container
type=javax.sql.DataSource/

 ResourceParams name=jdbc/pol
 parameter
 namefactory/name

valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
 /parameter
 parameter
 nameusername/name
 valuexxx/value
 /parameter
 parameter
 namepassword/name
 valuexxx/value
 /parameter
 parameter
 namedriverClassName/name
 value/value
 /parameter
 parameter
 namedriverClassName/name
 valueoracle.jdbc.OracleDriver/value
 /parameter
 parameter
 nameurl/name

valuejdbc:oracle:thin:@sunlhrd36.abc.com:1538:ZJUPT/value
 /parameter
 parameter
 namemaxActive/name
 value10/value
 /parameter
 parameter
 nameinitialSize/name
 value5/value
 /parameter
 parameter
 nameminIdle/name
 value2/value
 /parameter
 parameter
 namemaxIdle/name
 value5/value
 /parameter
 parameter
 namemaxWait/name
 value1/value
 /parameter
 parameter
 namevalidationQuery/name
 valueselect 1 from dual/value
 /parameter
 parameter
 nametestOnBorrow/name
 valuetrue/value
 /parameter
 parameter
 nametestOnReturn