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 2002/03/31 09:44:42 UTC
DO NOT REPLY [Bug 7640] New: -
JDBC connection and transaction related
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7640>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7640
JDBC connection and transaction related
Summary: JDBC connection and transaction related
Product: Tomcat 4
Version: 4.0.2 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: nmurthy@etouch.net
This is regarding jdbc connection and tyrex transaction manager.
When I start the transaction and whenever i get a connection from the
datasource in the same thread from the same method, data source gives me new
connection always. If I start a transaction and calls get connection from the
same datasource with in the same thread, it should not give the new connection.
For example, if I get a connection and after I am done with it, I call close
connection. In the next method call(transaction is not over yet), If I call the
get connection then also it should give me the same physical connection as the
previous one(sothat I can do the dirty read).
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>