JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Upgrade Guide
search filter icon
search icon

Document Information


1.  GlassFish Server Upgrade Compatibility Issues

Binary-Compatible Releases For GlassFish Server 3.1

New Default Installation Directory

Changes to Group Management Service Settings

Application Client Interoperability

Node Agent Support

HADB and hadbm Command Support

Command Line Interface: The asadmin Command

Deprecated asadmin Subcommands

Deprecated, Unsupported, and Obsolete Options

Applications That Use Java DB

Applications That Use Persistence

HTTP Service to Network Service Changes

Changes to Dotted Names

Changes to asadmin Commands

Remapping of HTTP Service Attributes and Properties

New Network Service Elements and Attributes

NSS Cryptographic Token Support

2.  Upgrading an Installation of Application Server or GlassFish Server


Applications That Use Java DB

The directory location of Java DB in GlassFish Server 3.1 has changed from its location in previous installations. Suppose that you have deployed applications that use Java DB databases in your previous server installation, and you upgrade your existing installation to GlassFish Server 3.1. If you run the asadmin start-database command and successfully start Java DB, you could run into problems while trying to run applications that were deployed on your previous server installation.

To solve this problem, you can copy the databases directory from your previous installation to as-install/databases. Make sure the database is not running when you do this.

Alternatively, you can perform these steps:

  1. Use the asadmin start-database command with the --dbhome option pointing to the databases directory in the older version of Java DB. For example:

    asadmin start-database --dbhome c:\glassfish\databases
  2. After upgrade, start GlassFish Server 3.1.