Bug 28411 - DBTags caching connection items to database
Summary: DBTags caching connection items to database
Status: RESOLVED WONTFIX
Alias: None
Product: Taglibs
Classification: Unclassified
Component: DBTags Taglib (show other bugs)
Version: 1.0
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-15 13:45 UTC by Eric Medlock
Modified: 2005-09-24 09:37 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Medlock 2004-04-15 13:45:04 UTC
The first time a page with DBtags is used after a compile it caches the
connection object and all subsequent calls to that page use that connection
(close seems to have no effect). This does not seem to happen under Tomcat 3.x
but does happen under Tomcat 5.01.

Our system uses dynamic database connections (ie: depending on which client our
user belongs to their data will come from a particular database, all our
databases have the same scheme but the data is different based on client). Our
issue is that once the page has compiled/used once, all subsequent users get the
data from the first users database. Once work aroundis using absolute references
in our from clause (ie: database.tablename).
Comment 1 Eric Medlock 2004-04-15 14:14:10 UTC
Disabling tag pooling seems to correct this issue.
Comment 2 Rahul Akolkar 2005-09-24 17:37:15 UTC
Thank you for also getting back to us on what worked for this issue.

The DBTags taglib has been deprecated, we do not expect any development around 
it in the near future. Please switch to the using JSTL, if possible.