title: TransactionManager Websphere vs Weblogic
body: <p>We have migrated an internal system from Weblogic to Websphere and it has been noticed that the weblogic implementation of the TransactionManager would flush the commands to the database immediately when commiting a nested transaction. In the other hand the implementation of websphere seems to wait the suspended transaction to finish to flush the nested ones.</p>
  
  <p>Example:</p>
  
  <pre><code>Weblogic Implementation of TransactionManager
  T1 begin
  T1 suspended T1.1 begin
               T1.1 commit *T1.1 results visible in the DB
  T1 resume
  T1 commit *T1 results visible in the DB
  
  Websphere Implementation of TransactionManager
  T1 begin
  T1 suspended T1.1 begin
               T1.1 commit 
  T1 resume
  T1 commit *T1.1 AND T1 results visible in the DB at this point.
  </code></pre>
  
  <p>Any thoughts are welcome.</p>
  
  <p>PS: as far as our investigation has gone both are supposed to be working with transaction isolation level READ_COMMITED. 
  The database is Oracle.</p>