title: WebSphere insert/update statements with SQL-SERVER hangs with REQUIRES_NEW propagation
body: <p>We are facing an issue in our spring batch application when we are deploying the application on WebSphere.</p>
  
  <p>Example: One class contains parent() method and Second class contains child() method, where child method requires a new transaction. After execution of the methods when transaction is committed the commit routine hangs and nothing happens further.</p>
  
  <pre><code>@Transactional //using current transaction
  public void parent(){
      child();
  }
  
  @Transactional(propagation=REQUIRES_NEW) //creates new transaction
  public void child(){
  //Database save statements including update, insert and deletes
  }
  </code></pre>
  
  <p>This issue only persists in WebSphere and code works fine on our local machine where we are using tomcat as web container.</p>
  
  <p>WebSphere logs/stacktrace shows that the WebSphere prepared statement keeps on waiting for the response from the database. At the same time update and inserts are locked out on the affected tables i.e. if we run an insert or update query manually on the affected table the query doesn't execute.</p>
  
  <p>We are using Spring JPA for data persistence and Spring’s JpaTransactionManager for transaction management and MSSQLServer database.</p>
  
  <p>Is it that WebSphere does not support creating new transaction from existing transaction?</p>