test

Sun GlassFish Enterprise Server v3 Prelude Release Notes

Known Issues

This section lists the following known issues with Enterprise Server:

Registration Not Available During Red Hat Linux Installations (Issue 6058)

Description

Product Registration through installation is not supported when Open JDK is used in Red Hat Linux operating system.

For more information, see Issue report.

Workaround

    To register your installation:

  1. During installation on this environment, select the Skip Registration option.

  2. Use the Administration Console or Update Center to register your installation.

Start and Stop Menu Items Launch the Administration Console in Minimized State (Issue 5100)

Description

The property Run field for the Start and Stop Application Server menu items is specified as Normal to open the Administration Console in a maximized state, but these menu items launch the Administration Console as though the property were set to Minimized.

For more information, see Issue report.

Workaround

You must maximize the Administration Console manually.

Start Menu Items Do Not Display on Windows Vista Installations (Issue 5087)

Description

After a Windows Vista installation is completed, the Start menu program group has these problems:

For more information, see Issue report.

Workaround

You must log out and log back in to display the Start menu item program group.

The delete-domain Command Does Not Check That Domain is not Running (Issue 6196)

Description

The delete-domain command does not verify whether the domain to be removed is running. If the domain to be removed is running when the delete-domain command runs, the command should fail and should notify the user to stop the domain.

For more information, see Issue report.

Workaround

Before the delete-domain command is executed, run the stop-domain command.

Windows Installation Directory Cannot be Removed When Update Tool Notifier is Running (Issue 5789)

Description

If you try to delete the glassfishv3-prelude directory from c:\Program files when Update Tool Notifier is running, you receive this error message: Error deleting File or Folder: Cannot delete msvcp71: Access is denied.

For more information, see Issue report.

Workaround

Before you delete the installation directory, stop Update Center Notifier by closing the window for this utility.

The uninstall.sh Command Does Not Delete All Files (Issue 6032)

Description

The message WARNING: Cannot delete file filename filename is generated following execution of uninstall.sh command.

For more information, see Issue report.

Workaround

Examine the contents of your directories to verify that the files are removed. If files remain, remove them manually. If you are removing a UNIX installation, check for and delete hidden directories.

The uninstall.exe Command to Does Not Remove the Desktop Shortcut (Issue 5856)

Description

The Desktop shortcut for Enterprise Server v3 Prelude remains in the Programs menu, and an error message is written to the log file after as-install/uninstall.exe, where as-install is the Enterprise Server installation directory.

For more information, see Issue report.

Workaround

Overwrite the entry by installing Enterprise Server v3 Prelude again, or manually remove the shortcut from the list.

File Permissions on Domain /applications Directory Can Cause NullProcessException (Issue 6545)

Description

If a domain's /applications directory restricts access, or if you use directory deployment from a restricted directory, the server cannot read the files in the expanded directory. A NullProcessException error occurs during deployment.

For more information, see Issue report.

Workaround

Change the file access settings for such directories yo grant the server permission to read the directory contents.

The Windows Installation Log File is not Readable (Issue 4881)

Description

The time-stamp-install.log file cannot be read, because all lines written to the file are concatenated into a single long string.

For more information, see Issue report.

Workaround

Use a different editor, and manually open the installation log file created under the %TEMP% directory.

Running updatetool Command to Start Update Center Produces a Segmentation Violation (Issue 5514)

Description

After Update Center is installed on a Solaris 10 x86 system, using the updatetool to start Update Center fails due to a segv error.

For more information, see Issue report.

Workaround

Use the Enterprise Server Administration Console to access Update Center.

For Solaris 10 x86 operating system installations, install patch 119964-08 and patch 125212-01.

Client VM Is Not Supported on Windows AMD64 (Issue 6395)

Description

By default Enterprise Server uses client VM to achieve best startup and deployment performance. If you use a JDK that includes only server VM, you must edit the domain.xml configuration file and remove the client line.

For more information, see Issue report.

Workaround

Ensure that Client JVM is supported on your platform/operating system. If it is not supported, edit the domain.xmlfile to remove the line <jvm-options>–client<jvm-options>. In this case, JVM ergonomics will choose the appropriate kind of VM for given platform.

For more information about platform support, see Ergonomics in the 5.0 Java Virtual Machine.

Anonymous User Has Administrator Privileges After a User Is Created (Issue 6481)

Description

Anonymous user is the default user created for the default domain. If another administrative user is added to the default domain, the anonymous user definition remains available for use. Any user can use the privileges of the anonymous user to perform Enterprise Server management tasks. This access can create a security problem for some development and production deployments.

For more information, see Issue report.

Workaround

Delete the anonymous user manually.

Access to Statistics For New Virtual Servers Requires Server Restart (Issues 6238 and 6422)

Description

Monitoring statistics about newly added virtual servers are available only after the server is restarted.

For more information, see the reports for Issue 6238 and Issue 6422.

Workaround

After adding a virtual server, restart the server to view monitoring data for the virtual server.

No Support for Logging Configuration is Provided in the Administration Console or at the Command Line (Issue 6630)

Description

No Support for logging configuration is provided in the Administration Console or at the command line.

For more information, see Issue report.

Workaround

Use a plain text editor to edit the as-install/domains/domain1/config/logging.properties file. For more information, see Configuring Logging in Sun GlassFish Enterprise Server v3 Prelude Administration Guide.

Attempt to Use Administration Console to Create a Connection Pool Fails Even if the Driver Is Present (Issue 6671)

Description

In some circumstances, an attempt to use the Administration Console to create a JDBC connection pool fails even if the driver is present. When this failure occurs, the Administration Console returns a server error such as HTTP Status 500.

For more information, see Issue report.

Workaround

Repeat the attempt to create the JDBC connection pool, specifying the data-source class name explicitly. You can use either the Administration Console or the asadmin utility for this task.

The required class name depends on the resource type. For example, for the MySQL database, the required class name for each resource type is as shown in Table 1–6.

For other database drivers, consult the documentation from the database driver vendor.

Table 1–6 Resource Types and Data-Source Class Names for the Driver for the MySQL Database

Resource Type 

Data-Source Class Name 

javax.sql.ConnectionPoolDataSource

com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource

javax.sql.DataSource

com.mysql.jdbc.jdbc2.optional.MysqlDataSource

javax.sql.XADataSource

com.mysql.jdbc.jdbc2.optional.MysqlXADataSource

Example 1–1 Creating a JDBC Connection Pool by Using the asadmin Utility

This example shows how to create a JDBC connection pool that is named mysql-pool for the MySQL database. The vendor-supplied JDBC data-source class is com.mysql.jdbc.jdbc2.optional.MysqlDataSource. This class implements the javax.sql.DataSource interface.


asadmin create-jdbc-connection-pool 
--datasourceclassname=com.mysql.jdbc.jdbc2.optional.MysqlDataSource
--restype=javax.sql.DataSource
--property="user=DBUSER:password=DBPASSWORD:url=jdbc\\:mysql\\://DB_HOSTNAME\\:3306/DATABASE_NAME"
mysql-pool

ProcedureTo Specify the Data-Source Class Name Explicitly When Using Administration Console

Perform this workaround only if an attempt to use the Administration Console to create a JDBC connection pool returns a server error such as HTTP Status 500. Use this workaround with the instructions for creating a JDBC connection pool in the Administration Console online help.

  1. In the step for selecting a database vendor, do not select a vendor from the Database Vendor drop-down list.

    You perform this step on the New JDBC Connection Pool (Step 1 of 2) page.

    As a result of not selecting a vendor, the data source class name in the New JDBC Connection Pool (Step 2 of 2) page will not be filled in for you.

  2. In the step for specifying the data-source class name, type the required class name in the Datasource Classname field.

    You perform this step on the New JDBC Connection Pool (Step 2 of 2) page.

    The required class name depends on the resource type that is selected from the Resource Type drop-down list. For example, for the MySQL database, the required class name for each resource type is as shown in Table 1–6.

    For other database drivers, consult the documentation from the database driver vendor.

  3. In the step for specifying additional properties, fill in the property table with the required property names and values.

    You perform this step on the New JDBC Connection Pool (Step 2 of 2) page.

    The required property names and values depend on the data-source class.

Option Missing From Help Information for create jbdc-connection-pool (Issue 5766)

Description

The option --validateatmostonceperiod=interval is missing from the Synopsis section and the Options section of the help information for the create jbdc-connection-pool command.

The description of this option is as follows:

--validateatmostonceperiod

Specifies the time interval in seconds between successive request to validate a connection at most once. Setting this attribute to an appropriate value minimizes the number of validation requests by a connection.

The default value is 0, which specifies that the connection is never validated.

For more information, see Issue report.

Workaround

For complete information about the create jbdc-connection-pool, see the create-jdbc-connection-pool(1) man page.

In Bourne shell, all DAS, node agent, and instance processes exit when console window is closed. (6879701)

Description

If you log in as root with the Bourne shell (/bin/sh) and run asadmin commands, then log out of the console window, all the domain administration server (DAS), node agent, and instance processes are killed. This is because in the Bourne shell all child terminals inherit the TTY by default, so when the terminal is logged out, all child processes are killed too.

Workaround

Before running any asadmin commands, do the following:

  1. Log in to the server.

  2. Log in to the server.


    # exec /bin/ksh

  3. In K shell, run all the asadmin commands to bring up the DAS, node agents, and instances.

Operand is missing from the man page example for ping-connection-pool. (6881540)

The example in the man page is missing the operand at the end of the command. An error occurs if the command is entered as shown in the example. Correct example is:


asadmin> ping-connection-pool --user admin1
--passwordfile pwordfile sampleConnectionPool