- Book Information
- Chapter 1 Overview
- Chapter 2 About Application Server Platform Edition 9.0 Update 1
- What’s New in the 9.0 Update 1 Release
- Hardware and Software Requirements
- Java EE 5 Platform APIs
- Java EE 5 SDK
- Switching to Another Supported Java Version
- Chapter 3 Known Issues and Limitations
- Administration
- The package-appclient script does not work if domain1 is not present. (ID 6171458)
- Starting Application Server with additional JMX Agent is not supported. (ID 6200011)
- InvalidJvmOptionException is thrown on stopping server if JDK path contains spaces (Windows) (ID 6475341)
- display-error-statistics brings negative stats
- Application Client
- Installation
- Lifecycle Management
- Java Persistence API
- The query compiler does not check all the rules as defined in the Java Persistence Language specification.
- In some cases, the query compiler throws a misleading error message, because it mentions the wrong token in the error message. (Glassfish ID 550)
- Two persistence units containing the same class cannot currently be deployed in the same EAR file.
- You cannot list MappedSuperclass explicitly using class element in persistence.xml. (Glassfish ID 558)
- Unable to map null database values to primitives.
- Upgrade
- Domains created in custom-path other than install_dir/domains directory are not upgraded directly while upgrading from Application Server Platform Edition 8 to Application Server Platform Edition 9.0 Update 1. (ID 6165528)
- The installer running “Upgrade in place” fails to start upgrade tool on some Linux systems after clicking on the “Start Upgrade Wizard” button. (6207337)
- Must close Application Server files when running Upgrade Tool on Windows
- Web Container
- Administration