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 2003/07/01 01:02:17 UTC

DO NOT REPLY [Bug 21207] New: - JDBCRealm not thread safe

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=21207>.
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=21207

JDBCRealm not thread safe

           Summary: JDBCRealm not thread safe
           Product: Tomcat 4
           Version: 4.1.24
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina:Modules
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: ronald@echteman.nl


Shouldn't there be synchronized blocks in JDBCRealm, because we use global 
PreparedStatements? This (pseudo-)code, will give two resultsets about id2. 
 
thread1.statement.setString(1, id1); 
thread2.statement.setString(1, id2); 
ResultSet rs = thread1.statement.execute(); 
ResultSet rs = thread2.statement.execute();

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org