JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.0.1 Release Notes

Document Information

1.  Oracle GlassFish Server 3.0.1 Release Notes

Revision History

What's New in the Oracle GlassFish Server 3.0.1 Release?

Support for Java EE Profiles

Modular Design

Support for Extending GlassFish Server

Update Tool Integration

Support for Scripting Languages

Web Services Interoperability Technologies (WSIT) Support

Enhancements to the appclient Utility

EclipseLink Integration

Move of HTTP Service Settings to Network Service

Changes Related to Administrator Authentication

Changes Related to the asadmin Utility

Changes Related to File Layout

Changes Related to Ant Tasks and the asant Utility

Changes Related to domain.xml Validation

Changes Related to Applications

force Option

Applications and Generated Directory Layout

domain.xml application Element

Stricter JAR Visibility Rules

Application Client deploy --retrieve and get-client-stubs Commands

Hardware and Software Requirements

Supported Platforms

System Virtualization Support

Required Disk Space

Required Free Ports

Important Patch Information

Required JDK Version

Path Settings for the JDK Software

Supported JDBC Drivers and Databases

Supported Browsers

mod_jk Support

Known Issues

Expired Root CA for CN=GTE CyberTrust Root 5, OU=GTE CyberTrust Solutions, Inc. (17405426)

Description

Solution

To Delete the GTE CyberTrust Root 5 Certificate From the Truststore

[OWSM] Interop Metro-WLS:NPE WSSECURTIYTOKEN NULL for WSSE:SECURITYTOKENREFERENCE (Issue 9716247)

Description

Workaround

[JDK_Issue] SSLHandshakeException when using JDK1.6.0_20 (Issue 12041)

Description

Workaround

[JDK_Issue] Performance degradation caused by invoking setSoLinger or setReuseAddress (Issue 7109)

Description

Workaround

[JDK_Issue] IO exception: invalid argument during longevity test (Issue 7529)

Description

Workaround

[JDK_Issue] Richaccess: java.io.IOException: Invalid argument from doSelect (Issue 8573)

Description

Workaround

GlassFish Server 3.0.1 on HP-UX when using jdk 1.6.0.07 (Issue 12206)

Description

Workaround

GF b22 failed to startup with JRockit jrmc-4.0.0-1.6.0 (Issue 12265)

Description

Workaround

File permissions on domain /applications directory can cause NullProcessException (Issue 6545)

Description

Workaround

Windows installation log file is not readable (Issue 4881)

Description

Workaround

Uninstallation fails on Windows 7 because of missing JDK error (Issue 12093)

Description

Workaround

Access to statistics for new virtual servers requires server restart (Issues 6238 and 6422)

Description

Workaround

[Open Installer] Option -l to relocate log files ignored on Windows (Issue 10693)

Description

Workaround

Issues occur with ZIP distribution if UAC enabled on Windows Vista (Issue 10755)

Description

Workaround

Null pointer exception thrown from com.sun.xml.wss.NonceManager.getInstance (Issue 11138)

Description

Workaround

[Open Installer] Start menus not displayed and then empty on Windows Vista and Windows 2008 (Issue 5087)

Description

Workaround

When specj application is deployed, asadmin get --monitor=true "server.*" results in I/O error (Issue 11163)

Description

Workaround

Standalone Update Tool fails with segmentation fault on Solaris (Issue 11222)

Description

Workaround

Ruby applications deployed on context root don't work with Admin Console (Issue 10854)

Description

Workaround

Java EE 6 Managed Bean support not available in app clients launched using Java Web Start (Issue 11257)

Description

Workaround

Warning messages when invoking appclient script on Mac OS X with Apple Java implementation (Issue 8644)

Description

Workaround

Launching an app client can give ClassNotFound error for the client's main class (Issue 11181)

Description

Workaround

Change to log file location requires server restart to take effect (Issue 11142)

Description

Workaround

Unable to open installation log files using links on the Summary screen on Linux and Mac OS (Issue 6621)

Description

Workaround

updatetool command does not work if you reinstall into the same install directory on Windows (Issue 8233)

Description

Workaround

[Update Center] Non-user directory access fails (Update Center Issue 1583)

Description

Workaround.

Inline help and CLI man page list incorrect servlet version 2.4 in X-Powered-By (Issue 11011)

Description

Workaround

[Embedded] Deployment of application containing activation-1.1.jar fails when using uber-jar (Issue 11149)

Description

Workaround

create-service fails to create service without AS_ADMIN_USER in passwordfile on Solaris (Issue 11119)

Description

Workaround

[Monitoring] Extra monitoring view for connector-connection-pools not available (Issue 11256)

Description

Workaround

[EclipseLink] Issues with ElementCollections of embeddables (EclipseLink Issue 296606)

Description

Workaround

Virtual server started twice (Issue 11195)

Description

Workaround

Problems debugging JPA (Issue 11274)

Description

Workaround

EJB interop for remote EJBs broken when target EJB is on the same host (Issue 11152)

Description

Workaround

Cannot send JMS messages between systems (Issue 11254)

Description

Workaround

Windows system menu is empty (Issue 11239)

Description

Workaround

Embedded ACC overly strict on current thread context class loader (Issue 11427)

Description

Workaround

EJB Timer Service config issue for MySQL (Issue 11428)

Description

Workaround

deploy subcommand fails against secure server (Issue 11439)

Description

Workaround

Expired certificate in GlassFish Server truststore (Issue 6852796)

Description

Workaround

GlassFish V3 should allow multiple applications with the same context root (7002834)

Description

Solution

Install Directory of application server not known. Specify either the installDir attribute or the asinstall.dir property (14837)

Description

Solution

Disabling Trace Request on GlassFish 3.0.1 (12650799)

Description

Solution

Restrictions

Unsupported Options in asadmin Commands

No Support for Client VM on Windows AMD64

GlassFish Server Documentation Set

Features Available Only in the Full Platform Profile

Java EE 6 Standards

Java EE 6 SDK

How to Report Problems and Provide Feedback

Additional Resources

Third-Party Web Site References

Accessibility Features

What’s New in the Oracle GlassFish Server 3.0.1 Release?

This section describes the following new features in GlassFish Server 3.0.1:

Support for Java EE Profiles

Java EE 6 introduces the concept of profiles. A profile is a collection of Java EE technologies and APIs that address specific developer communities and application types.

The following profiles are implemented through the distributions of Oracle GlassFish Server 3.0.1:

Java EE 6 SDK distributions are available from the Java EE 6 SDK downloads page.

For the list of APIs in each profile, see Java EE 6 Standards.

Modular Design

In GlassFish Server version 3.0.1, the GlassFish Server code was split into modules to provide flexibility and improved runtime performance. The modular architecture is implemented on top of OSGi Alliance standards and enables reusability of GlassFish Server 3.0.1 modules as well as other modules.

This design change allows use of only those modules that you require for the applications deployed. Runtime is used only for applications that use it, and upgrades can be implemented without a complete system reinstallation. This change minimizes startup times, memory consumption, and disk space requirements.

The modular design provides the ability to do the following:

Support for Extending GlassFish Server

A new Oracle GlassFish Server 3.0.1 container System Provider Interface (SPI) defines interfaces that a container developer must implement so that GlassFish Server can call into it at appropriate times. This change enables GlassFish Server users to customize GlassFish Server by adding administrative commands and graphical add-on components.

GlassFish Server also provides streamlined support of new module types, such as Ruby on Rails.

Update Tool Integration

Update Tool is now embedded in the Oracle GlassFish Server 3.0.1 Administration Console. This tool facilitates managing add-on components and related applications that are available for extending GlassFish Server 3.0.1 functions.

The Administration Console provides access to the Update Tool page through the navigation tree. The Update Tool page provides tabs to display the following:

Integration of Update Tool in the Administration Console enables administrators to easily extend GlassFish Server and view available updates. A standalone version of Update Tool is also available using the updatetool command. For more information about Update Tool, see Update Tool in Oracle GlassFish Server 3.0.1 Administration Guide.


Note - You cannot perform updates to existing components using the Update Tool interface directly from within the GlassFish Server Administration Console. To update or remove installed components, you must use the standalone command-line version or the pkg command.


Update Tool is developed through the Update Center project. The Administration Console uses the Update Center 2.3 API to display a list of available components, versions, and dates. For information about Update Center 2.3, see the Release Notes for Update Center 2.3 .


Note - Update Tool differs from the older Upgrade Tool, which is used to migrate the configuration and deployed applications from an earlier version of GlassFish Server to the current version. For more information about Upgrade Tool, see the Oracle GlassFish Server 3.0.1 Upgrade Guide.


Support for Scripting Languages

To facilitate rapid application development and deployment, Oracle GlassFish Server 3.0.1 supports a variety of scripting languages. The use of scripting languages enables GlassFish Server to be applied beyond developments that are centered on Java technology. Supported scripting languages include the following:

The components for integrating scripting languages with GlassFish Server are available through Update Tool.

Note that scripting languages are not covered under an Oracle GlassFish Server license and support offering.

Web Services Interoperability Technologies (WSIT) Support

Oracle is working closely with Microsoft to ensure interoperability of Web services enterprise technologies such as message optimization, reliable messaging, and security. WSIT is a product of this joint effort. WSIT is part of Metro 2.0, a high-performance, extensible web service stack that offers interoperability with Microsoft .NET 3.5. Metro 2.0 is included in the full distribution of GlassFish Server 3.0.1.

WSIT is an implementation of a number of open web services specifications to support enterprise features. In addition to message optimization, reliable messaging, and security, WSIT includes a bootstrapping and configuration technology. Starting with the core XML support currently built into the Java platform, WSIT uses or extends existing features and adds new support for interoperable web services, including:

Enhancements to the appclient Utility

The appclient utility has been enhanced in GlassFish Server 3.0.1, as follows:

For more information, see the appclient(1M) man page.

EclipseLink Integration

Oracle GlassFish Server 3.0.1 uses EclipseLink as its Java Persistence API (JPA) 2.0 provider. EclipseLink is also the Reference Implementation for JSR 317. For the most recent information regarding EclipseLink functionality, see the EclipseLink 2.0 Release Notes.

Move of HTTP Service Settings to Network Service

In Oracle GlassFish Server 3.0.1, most HTTP Service settings have been moved into the new Network Service configuration. For more information, see the Oracle GlassFish Server 3.0.1 Upgrade Guide.

Changes Related to Administrator Authentication

In Oracle GlassFish Server 3.0.1, you are not prompted for administration credentials by default. This is a change from previous releases.

If you install GlassFish Server using the ZIP file, you will not be prompted for administration credentials when you launch the Administration Console or use the asadmin utility and remote subcommands to perform administrative tasks.

If you install GlassFish Server 3.0.1 using the self-extracting file and graphical installer, you will not be prompted for administration credentials unless you specified a user name and password on the Administration Settings page during installation. If you accepted the defaults on that page, the default administrative user is admin and the password field is left empty.

If there is only one admin user with no password, unauthenticated logins are permitted. For more information about administrator authentication, see To Log In to a Domain in Oracle GlassFish Server 3.0.1 Administration Guide.

Administrator authentication requirements can be changed after GlassFish Server has been installed. For information about using the Administration Console to perform this and related tasks, see the Administration Console online help. For information about using the command-line interface, see Administering Passwords in Oracle GlassFish Server 3.0.1 Administration Guide.

Changes Related to the asadmin Utility

The behavior of the asadmin utility has been modified to emphasize the distinction between options for the asadmin utility itself and options for its subcommands. Options for the asadmin utility itself are now allowed before the subcommand. However, for compatibility with other releases, options for the asadmin utility itself are still allowed after the subcommand, but such syntax is deprecated.

For more information, see Using the asadmin Utility in Oracle GlassFish Server 3.0.1 Administration Guide.

Changes Related to File Layout

Oracle GlassFish Server 3.0.1 includes the following file layout changes from previous releases:

Changes Related to Ant Tasks and the asant Utility

Oracle GlassFish Server 3.0.1 provides server-specific Ant tasks, for which Ant must be installed. The asant utility is not included in the release.

GlassFish Server is compatible with Apache Ant versions 1.6.5 or greater. If Ant is not installed, you can install it using Update Tool.

For more information about Update Tool, see Update Tool in Oracle GlassFish Server 3.0.1 Administration Guide. For more information about Ant tasks, see Chapter 3, Using Ant with GlassFish Server, in Oracle GlassFish Server 3.0.1 Application Development Guide.

Changes Related to domain.xml Validation

Because Oracle GlassFish Server 3.0.1 is modular and extensible, the domain.xml file cannot be validated against a static DTD file. Instead, the domain.xml file is validated against @Configured annotations in the source code. For more information about the structure of the domain.xml file, see the Oracle GlassFish Server 3.0.1 Domain File Format Reference.

Changes Related to Applications

Application-related differences exist between GlassFish Server 3.0.1 and GlassFish Server v2. This section describes some of those differences.

force Option

The default value of the force option for deployment is false in GlassFish Server 3.0.1. This default value was true in GlassFish Server v2. In GlassFish Server 3.0.1 you must explicitly set the option to true for redeployment. This option is not automatically set during the upgrade process. The purpose of this change is to avoid accidentally overwriting the contents of an existing application. This applies to both the Administration Console and command-line utility.

The asadmin redeploy command is also new in GlassFish Server 3.0.1 and offers an equivalent to --force=true. The force option is only applicable to the deploy command (command-line interface) and the deploy screen (console), not to the redeploy command and redeploy screen.

Applications and Generated Directory Layout

GlassFish Server v2 contained two subdirectories for the applications repository: applications/j2ee-apps and applications/j2ee-modules. Those subdirectories no longer exist in GlassFish Server 3.0.1 (there is no j2ee-apps or j2ee-modules level). Deployment of a standalone module such as foo.war, which was previously located in applications/j2ee-modules/foo in GlassFish Server v2, is now located in applications/foo in GlassFish Server 3.0.1. Enterprise applications and standalone modules essentially share the same name space, so the intermediate directory layer was not necessary.

domain.xml application Element

Previous elements such as web-module, ejb-module, and so on are deprecated in GlassFish Server 3.0.1 and replaced with the new application element. For more information about the application element, see application in Oracle GlassFish Server 3.0.1 Domain File Format Reference.

During an upgrade, GlassFish Server v2 applications are redeployed at the new applications/ location with the new application element in domain.xml. Any new applications deployed on GlassFish Server 3.0.1 will be deployed with the new directory structure and element.

Stricter JAR Visibility Rules

Java EE 6 imposes stricter JAR visibility rules than did Java EE 5. As a result, some older applications might fail.

The Java EE 6 specification imposes strict rules about which JAR files are visible from an enterprise archive (EAR) file. Refer to section EE.8.3.3; specifically, application client modules should not have access to any EJB JAR file unless the application client JAR file's manifest Class-Path refers to the EJB JAR file(s) explicitly.

This is a change from GlassFish Server v2, in which application clients automatically had access to all EJB JAR files in the EAR file and all JAR files at the top level of the EAR file. To comply with the stricter specification language, GlassFish Server 3.0.1 cannot automatically provide application clients with access to these JAR files.

This new, stricter behavior imposed by Java EE 6 can be addressed as follows:

This change in behavior is also discussed in Chapter 1, GlassFish Server Compatibility Issues, in Oracle GlassFish Server 3.0.1 Upgrade Guide.

Application Client deploy --retrieve and get-client-stubs Commands

In Oracle GlassFish Server 3.0.1, running the deploy --retrieve and get-client-stubs commands no longer downloads just one JAR file to your local directory as in GlassFish Server v2. While localdir/myAppClient.jar is still created in GlassFish Server 3.0.1 and can be used as a target in the appclient command, another directory is also created, localdir/myAppClient, which in turn might contain other files.

If you typically copy the single GlassFish Server v2 downloaded JAR file as a way to move the application client components from one place to another, that will not work in GlassFish Server 3.0.1. The supported method is to use the asadmin get-client-stubs command for that purpose. For more information about the command, see get-client-stubs(1).

If you still choose to copy, however, you must copy not only the localdir/myAppClient.jar file (as in GlassFish Server v2), but also all of the contents of the localdir/myAppClient directory.