Author: paristote Date: 2011-07-08 00:01:54 -0400 (Fri, 08 Jul 2011) New Revision: 4613 Added: jcr/branches/1.12.x/patch/1.12.10-GA/JCR-1639/readme.txt Modified: jcr/branches/1.12.x/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/storage/jdbc/JDBCStorageConnection.java Log: JCR-1639 What is the problem to fix? * Delay in replication of Nodes data in JBoss EPP How is the problem fixed? * Need to rollback JDBC connection before closing. Modified: jcr/branches/1.12.x/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/storage/jdbc/JDBCStorageConnection.java =================================================================== --- jcr/branches/1.12.x/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/storage/jdbc/JDBCStorageConnection.java 2011-07-07 12:49:29 UTC (rev 4612) +++ jcr/branches/1.12.x/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/storage/jdbc/JDBCStorageConnection.java 2011-07-08 04:01:54 UTC (rev 4613) @@ -373,12 +373,17 @@ { closeStatements(); - // If READ-ONLY status back it to READ-WRITE (we assume it was original state) + // If READ-ONLY status back it to READ-WRITE (we assume it was original state) if (readOnly) { dbConnection.setReadOnly(true); } + if (dbConnection.getTransactionIsolation() > Connection.TRANSACTION_READ_COMMITTED) + { + dbConnection.rollback(); + } + dbConnection.close(); } catch (SQLException e) Added: jcr/branches/1.12.x/patch/1.12.10-GA/JCR-1639/readme.txt =================================================================== --- jcr/branches/1.12.x/patch/1.12.10-GA/JCR-1639/readme.txt (rev 0) +++ jcr/branches/1.12.x/patch/1.12.10-GA/JCR-1639/readme.txt 2011-07-08 04:01:54 UTC (rev 4613) @@ -0,0 +1,72 @@ +Summary + + Status: Delay in replication of Nodes data in JBoss EPP + CCP Issue: CCP-984, Product Jira Issue: JCR-1639. + Complexity: High + +The Proposal +Problem description + +What is the problem to fix? + + Delay in replication of Nodes data in JBoss EPP + +Fix description + +How is the problem fixed? + + * Need to rollback JDBC connection before closing. + +Patch information: +JCR-1639.patch + +Tests to perform + +Reproduction test + + A folder was created with the name 00480017, and a document inside it named 00480017-test1 + After few seconds, the folder just disappeared. We tried to access it using its full path /00480017 but, it wasn't there anymore. Message that the folder doesn't exist or something like that. + Then, we tried to create a new folder with the name name of the previous, then we got a "Can not save. This node doesn't allow 2 nodes with the same name" message. + After ~15 minutes, the folder appeared again. + +Tests performed at DevLevel + * Functional testing, manual testing in customer env. + +Tests performed at QA/Support Level +* + +Documentation changes + +Documentation changes: + * No + +Configuration changes + +Configuration changes: + * No + +Will previous configuration continue to work? + * Yes + +Risks and impacts + +Can this bug fix have any side effects on current client projects? + + No + +Is there a performance risk/cost? + * it is possible a bit perf decreasion on MySQL with InnoDB engine. See QA reports (two last columns) http://tests.exoplatform.org/JCR/1.12.10-GA/rev.4553/daily-performance-te...; + +Validation (PM/Support/QA) + +PM Comment + + Patch approved by the PL + +Support Comment + + Support review: Patch validated + +QA Feedbacks +* +