Bug 702037 - Default JNDI factory used by tomcat5 for javax.sql.DataSource not available in standard jars
Summary: Default JNDI factory used by tomcat5 for javax.sql.DataSource not available i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat5
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 15:43 UTC by Alain Knaff
Modified: 2013-02-14 01:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 01:13:37 UTC
Type: ---


Attachments (Terms of Use)

Description Alain Knaff 2011-05-04 15:43:09 UTC
Description of problem:

By default, tomcat5 uses org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory for resources of type javax.sql.DataSource, but this class is no longer defined anywhere in the jars included in the Fedora 15 RPMs


Version-Release number of selected component (if applicable):

# rpm -q tomcat5
tomcat5-5.5.31-3.fc15.noarch

How reproducible:

always

Steps to Reproduce:
1. Define a javax.sql.DataSource:

<Resource name="jdbc/testDB" auth="Container"
            type="javax.sql.DataSource" username="me" password="secret"
            driverClassName="org.gjt.mm.mysql.Driver" 
            url="jdbc:mysql://localhost:3306/test"
            maxActive="8" maxIdle="4" />

2. Look up that resource from within your test app:
           	Context initCtx = new InitialContext();
		Context envCtx = (Context) initCtx.lookup("java:comp/env");
		ds = (DataSource) envCtx.lookup("jdbc/testDB"); 
  
Actual results:

It throws an exception that it can't find class org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory

Expected results:

By default, it should use a factory class that is included in the standard jars, such as org.apache.commons.dbcp.BasicDataSourceFactory

Additional info:

Everything works correctly if I explicitly add factory="org.apache.commons.dbcp.BasicDataSourceFactory" to my resource definition.

Another workaround is to manually add the naming-factory-dbcp.jar from an older version of tomcat5 (... but this doesn't seem to be included in any of the current Fedora 15 rpms...)

Comment 1 Fedora Admin XMLRPC Client 2011-09-08 14:47:32 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 kielogl 2011-09-24 00:46:31 UTC
tomcat-7.0.20-3.fc15.noarch has the same problem.

tomcat-dbcp.jar is missing from tomcat-lib-7.0.20-3.fc15.noarch.

Comment 3 Fedora End Of Life 2012-08-07 14:55:50 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-01-16 22:41:17 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-14 01:13:40 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.