This section describes known bundled Sun JDBC driver issues and associated solutions.
If an application generates more than 3000 PreparedStatement objects in one transaction, the following error may occur with DB2:
[sunm][DB2 JDBC Driver] No more available statements.Please recreate your package with a larger dynamicSections value.
Add following properties to the connection pool definition to get the driver to rebind DB2 packages with a larger dynamic sections value:
createDefaultPackage=true replacePackage=true dynamicSections=1000
See the Sun GlassFish Communications Server 1.5 Administration Guidefor details about configuring connection pools.
Related to the PrepardStatement error above, another error message that may be thrown is:
[sunm][DB2 JDBC Driver][DB2]Virtual storage or database resource is not available.
Increase the DB2 server configuration parameter APPLHEAPSZ. A good value is 4096.
Isolation level TRANSACTION_SERIALIZABLE. If your application uses isolation level TRANSACTION_SERIALIZABLE and uses one of the parameters suggested above, it might hang while obtaining a connection.
To set desired isolation level for a connection, the corresponding connection pool has to be created at that isolation level. See the Sun GlassFish Communications Server 1.5 Administration Guide for instructions.
The bundled Java DB database is not automatically restarted after a host system or Solaris zone reboot, or an Communications Server start. This is not a bug, but expected behavior for any bundled or third-party application. The problem is that the Java DB must be started before the Communications Server instance.
After rebooting the host machine or Solaris zone, be sure to start the Java DB before starting Communications Server; for example:
Refer to Administration Tools in Sun GlassFish Communications Server 1.5 Quick Start Guide in the Sun GlassFish Communications Server 1.5 Quick Start Guide for more information about asadmin command options.