Depending on your application server, you may need to increase the transaction timeout and datasource connection pool settings in order for indexing to run successfully.

Increasing the Transaction Timeout

If indexing is not successful, it may be related to the transaction timeout setting in your application server. Oracle ATG recommends setting a transaction timeout of 300 seconds or greater. 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. 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 ATG Installation and Configuration Guide.

Increasing the Data Source Connection Pool

Oracle ATG recommends setting the data source connection pool maximum capacity to 30 or greater for all of your data sources. For information on setting the data source connection pool maximum capacity, refer to your application server’s documentation.


Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Legal Notices