5 Administration Issues

This chapter provides release notes on Oracle RTD administration. It contains the following topics:

• Section 5.1, "Warning Messages upon Start-up of Oracle RTD 3.0 Batch Console"

• Section 5.2, ""Failed to Save Study" Error Messages when Stopping Oracle RTD Server in OC4J / Oracle Application Server"

• Section 5.3, "Must Restart OC4J When Database Server Restarts"

5.1 Warning Messages upon Start-up of Oracle RTD 3.0 Batch Console

This issue applies to Version 3.0 and Version 3.0.0.1.

When starting the Batch Console, two log4j warnings appear:

log4j: WARN No appenders could be found for logger(org.apache.axis.i18n.ProjectResourceBundle). 
log4j: WARN Please initialize the log4j system properly.

These warnings can be ignored, they do not hamper functionality.

5.2 "Failed to Save Study" Error Messages when Stopping Oracle RTD Server in OC4J / Oracle Application Server

This issue applies to Version 3.0 and Version 3.0.0.1.

When running RTD 3.0 in OC4J/Oracle Application Servers, an error in the way the connection pool is managed may cause a "Failed to save study" error message to appear in the RTD server log upon shutdown of the Oracle RTD application. For example:

2009-03-02 19:57:18,187 ERROR [LearningDispatcher] Failed to save study "CrossSell".
com.sigmadynamics.server.DataServices.DatabaseProvider.DatabaseProviderException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.

When this error occurs, some Oracle RTD model data may not have been committed to the database. Data is not lost, however, as the learning records are still saved in the Oracle RTD database and will be processed the next time the Oracle RTD server starts up. Learning records that need to be removed will be removed as appropriate at the end of each model persist period (default is 60 minutes).

Users can safely ignore this error message for routine restarts of the Oracle RTD application within OC4J/Oracle Application Server.

5.3 Must Restart OC4J When Database Server Restarts

This issue applies to Version 3.0 and Version 3.0.0.1.

When Oracle RTD is running on standalone OC4J, if the Oracle RTD Database (or any database that Oracle RTD is accessing) goes down for any reason, you must restart OC4J.

This problem occurs because standalone OC4J does not support refreshing stale database connections after a database restart.