All supported application servers time out long-running transactions by marking the active transaction as rolled back (essentially, by calling setRollbackOnly on the transaction), which can result in problems when indexing. If your indexing process fails, try increasing the transaction timeout setting. Oracle recommends setting a transaction timeout of 300 seconds or greater. For details on changing your transaction timeout, see Setting the Transaction Timeout on WebLogic, Setting the Transaction Timeout on JBoss, or Setting the Transaction Timeout on WebSphere in the Platform Installation and Configuration Guide.
