InnerhalbNach weiteren Dokumenten suchenSupport-Ressourcen |  Dieses Buch im PDF-Format herunterladen (674 KB)
Chapter 1 Sun GlassFish Enterprise Server v3 Preview Release NotesThe Sun GlassFishTM Enterprise Server v3 Preview Release Notes contain important information for the Enterprise Server v3 Preview release, including new Enterprise Server features and known issues with workarounds, if available. Check this document prior to installing and setting up your software, and read this document before you begin using Sun GlassFish Enterprise Server v3 Preview. Consult this document periodically to view the most up-to-date documentation. Revision HistoryThis section provides a record of changes in Sun GlassFish Enterprise Server v3 Preview Release Notes. Table 1–1 Revision History
What’s New in the Sun GlassFish Enterprise Server v3 Preview Release?Sun GlassFish Enterprise Server v3 Preview provides a server for the development and deployment of Java Platform, Enterprise Edition (JavaTM EE platform) applications and web technologies based on Java technology. The following new features of Enterprise Server are described here: Support for Java EE ProfilesJava 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 Sun GlassFish Enterprise Server v3 Preview:
The distributions that implement these profiles are available from the Java EE 6 SDK Preview download page. Note – These profiles are not yet final. The implementations for Sun GlassFish Enterprise Server v3 Preview represent work-in-progress versions of some but not all Java EE 6 standards, based on published drafts. Modular DesignSun GlassFish Enterprise Server v3 Preview has split the GlassFish code into modules to provide flexibility and improved runtime performance. The modular architecture is implemented on top of OSGi Alliance standards and enables reusability of Enterprise Server v3 Preview modules as well as other modules. This design change allows you to download and install only the modules that you require for the applications that you are deploying. 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 Enterprise ServerA new Sun GlassFish Enterprise Server v3 Preview container system provider interface (SPI) defines interfaces that the container developer must implement so that Enterprise Server can call into it at appropriate times. This change enables Enterprise Server users to create custom application servers by adding administrative commands and graphical add-on components. Enterprise Server also provides streamlined support of new module types, such as Ruby on Rails. Update Tool IntegrationUpdate Tool is now embedded in the Sun GlassFish Enterprise Server v3 Preview Administration Console. This tool provides automated updates, and facilitates managing add-on components and related applications that are available for extending Enterprise Server v3 Preview 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 Administration Console enables administrators to extend and update Enterprise Server without the need to launch a standalone version of Update Tool by using the updatetool command. The Update Tool is developed through the Update Center project. The Administration Console uses the Update Center 2.0 API to display a list of available components, versions and dates. For information about Update Center 2.0, see the Release Notes for Update Center 2.0 . Support for Scripting LanguagesTo facilitate rapid application development and deployment, Sun GlassFish Enterprise Server v3 Preview supports a variety of scripting languages. The use of scripting languages enables Enterprise Server to be applied beyond developments that are centered on Java technology. Supported scripting languages include the following:
Support for these scripting languages is provided by components that are available through Update Tool. Enhancements to the appclient UtilityIn this release, the appclient utility is enhances as follows:
For more information, see the appclient(1M) man page. Move of HTTP Service Settings to Network ServiceIn Sun GlassFish Enterprise Server v3 Preview, most HTTP Service settings have been moved into the new Network Service configuration. For more information, see Appendix A, HTTP Service to Network Service Changes. Hardware and Software RequirementsThis section lists the requirements that must be met before installing the Sun GlassFish Enterprise Server v3 Preview product. Supported PlatformsSun GlassFish Enterprise Server v3 Preview requires a minimum of 200 Mbytes of free disk space to install, and 100 Mbytes of free memory to run. This following table lists supported operating systems and provides minimum memory, recommended memory, minimum disk space, recommended disk space, and Java virtual machine for each. Table 1–2 Supported Operating Systems
On UNIX® platforms, you can check your operating system version by using the uname command. Disk space can be checked by using the df command. Note – Use the NTFS file system rather than FAT or FAT32 when running the Enterprise Server on any Microsoft Windows platform. System Virtualization SupportSystem virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see System Virtualization Support in Sun Java System Products. Required Disk SpaceYour temporary directory must have enough free space for the installation of the following software:
Required Free PortsYou must have seven unused ports available. The installation program automatically detects ports that are in use and suggests currently unused ports for the default settings. The initial default port assignments are listed in the following table. If these default port numbers are in use, the installation program assigns a randomly selected port number from the dynamic port range. The selected port number might not be the next available port number. Table 1–3 Default Port Assignments for Enterprise Server v3 Preview
Important Patch InformationSolaris Patch RequirementsIf you are using the Solaris 10 operating system, you must apply the appropriate patch for your platform as listed in the following table.
You must also ensure that the Sun recommended patch cluster is applied. These patches and the patch cluster are available from the SunSolveSM program web site.
Required JDK VersionInstallation of Sun GlassFish Enterprise Server v3 Preview requires JDKTM release 6. The minimum (and certified) version of the JDK software that is required for Enterprise Server depends on the operating system:
Path Settings for the JDK SoftwareThe following binary files that are used with Enterprise Server must come from the JDK software, not the Java Runtime Environment (JRETM) software:
To meet this requirement, ensure that the bin directory of the JDK software precedes the bin directory of the JRE software in your path. Supported JDBC Drivers and DatabasesThe following table lists the databases and drivers that are supported in this release. All supported configurations of the Sun GlassFish Enterprise Server v3 Preview must contain at least one combination of database and driver from this table, such as the Java DB and driver. In addition, the Enterprise Server is designed to support connectivity through Java DataBase Connectivity (JDBCTM) technology to any additional database management system (DBMS) with a corresponding driver that supports the JDBC API (JDBC driver). Table 1–4 Supported JDBC Drivers and Databases
Supported BrowsersThe following table lists supported browsers and versions. Table 1–5 Supported Web Browsers
Known IssuesThis section lists the following known issues with Enterprise Server:
[JDK ISSUE] Performance degradation caused by invoking setSoLinger or setReuseAddress (Issue 7109)DescriptionWhen the setSoLinger method or the setReuseAddess method is invoked, performance is degraded and the following exception is thrown:
This issue is caused by an issue with the JDK software. This issue is resolved in JDK version 7. For more information, see Issue report. WorkaroundNone. [JDK_ISSUE] Warnings in server.log during clicks in the Administration Console GUI on deployed samples (Issue 7206)DescriptionThe following sequence of operations causes warnings to be written to the server.log file:
The warnings are as follows: [#|2009-02-19T17:49:07.395-0800|WARNING|glassfish| javax.enterprise.system.core|_ThreadID=26;_ThreadName=Thread-2;|setSoLinger exception java.net.SocketException: Invalid argument ... [#|2009-02-19T17:49:07.396-0800|WARNING|glassfish| javax.enterprise.system.core|_ThreadID=26;_ThreadName=Thread-2;|setReuseAddress exception java.net.SocketException: Invalid argument ... This issue is caused by an issue with the JDK software. This issue is resolved in JDK version 7. For more information, see Issue report. WorkaroundNone. [JDK ISSUE] Null pointer exception on server restart (Issue 8299)DescriptionRestarting Enterprise Server sometimes causes a null pointer exception to be thrown.
This issue is caused by an issue with the JDK software. This issue is resolved in JDK version 7. For more information, see Issue report. WorkaroundNone. Start and Stop Menu Items Launch the Administration Console in Minimized State (Issue 5100)DescriptionThe 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. WorkaroundYou must maximize the Administration Console manually. The delete-domain Command Does Not Check That Domain is not Running (Issue 6196)DescriptionThe 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. WorkaroundBefore the delete-domain command is executed, run the stop-domain command. The uninstall.sh Command Does Not Delete All Files (Issue 6032)DescriptionThe message WARNING: Cannot delete file filename filename is generated following execution of uninstall.sh command. For more information, see Issue report. WorkaroundExamine 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)DescriptionThe Desktop shortcut for Enterprise Server v3 Preview 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. WorkaroundOverwrite the entry by installing Enterprise Server v3 Preview again, or manually remove the shortcut from the list. File Permissions on Domain /applications Directory Can Cause NullProcessException (Issue 6545)DescriptionIf 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. WorkaroundChange 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)DescriptionThe 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. WorkaroundUse a different editor, and manually open the installation log file created under the %TEMP% directory. Anonymous User Has Administrator Privileges After a User Is Created (Issue 6481)DescriptionAnonymous 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. WorkaroundDelete the anonymous user manually. Access to Statistics For New Virtual Servers Requires Server Restart (Issues 6238 and 6422)DescriptionMonitoring 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. WorkaroundAfter adding a virtual server, restart the server to view monitoring data for the virtual server. Intermittent: Deployment by Using Ant Fails With Invalid chunk header Error (Issue 8408)DescriptionAn attempt to deploy an application by using the all Ant task with Ant 1.7.1 might fail with a remote failure: Invalid chunk header error. For more information, see Issue report. WorkaroundRepeat the attempt to deploy the application. Intermittent: The JRuby Gem Cannot Be Downloaded on the MacOS Platform (Issue 8423)DescriptionAn attempt to download the JRuby gem on the MacOS platform might fail with a resource temporarily unavailable error. This issue is intermittent and occurs when the contrib repository is inaccessible. For more information, see Issue report. WorkaroundTry the download again later. Because this issue is intermittent, repeating the download later might resolve the issue. Grizzly Framework Closure of Input/Output Queue Has an Infinite Loop (Issue 8446 and Grizzly Issue 626)DescriptionThe executePendingIO method of the TCPSelector class contains a logic error. Under heavy loads, this logic error can cause the thread that is processing HTTP connections to go into an infinite loop. This condition can cause increased CPU usage and a memory leak with corresponding OutOfMemoryException exceptions. For more information, see Issue 8446 and Grizzly Issue 626. WorkaroundDownload version 1.9.15b of the Grizzly Framework to the as-install/modules directory. Deploying a WAR File With WEB-INF/ejb-jar.xml and WEB-INF/lib/ejb.jar Throws a NullPointerException Exception (No Issue Number)DescriptionAn attempt to deploy a WAR file might fail, causing a NullPointerException exception to be thrown. The failure occurs if some EJB components reference annotations such as @EJB, @Stateless, @Stateful in classes that are packaged in JAR files in the WEB-INF/lib directory. WorkaroundPackage the JAR files that contain the classes in the WEB-INF/classes directory. RestrictionsThis section describes the following Sun GlassFish v3 Preview Enterprise Server restrictions: UpgradesAn upgrade scenario from an earlier installation into Enterprise Server v3 Preview is not supported. The command-line interface and configuration are compatible. application-root Attribute in the domain.xml FileYou should not modify the default setting in the domain.xml file for the application-root attribute. The domain element's application-root attribute In the domain.xml file is intended to specify where the server will expand application archives when the user deploys them. Currently, not all places in Enterprise Server v3 Preview that should use this attribute do so. Some uses of the attribute assume that applications are to be expanded in ${com.sun.aas.instanceRoot}/applications. Unsupported Options in asadmin CommandsThe help for asadmin commands describes some options that are not supported by Sun GlassFish Enterprise Server v3 Preview. For example:
If you specify an unsupported option, a syntax error does not occur. Instead, the command runs successfully, and the unsupported option is silently ignored. SecuritySecure mode (with a security manager) is not supported. No Support for Client VM on Windows AMD64By default, Enterprise Server uses client VM to achieve best startup and deployment performance. If you are using Windows AMD64, edit the domain.xml file to remove the line <jvm-options>–client<jvm-options>. In this case, JVM ergonomics chooses the appropriate kind of VM for given platform. For more information about platform support, see Ergonomics in the 5.0 Java Virtual Machine. No Support for Launching Application Clients Through Java Web Start SoftwareAutomatic support for launching application clients by using Java Web Start software is not included . Enterprise Server Documentation SetThe following table provides titles and short descriptions of books in the Enterprise Server documentation set. Table 1–6 Books in the Enterprise Server Documentation Set
Features Available Only in the Full Platform ProfileThe following features of Sun GlassFish Enterprise Server v3 Preview are available only in the Full Platform Profile:
Connector modules that use only outbound communication features and work-management that does not involve inbound communication features are supported in the Web Profile. Other connector features are supported only in the Full Platform Profile. Java EE 6 StandardsSun GlassFish Enterprise Server v3 Preview implements work-in-progress versions, based on published drafts, of the Java EE standards that are listed in the following table. The table also indicates the distributions in which the implementation of a standard is available. · indicates that the implementation is available in the distribution. - indicates that the implementation is not available in the distribution.
Building on these standards, Enterprise Server v3 Preview provides a number of extensions, including the following:
Java EE 6 SDKEnterprise Server v3 Preview is available as part of the Java EE 6 SDK. The following versions of the Java EE 6 SDK are available:
How to Report Problems and Provide FeedbackIf you have problems with Sun GlassFish Enterprise Server v3 Preview, provide feedback through one of the following mechanisms:
Additional ResourcesUseful information can be found at the following locations: Third-Party Web Site ReferencesThird-party URLs are referenced in this document and provide additional, related information. Note – Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources. Accessibility FeaturesTo obtain accessibility features that have been released since the publication of these media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at http://sun.com/software/javaenterprisesystem/get.html. For information on Sun's commitment to accessibility, visit http://sun.com/access. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||