Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Tomcat 5.0.28, Windows XP, MySQL 4.1.7
-
MS IE 6.x
-
MySQL 4.1.7
-
Sun JDK 1.4.2_05
-
Windowx XP Pro SP2
Description
While diagnosing ROL-338, I noticed that the transaction was not getting rolled back when the exception was thrown. I am not sure what code is responsible for rollback in that situation, the HibernateStrategy.rollback() method seems to have its contents entirely commented out.
I got the following DBCP configuration from the guide. Should I be using "defaultAutoCommit=true"?
<ResourceParams name="jdbc/rollerdb">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>
jdbc:mysql://localhost:3306/roller?autoReconnect=true&
useUnicode=true&characterEncoding=utf-8&mysqlEncoding=utf8
</value>
</parameter>
<parameter><name>username</name><value>roller</value></parameter>
<parameter><name>password</name><value>roller</value></parameter>
<parameter><name>maxActive</name><value>50</value></parameter>
<parameter><name>maxIdle</name><value>5</value></parameter>
<parameter><name>removeAbandoned</name><value>true</value></parameter>
<parameter><name>maxWait</name><value>3000</value></parameter>
</ResourceParams>