You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/04/29 21:01:26 UTC
DO NOT REPLY [Bug 44904] New: Provide warning message when
DataSource'
s maxActive="0"
https://issues.apache.org/bugzilla/show_bug.cgi?id=44904
Summary: Provide warning message when DataSource's maxActive="0"
Product: Tomcat 5
Version: 5.5.26
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: belingueres@yahoo.com.ar
Hi,
While I was trying to set up a Tomcat 5.5.26, using an old configuration from a
Tomcat 5.5.9, I did copy & paste of a datasource with the following form:
<Resource
name="jdbc/MySQLDS"
type="javax.sql.DataSource"
password="password"
driverClassName="com.mysql.jdbc.Driver"
maxIdle="8"
maxWait="5000"
validationQuery=""
username="username"
url="jdbc:mysql://localhost:3306/mydatabase?zeroDateTimeBehavior=convertToNull"
maxActive="0" />
This works under 5.5.9, but it doesn't work on 5.5.26. Both databases are the
same (MySQL 5.0.x) and equal JDBC driver (MySQL 5.0.3)
Changing the maxActive attribute to some positive or negative value it will
start working.
The maxActive="0" will refuse to get a connection from the database and will
throw an exception because of the exhausted timeout period.
This is clear to me now after being researching the issue, but it would be nice
to add at least a WARNING in a log file when detected that maxActive="0".
(Don't know if this enhacement belongs to Tomcat or DBCP, though.)
Regards,
Gabriel
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44904] Provide warning message when DataSource's
maxActive="0"
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44904
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #2 from Mark Thomas <ma...@apache.org> 2012-01-15 21:54:20 UTC ---
There are far too many configuration settings that can me set in ways likely to
break things to add warnings for every one. It does make sense to do this for
frequent mistakes. I don't see this happening often enough to justify adding
the warning.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 44904] Provide warning message when DataSource's
maxActive="0"
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44904
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Unknown |Catalina
Version|5.5.26 |unspecified
Product|Tomcat 5 |Tomcat 7
--- Comment #1 from Mark Thomas <ma...@apache.org> 2011-12-20 20:36:48 UTC ---
This Tomcat 5 enhancement request has been moved to Tomcat 7 (the latest
version) since Tomcat 5 development is limited and focussed on bugs and
security issues whereas Tomcat 7 is still seeing new feature development.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org