Java DB is not started after machine reboot or Application Server start (6515124)

Description

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.

Solution

After rebooting the host machine or Solaris zone, be sure to start the Java DB before starting Communications Server; for example:

/opt/SUNWappserver/appserver/bin/asadmin start-database

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.