Database Error Messages

This section describes error messages relating to your LiveCycle database.

    javax.resource.ResourceException error

    The javax.resource,ResourceException error message is encountered when the load on your JBoss application server is high. To avoid this issue, increase the number of database connection as follows:

    1. Open the [appserver root]\server\<profile>\deploy\adobe-ds.xml in a text editor.

    2. Increase the value of the max-pool-size property to 75.

    3. Restart the JBoss application server.

    Exceptions thrown when initializing the database multiple times

    When you initialize the LiveCycle database after it is already initialized, exceptions may be thrown indicating that the POF schema was initialized.

    This error can be safely ignored.

    MySQL “Too many connections” error

    Under heavy load conditions, MySQL may generate “Too many connections” errors. This problem can be alleviated by increasing the number of parallel connections allowed by MySQL.

    1. Go to the MySQL install directory.

    2. Locate the my.ini file and open it in an editor.

    3. Locate the max_connections parameter and set it to the required value. The default value is 100.

    4. Restart MySQL.

    J2CA0081E: Method cleanup error on SQL Server

    If you see the error “J2CA0081E: Method cleanup failed while trying to execute method cleanup...”, the stack trace appears as follows:

    "00000057 MCWrapper E J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@6d826d82 from resource SP_DS. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: This operation is not supported.. with SQL State : null SQL Code : 0"

    You must update to SQL Server 2005 JDBC driver version 1.2. Obtain this driver from the Microsoft Download Center.

    Database initialization fails on WebLogic

    You may receive the following exception while initializing the LiveCycle database on WebLogic Server:

    Servlet failed with Exception java.lang.ClassCastException: weblogic.jndi.factories.java.ReadOnlyContextWrapper at com.adobe.livecycle.bootstrap.framework.BootstrapServlet.checkDatasource(BootstrapServlet.java:216)

    To resolve this problem, modify the IDP_DS-3079-jdbc.xml file.

    Modify the IDP_DS-3079-jdbc.xml file

    1. Locate the IDP_DS-3079-jdbc.xml file in the [appserverdomain]/config/jdbc directory and open it in an editor.

    2. Locate the line <jndi-name></jndi-name> and delete it.

    3. Save and close the file, and reinitialize the database.

    Memory issues on DB2 server

    DB2 configuration page displays the following error message: 

    SQL1585N A temporary table space with sufficient page size does not exist. 
Following is the SQLCODE and SQLSTATE value specific to memory issue on DB2 server.  
sqlcode: -1584  
sqlstate: 57055  
SQL1585N A temporary table space with sufficient page size does not exist.

    For information on this error, see this IBM knowledgebase article.

    To avoid this issue, do the following:

    • Increase the system RAM. See the Preparing to Install LiveCycle ES3 guide for recommendations.

    • Provide at least 2 GB of space to each DB2 instance. If you are installing Content Services (deprecated) for use with a DB2 database, you must have a minimum of 2GB of RAM on the computer that hosts the LiveCycle database.

    // Ethnio survey code removed