Sun Java System Application Server Enterprise Edition Release Notes for Microsoft Windows

Sun Java™ System Application Server Enterprise Edition Release Notes for Microsoft Windows

Version 8.1 2005Q2

Part Number 819-4264-10

The Sun Java System Application Server Enterprise Edition 8.1 2005Q2 product greatly simplifies the task of creating and administering web services applications. It provides superior performance, clustering, and high availability features for scalable services that continue to operate despite software and hardware faults. The Application Server provides a development path for web services that simplifies the development process while providing uniquely flexible growth opportunities.

These release notes contain important information available at the time of the Sun Java System Application Server 8.1 2005Q2 product release for Windows. Component requirements, platform summary, known problems, and other late-breaking issues are addressed here. Read this document before you begin using the Application Server product.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/app/docs/prod/entsys.05q4#hic. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.

This document contains the following sections:

Third-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.



Release Notes Revision History

This section lists the changes that have been made in these release notes after the initial release of the Application Server 2005Q2 component.

Table 1  Revision History

Revision Date

Description

February 2006

Revenue release.

November 2005

Beta release.


About Application Server 8.1 2005Q2

The Sun Java System Application Server Enterprise Edition 8.1 is a J2EE 1.4 platform-compatible server for the development and deployment of J2EE applications and Java technology-based web services in large-scale production environments.

This section includes:

What’s New in Application Server 8.1 2005Q2

The Application Server Enterprise Edition 8.1 2005Q2 Update 2 includes the following enhancements:

Application Server Product Releases

The Application Server product is delivered in various ways. The following table identifies the product delivered for the various delivery mechanisms:

Application Server Product Release

Delivery Mechanism

Application Server Enterprise Edition component within the Sun Java Enterprise System.

File-based distribution patch installation needed through Sunsolve

J2EE Support

The Sun Java System Application Server 8.1 2005Q2 supports the J2EE 1.4 platform. The following table describes the enhanced APIs available on the J2EE 1.4 platform.

Table 2  Major API changes on the J2EE 1.4 Platform 

API

Description

Components

Application and Application Client

Implementation of standard deployment descriptors by means of XML schemas

Enterprise JavaBeans (EJB) 2.1

Timer service and EJB Web-service endpoint

Java Servlet 2.4

Web-service endpoint filter

JavaServer Pages (JSP) 2.0 architecture

Expression language and tag library

J2EE Connector Architecture 1.5

Inbound resource adaptor and Java Message Service (JMS) pluggability

Web Services

Java Web Services Developer Pack 1.5

Integrated toolkit for building, testing and deploying XML applications, Web services, and Web applications

Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.1

Mapping for WSDL and Java technology and support for development of Web-service clients and endpoints

WS-I Basic Profile 1.0

The enabling element for interoperability using WSDL and SOAP

SOAP with attachment API for Java (SAAJ) 1.2

An API for SOAP-based messaging; fosters the creation of SOAP messages with attachments

Java APIs for XML Registries (JAXR) 1.0

A uniform and standard API for accessing XML registries, such as those for Universal Description Discovery and Integration (UDDI and ebXML)

Other

J2EE Deployment 1.1

Standard APIs that enable deployments of J2EE components and applications

J2EE Management 1.0

Definitions for the information model for managing the J2EE platform

Java Management Extensions (JMX) 1.2

Standard management API

Java Authorization Contract for Containers (JACC) 1.0

Definitions of security contracts between a J2EE Application Server and the authorization policy provider

Java API for XML Processing (JAXP) 1.2

An API with which applications can parse and transform XML documents; also adds support for processing of XML schemas

JMS 1.1

A messaging standard that enables J2EE application components to create, send, receive, and read messages; also adds support for uniform APIs for queues and topics

JavaMail 1.3

A set of abstract classes that model a mail system; also includes minor updates to the APIs

High Performance

The Application Server includes a high performance EJB container, Web container and services, and supports concurrent message delivery with the Sun Java System Message Queue software.

Scalability

The Application Server supports horizontal scalability through clustering of server instances and request load balancing. It also achieves class leading vertical scalability supporting large multi-processor machines. The integrated message broker can be clustered for better scalability and availability. Client access from HTTP clients, RMI/IIOP based Rich Client Applications, Web Services Clients, and JRM Clients can be load balanced to Application Server clusters.

High Availability

The Application Server includes load balancing for HTTP, IIOP, and JMS clients; HTTP session failover support; EJB clustering and failover support; highly available EJB timers; distributed transaction recovery; support for rolling application upgrades; and a high availability database for storing the transient state of J2EE applications.

Availability allows for failover protection of Application Server instances in a cluster. If one Application Server instance goes down, another Application Server instance takes over the sessions that were assigned to the unavailable server. Session information is stored in the HADB. HADB supports the persistence of HTTP sessions, Stateful Session Beans, and Single Sign On credentials.

JavaServer Faces 1.1 Support

The Sun Java System Application Server Enterprise Edition 8.1 supports JavaServer Faces 1.1 technology. The JavaServer Faces technology consists of a set of server-side APIs that represent user-interface components that manage their state, event, handling, and input validation. The APIs also define page navigation and support internationalization and accessibility. You can add custom UI components with a JSP custom tag library.

While developing with JavaServer Faces technology, each member of a development team can focus on a single piece of the process. A simple programming model then links the pieces, resulting in a much more efficient and simpler development cycle.

Hardware and Software Requirements

This section lists the requirements that must be met before installing the Sun Java System Application Server Enterprise Edition 8.1 product.

Platform Requirements

The following table lists the operating systems that are supported for Sun Java System Application Server Enterprise Edition 8.1 2005Q2 product. Additionally, the minimum and recommended memory requirements are identified for installing and running the Application Server

.

Table 3  Sun Java System Application Server 8.1 2005Q2 Platform Requirements 

Operating System

Minimum Memory

Recommended Memory

Minimum Disk Space

Recommended Disk Space

JVM

Microsoft Windows 2000 SP4

512 MB

1 GB

250 MB free

500 MB free

JDK 1.5.0.04

Microsoft Windows 2003 Enterprise Server

1 GB

2 GB

250 MB free

500 MB free

JDK 1.5.0.04

Microsoft Windows XP

1 GB

2 GB

250 MB free

500 MB free

JDK 1.5.0.04

To check your operating system version, use the ver command. To check the disk space use the mem command.

JDBC Drivers and Databases

The Sun Java System Application Server is designed to support connectivity to any DBMS with a corresponding JDBC driver. For a list of components that Sun has tested and found to be acceptable for constructing J2EE compatible database configurations, please refer to the following table:

Table 4  JDBC Drivers and Databases

JDBC Vendor

JDBC Driver Type

Supported Database Server

i-net Software

Type 4

Oracle (R) 8.1.7, 9i, 9.2.0.3
Sybase ASE 12.5.2
Microsoft SQL Server 2000 4.0 Service Pack 1

IBM

Type 2

IBM DB2 8.1 Service Pack 3+

PointBase

Type 4

PointBase Network Server 4.8

DataDirect

Type 4

Oracle (R) 8.1.7, 9i, 9.2.0.3
Sybase ASE 12.5.2
Microsoft SQL Server
IBM DB2 8.1 Service Pack 3+

Sun Java System JDBC Driver for Oracle

Type 4

Oracle (R) 9.2.0.3, 10G

Sun Java System JDBC Driver for DB2

Type 4

IBM DB2 8.1 Service Pack 3+

Sun Java System JDBC Driver for Sybase

Type 4

Sybase ASE 12.5.2

Sun Java System JDBC Driver for Microsoft SQL Server

Type 4

Microsoft SQL Server 2000 4.0 Service Pack 1

Oracle

Type 4, Type 2

Oracle (R) 9.2.0.3, 10G

For more information about i-net Software, see:

http://www.inetsoftware.de/

The following table identifies additional supported JDBC drivers; however these drivers are not J2EE compatible.

Table 5  JDBC Drivers not J2EE compatible

JDBC Vendor

JDBC Driver Type

Supported Database Server

Oracle

Type 4

Oracle (R) 9.2.0.3, 10G

Sybase

jConnector

Sybase ASE 12.5.1

Additional drivers have been tested to meet the JDBC requirements of the J2EE 1.4 platform with the JDBC Driver Certification Program. These drivers can be used for JDBC connectivity with the Sun Java System Application Server. While Sun offers no product support for these drivers, we support the use of these drivers with the Sun Java Enterprise System Application Server.

Configuring Oracle

Oracle JDBC drivers must be configured properly to be compliant with J2EE 1.4. Use the following configuration for Type 2 and Type 4 drivers:

  1. Use the JDBC driver from 9.2.0.3 or later.
  2. The Oracle database needs to have compatible=9.0.0.0.0 or higher in its parameter (init.ora) file.
  3. Use the ojdbc14.jar file.
  4. Configure the Application Server to define the following JVM property:

Configuring PointBase

Many sample applications use the PointBase database server included with the Application Server. When using Application Server Enterprise Edition, you must configure the PointBase database server before using it. Before using PointBase with the Application Server, however, note the supported configuration combination.

Table 6  Supported J2SE/PointBase Combinations

Application Server

PointBase

Supported

J2SE 5.0

J2SE 1.4.2

Unsupported

J2SE 5.0

J2SE 1.4

J2SE 5.0

J2SE1.4

There are two ways to configure PointBase:

To use the first method:

  1. Make sure you have the J2SE installed that you want to use.
  2. Download J2SE 1.4.2 if you do not already have it.

  3. Using the command appropriate for your operating system and shell, set the JAVA_HOME environment variable to the directory in which J2SE is installed; for example:

To use the second method, the procedure depends on the operating system.

Solaris and Linux

Edit the install_dir/pointbase/tools/serveroption/pbenv.conf configuration file, changing the line:

PB_JAVA=%%%PB_JAVA%%%

where J2SE_location is the directory where the J2SE is installed. If you installed J2SE with Application Server, it is installed by default to install_dir/jdk. After making this change, you can start PointBase using the startserver script.

Windows

Edit the install_dir\pointbase\tools\serveroption\pbenv.bat configuration file, changing the line:

set PB_JAVA=%%%PB_JAVA%%%

where J2SE_location is the directory in which the J2SE is installed. If you installed J2SE with Application Server, it is installed by default to install_dir\j2se1.4. After making this change, you can start PointBase by running startserver.bat.

Web Servers

This section lists the web servers that are supported for the Sun Java System Application Server Enterprise Edition 8.1 2005Q2.

Table 7  Supported Web Servers

Web Server

Version

Operating System

Sun Java System Web Server

6.1 +

Solaris SPARC 8, 9, 10
Solaris x86 9, 10
Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1

Browsers

This section lists the browsers that are supported with the Sun Java System Application Server Enterprise Edition 8.1 2005Q2.

Table 8  Browsers Supported

Browser

Version

Mozilla

1.4, 1.5, 1.6, 1.7.x

Netscape Navigator

4.79, 6.2, 7.0

Internet Explorer

5.5 Service Pack 2, 6.0

High Availability Requirements and Limitations

The following high availability requirements must be met before configuring the Sun Java System Application Server High Availability component:

Other Requirements

The following additional requirements should be met before installing the Sun Java System Application Server software.

Related Documentation

The Sun Java System Application Server documentation set covers the following product releases:

Unless otherwise specified, whenever either product release is mentioned in the documentation, both releases are implied.

In addition to these release notes, the Application Server component includes an entire set of documentation that can be found at this location:

The following table summarizes the books included in the Application Server core application documentation set.

Table 9  Books in This Documentation Set 

Book Title

Description

Release Notes

Late-breaking information about the software and the documentation. Includes a comprehensive, table-based summary of the supported hardware, operating system, JDK, and JDBC/RDBMS.

Quick Start Guide

How to get started with the Sun Java System Application Server product.

Installation Guide

Installing the Sun Java System Application Server software and its components.

Deployment Planning Guide

Evaluating your system needs and enterprise to ensure that you deploy Sun Java System Application Server in a manner that best suits your site. General issues and concerns that you must be aware of when deploying an application server are also discussed.

Developer’s Guide

Creating and implementing Java™ 2 Platform, Enterprise Edition (J2EE™ platform) applications intended to run on the Sun Java System Application Server that follow the open Java standards model for J2EE components and APIs. Includes general information about developer tools, security, assembly, deployment, debugging, and creating lifecycle modules.

J2EE 1.4 Tutorial

Using J2EE 1.4 platform technologies and APIs to develop J2EE applications and deploying the applications on the Sun Java System Application Server.

Administration Guide

Configuring, managing, and deploying the Sun Java System Application Server subsystems and components from the Administration Console.

High Availability Administration Guide

Post-installation configuration and administration instructions for the high-availability database.

Administration Reference

Editing the Sun Java System Application Server configuration file, domain.xml.

Upgrade and Migration Guide

Migrating your applications to the new Sun Java System Application Server programming model, specifically from Application Server 6.x and 7. This guide also describes differences between adjacent product releases and configuration options that can result in incompatibility with the product specifications.

Performance Tuning Guide

Tuning the Sun Java System Application Server to improve performance.

Troubleshooting Guide

Solving Sun Java System Application Server problems.

Error Message Reference

Solving Sun Java System Application Server error messages.

Reference Manual

Utility commands available with the Sun Java System Application Server; written in manpage style. Includes the asadmin command line interface.


Bugs Fixed in This Release

The following table describes the bugs fixed in Application Server 8.1 2005Q2.

Table 10  Fixed Bugs in Application Server 8.1 2005Q2

Bug Number

Description

6295958

Impossible to enter AS master password and the master pswd is unknown to the user.

Note: Master password will be the same as admin password in the Configure Automatically during Installation mode whereas in the Configure Manually after Installation mode, the user can specify the different password in the CLI.


Important Information

This section covers the following topics:

Installation Notes

For information about patch requirements and installation, see the following section:

Patch Requirement Information

The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.

To access the patches, go to http://sunsolve.sun.com.

Table 11  Application Server 8.1 2005Q2 Alignment Patches Required For Windows

Patch Number

Patch Description

121533-01

Windows (MSI): Sun Java™ System Message Queue 3 2005Q4

121523-01

Windows (MSI): Shared Components Patch

121528-01

Windows (MSI): Sun Java™ System Application Server 8.1 2005Q2

For detailed information about Upgrade procedure of the Application Server from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for Microsoft Windows located at http://docs.sun.com/app/docs/doc/819-4461.

Compatibility Issues

In the next major release of the Sun Java System Application Server Enterprise Edition the following incompatibilities will be introduced:

Deploytool

Deploytool will no longer be available. The equivalent functionality is available in the NetBeans IDE. For more information and to plan a migration, please see J2EE 1.4 tutorial for NetBeans 4.1 at http://www.netbeans.org/kb/41/j2ee-tut/index.html.

Verifier

Classloader Changes

In the current release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix attributes of domain.xml (application server configuration file) are available in the JVM system classpath. An application depending on this behavior might be using the following methods from the class java.lang.ClassLoader to access classes or other resources from JVM system classpath:

In the next major release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix will no longer be available in the JVM system classpath. If an application uses one of the methods mentioned above, Sun strongly recommends using an equivalent method that does not assume that the resources are available in the system classpath. The equivalent methods that do not rely on the JVM system classpath are available in java.lang.ClassLoader and should be used when possible; for example:

EXAMPLE: Old Code

java.net.URL url = ClassLoader.getSystemResource

("com/acme/tools/tools.properties");

EXAMPLE: Suggested Change

java.net.URL url = this.getClass().getClassLoader().getResource

("com/acme/tools/tools.properties");

If it is not possible to change the code, then you may choose to use a new configuration option that will be added in the next release to set JVM system classpath.

Web Service Security Configuration

Security for Web services can be configured using the files wss-client-config.xml and wss-server-config.xml. Please note that the content and names of these configuration files are unstable and likely to change. The equivalent functionality will continue to be available.

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this 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.


Known Issues and Limitations

This section describes the known issues and limitations of Application Server Enterprise Edition 8.1 2005Q2 for Microsoft Windows.

This section describes known problems and associated workarounds for the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 component. If a summary statement does not specify a particular platform, the problem applies to all platforms. This information is organized into the following sections:

Administration

This section describes known administration issues and associated solutions.

Bug ID

Summary

6196993

Cannot restore backed-up domain with another name.

Mirroring of a domain on the same Application Server installation cannot be performed using the backup-domain and restore-domain commands because the domain cannot be restored using a different name than the original, even though the asadmin restore-domain command provides an option to rename the domain. Renaming the backed-up domain appears to succeed, but attempts to start the renamed domain fail because the entries in the domain configuration are not changed, and startserv and stopserv use the original domain name to set paths.

Solution

The domain name used for restore-domain must be the same as that used for the original backup-domain command. The backup-domain and restore-domain commands in Application Server 8.1 work only for backing up and restoring the same domain on the same machine.

6200011

Starting Application Server with additional JMX Agent is not supported.

J2SE 1.4.x, 5.0, or later can be configured on the Application Server. An integral feature of J2SE 5.0 platform is the ability to start a JMX agent. This is activated when you explicitly set system properties at the server startup.

Example values include:

name="com.sun.management.jmxremote" value="true"

name="com.sun.management.jmxremote.port" value="9999"

name="com.sun.management.jmxremote.authenticate" value="false"

name="com.sun.management.jmxremote.ssl" value="false"

After configuring JMX properties and starting the server, a new jmx-connector server is started within the Application Server Virtual Machine. An undesirable side-effect of this is that the administration functions are affected adversely, and the Application Server administration Console and command—line interface may produce unexpected results. The problem is that there are some conflicts between the built in jmx-connector server and the new jmx-connector server.

Solution

If using jconsole (or any other JMX-compliant client), consider reusing the standard JMX Connector Server that is started with Application Server startup.

When the server starts up, a line similar to the one shown below appears in the server.log. You can connect to the JMXService URL specified there and perform the same management/configuration operations after successfully providing the credentials; for example:

[#|2004-11-24T17:49:08.203-0800|INFO|sun-appserver-ee8.1|javax.enterprise.system

6236544, 6275436

Load balancer configuration file does not get created with the endpoint URL of any web service.

When setting up the load balancer configuration with an application that has an EJB module that exports a web service URL, the context root for the web service isn’t in the resulting loadbalancer.xml file.

Solution

  1. Edit the loadbalancer.xml file to add the missing web module as follows:
  2. <web-module context-root="context-root-name"

    disable-timeout-in-minutes="30" enabled="true"/>

  3. Replace context-root-name value with the context root name of the web service that was exposed as an EJB.

Application Client

This section describes known application client issues and associated solutions.

Bug ID

Summary

6193556

Library JAR packaged in Application Client Archive overwrites MANIFEST file.

If you have a top level JAR file inside your client JAR (in this case, reporter.jar), when you deploy the client JAR, the MANIFEST file for that JAR overwrites the MANIFEST file for the client JAR.

Solution

None at this time.

Bundled Sun JDBC Drivers

This section describes known bundled Sun JDBC driver issues and associated solutions.

Bug ID

Summary

6165970

Applications using the TRANSACTION_SERIALIZABLE isolation level with the bundled Sun driver for Microsoft SQL Server may hang when using a prepared statement to update if two parallel transactions are running and one of them is rolled back.

To set a desired isolation level for a connection, the corresponding connection pool must be created at that same isolation level. See the Administration Guide for details about configuring connection pools.

Solution

None at this time.

6170432

PreparedStatement Errors.

Description #1

If an application generates more than 3000 PreparedStatement objects in one transaction, the following error may occur with DB2:

[sunm][DB2 JDBC Driver] No more available statements.Please recreate your package with a larger dynamicSections value.

Solution #1

Add following properties to the connection pool definition to get the driver to rebind DB2 packages with a larger dynamic sections value:

createDefaultPackage=true replacePackage=true

dynamicSections=1000

See the Administration Guide for details about configuring connection pools.

Description #2

Related to the PrepardStatement error above, another error message that may be thrown is:

[sunm][DB2 JDBC Driver][DB2]Virtual storage or database resource is not available.

Solution #2

Increase the DB2 server configuration parameter APPLHEAPSZ. A good value is 4096.

Description #3

Isolation level TRANSACTION_SERIALIZABLE. If your application uses isolation level TRANSACTION_SERIALIZABLE and uses one of the parameters suggested above, it might hang while obtaining a connection.

Solution #3

To set desired isolation level for a connection, the corresponding connection pool has to be created at that isolation level. See the Administration Guide for instructions.

6189199

Problems setting isolation level with the bundled Sun driver for Sybase Adaptive Server.

Applications using the TRANSACTION_SERIALIZABLE isolation level with the bundled Sun driver for Sybase Adaptive Server may hang when using a prepared statement to update if two parallel transactions are running and one of them is rolled back. Connection rollback fails with following message, and the rolled back connections cannot be used anymore:

java.sql.SQLException: [sunm][Sybase JDBC Driver]Request cannot be submitted due to wire contention

Sybase Adaptive Server does not support the TRANSACTION_REPEATABLE_READ isolation level. However, querying DatabaseMetaData, the bundled Sun driver returns that this isolation level is supported by the database. Applications using the this isolation level will fail.

Applications using the bundled Sun driver cannot set the TRANSACTION_READ_UNCOMMITTED isolation level. The application throws the following exception on the first DataBaseMetaData access:

java.sql.SQLException: [sunm][Sybase JDBC Driver][Sybase]The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table ’sybsystemprocs.dbo.spt_server_info’.

Solution

None at this time.

Connectors

This section describes known J2EE connector architecture issues and associated solutions.

Bug ID

Summary

6188343

After restarting a DAS instance, undeploying the connector module fails when cascade is set to false.

In this scenario, a standalone or embedded connector module is deployed in DAS and connector connection pools, and resources are created for the deployed module. After restarting the DAS instance, undeploying the connector module fails when cascade is set to false with the following exception:

[#|2004-10-31T19:52:23.049-0800|INFO|sun-appserver-ee8.1|javax.enterprise.system .core|_ThreadID=14;|CORE5023: Error while unloading application [foo]|#]

Solution

Use cascaded undeploy (set the cascade option to true) for undeploying standalone and embedded connectors after restart of the DAS instance.

Documentation

This section describes known documentation issues and associated solutions.

Bug ID

Summary

Various IDs

Javadoc Inconsistencies.

The Javadoc for several AMX interfaces and methods is either missing or incorrect:

Getter methods for NumConnAcquired and NumConnReleased statistics are missing from ConnectorConnectionPoolStats and AltJDBCConnectionPoolStats. These getter methods will be added in a future release as getNumConnAcquired() and getNumConnReleased().

Calling the following methods in EJBCacheStats will throw an exception: getPassivationSuccesses(), getExpiredSessionsRemoved(), getPassivationErrors(), getPassivations().
This will be fixed in a future release.

The AMX MBeans may require several seconds after server startup before they are all registered and available for use. A future release will make it possible to determine when the AMX MBeans are fully loaded.

The constant XTypes.CONNNECTOR_CONNECTION_POOL_MONITOR is misspelled ("NNN"). This will be corrected in a future release.

6265624

Bundled ANT throws java.lang.NoClassDefFoundError.

The following exception is thrown in thread "main" java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/Launcher.

Solution

Use the bundled ANT for things outside the Application Server is not recommended.

Lifecycle Management

This section describes known lifecycle management issues and associated solutions.

Bug ID

Summary

6193449

After setting the ejb-timer-service property minimum-delivery-interval to 9000, an attempt to set the ejb-timer-service property redelivery-interval-in-mills to 7000 causes the set command to fail with the following error:

[echo] Doing admin task set
[exec] [Attribute(id=redelivery-interval-internal-in-millis) : Redelivery-Interval should be greater than or equal to Minimum-delivery-interval-in-millis (9,000)]
[exec] CLI137 Command set failed.

minimum-delivery-interval is the minimal interval duration between deliveries of the same periodic timer.

redelivery-interval-in-mills is the time the timer service will wait after a failed ejbTimeout before attempting redelivery.

The problem is that the logic that relates the redelivery interval property to the minimum delivery property is incorrect and prevents you from using the GUI or the CLI to set any value where the minimum delivery interval is greater than redelivery interval.

The minimum-delivery-interval-in-millis must always be set equal to or higher than ejb-timer-service property redelivery-interval-in-millis. The problem is that there is an erroneous validation check in the Application Server to verify that the value for redelivery-interval-in-millis is greater than the value for minimum-delivery-interval-in-millis.

Solution

Use the default values for these properties, as follows:

minimum-delivery-interval(default)=7000
redelivery-interval-in-millis(default)=5000

Values other than these defaults will generate an error.

Logging

This section describes known logging issues and solutions.

Bug ID

Summary

6180095

Setting debug statement for access,failure causes hanging in Application Server startup.

Setting the java.security.debug option for the JVM will cause the server instance startup to freeze with a deadlock; for example, setting the following in domain.xml causes the problem: <jvm-options>-Djava.security.debug=access,failure</jvm-options>

None at this time. Please avoid setting this flag.

Monitoring

This section describes known monitoring issues and associated solutions.

Bug ID

Summary

6174518

Some of the HTTP Service monitoring statistics do not present useful information and should be ignored.

When viewing the monitoring statistics of some elements of the HTTP Service, some values presented do not correspond to current values or are always 0. Specifically, the following HTTP Service statistics do not present information applicable to the Application Server, and should be ignored:

http-service

load1MinuteAverage

load5MinuteAverage

load15MinuteAverage

rateBytesTransmitted

rateBytesReceived

pwc-thread-pool (the element)

Solution

These monitors will be removed in future releases and replaced with more appropriate information.

6191092

Monitoring MBean for an undeployed EJB module is not removed, even though all statistics under that monitoring name are moved.

For example:

EJBModuleMonitorMap().size() = 1 eventhough ejb module is undeployed EJBModu

This true for both EJB modules and applications. Both programmatically (through MBean API) and through asadmin list/get, an empty monitoring MBean still exists.

Diagnostics

asadmin list -m "server.applications" shows the following output:
server.applications.MEjbApp
server.applications.__ejb_container_timer_app
server.applications.adminapp
server.applications.admingui
server.applications.com_sun_web_ui
server.applications._export_install_nov-11_domains_domain1_applications_j2ee-

You can look at statistics:

bin/asadmin list -m "server.applications._expo
rt_install_nov-11_domains_domain1_applications_j2ee-modules_sqe_ejb_s1_01"
server.applications._export_install_nov-11_domains_domain1_applications_j2eeules_
sqe_ejb_s1_01.SQEMessage
server.applications._export_install_nov-11_domains_domain1_applications_j2eeules_
sqe_ejb_s1_01.TheGreeter

Once you undeploy:

_export_install_nov-11_domains_domain1_applications_j2ee-modules_sqe_ejb_s1_0

If you do a list command, you still see the application:

 

 

asadmin list -m "server.applications"
server.applications.MEjbApp
server.applications.__ejb_container_timer_app
server.applications._export_install_nov-11_domains_domain1_applications_j2eeules_sqe_ejb_s1_01
server.applications.adminapp
server.applications.admingui
server.applications.com_sun_web_ui

but it does not contain any monitoring statistics:

asadmin list -m "server.applications._expo
rt_install_nov-11_domains_domain1_applications_j2ee-modules_sqe_ejb_s1_01"
Nothing to list at server.applications.-export-install-nov-11-domains-domain1 applications-j2ee-modules-sqe-ejb-s1-01.

To get the valid names beginning with a string, use the wildcard (‘*’)

character. For example, to list the names of all the monitorable entities that

begin with server, use list "server.*".

Solution

This is harmless. Module can be safely redeployed with out any problems. The root monitoring Mbean is not removed, but it is empty.

PointBase

This section describes known and associated solutions related to PointBase.

Bug ID

Summary

6184797

Setting the isolation levels on a connection pool for an application causes exceptions in PointBase.

For a JDBC connection pool pointing to a PointBase database installation, setting the transaction-isolation-level pool attribute to any value other than the default (Connection.TRANSACTION_READ_COMMITTED) causes an exception. However, setting this same parameter to non-default values for pools pointing to other databases does not throw an exception.

Solution

For a JDBC connection pool pointing to a PointBase database installation, do not attempt to set the transaction-isolation-level.

6204925

PointBase throws an exception if a network server and embedded drivers are used together.

The bundled PointBase sometimes throws an exception if the network server driver and the embedded driver are simultaneously used.

Solution

Use either the embedded driver or the network server driver, but not both.

6264969,6275448

Upgrade problem where the default PointBase database is overwritten

When upgrading to Application Server Enterprise Edition 8.1 2005Q2 Update 2, the Update release patch overwrites the Pointbase default database.

Solution

Recreate or re-enter any scheme or data that existed prior to the upgrade. If you deployed applications with CMP beans with the generate table option, you must undeploy or redeploy the application to have the tables regenerated.

Samples

This section describes known and associated solutions related to the sample code included with the Application Server 8.1 product.

Bug ID

Summary

6195092

On Windows, setup-one-machine-cluster hangs but works on Solaris; mqfailover requires Ctrl+C to cancel and then must be re-run.

From

install_dir\samples\ee-samples\failover\apps\mqfailover\docs\index.html, if you run the following commands:

  • Console 1

    cd install_dir\samples\ee-samples asant start-mq-master-broker1

  • Console 2

    cd install_dir\samples\ee-samples asant start-mq-cluster-broker1

  • Console 3

    cd install_dir\samples\ee-samples asant start-mq-cluster-broker2

  • Console 4

    cd install_dir\samples\ee-samples asadmin start-domain domain1

If you have already executed

asant setup-one-machine-cluster-without-ha or asant

setup-one-machine-cluster-with-ha for any other Enterprise Edition

sample, then execute asant configure-mq otherwise execute

asant setup-one-machine-cluster-and-configure-mq. In this case, the command appears to succeed:

start_nodeagent: [echo] Start the node agent cluster1-nodeagent [exec] Comman

But then the system hangs indefinitely.

Solution

None at this time. This problem similarly affects all Enterprise Edition samples that use this ant target on Windows. A workaround is to Ctrl+C out of the hung process and then rerun it.

6198003

Documentation does not explicitly state that you need to create JMS resources before running the MQ Failover Sample Application following the asadmin deploy instructions.

The error thrown is as follows:

Install_Location>\AppServer\domains\domain1\config\sun-acc.xml -name MQFailoverTestClient -t Nov 18, 2004 10:50:17 PM com.sun.enterprise.naming.NamingManagerImpl bindObjects SEVERE: NAM0006: JMS Destination object not found: jms/durable/TopicA Nov 18, 2004 10:50:18 PM com.sun.enterprise.naming.NamingManagerImpl bindObjects SEVERE: javax.naming.NameNotFoundException javax.naming.NameNotFoundException

The documentation does not explicitly state that JMS resources must be manually created if manual deployment is done using asadmin deploy commands, and that the provided ant targets to deploy the sample application should be used.

Solution

Use the asant deploy target for the build.xml script, which creates the required JMS resources to run the application.

Security

This section describes known issues and associated solutions related to Application Server and web application security and certificates.

Bug ID

Summary

6183318

Cannot run WebServiceSecurity applications on Enterprise Edition with J2SE 5.0.

WebServiceSecurity applications cannot run with J2SE 5.0 because:

  • J2SE 5.0 PKCS11 does not support UNWRAP mode
  • J2SE 5.0 PKCS11 does not support

    RSA/ECB/OAEPWithSHA1AndMGF1Padding with PKCS11

The J2SE team has filed "CR 6190389: Add support for the RSA-PKCS1 and RSA-OAEP wrap/unwrap mechanisms" for this bug.

Solution

Use J2SE 1.4.2 with any other JCE provider (not the one included by default). Note that hardware accelerator support will not be present in this configuration.

Web Container

This section describes known web container issues and associated solutions.

Bug ID

Summary

5004315

On Windows, deploying an application using --precompilejsp=true can lock JAR files in the application, causing later undeployment or redeployment to fail.

If you request precompilation of JSPs when you deploy an application on Windows, later attempts to undeploy that application or to redeploy it (or any application with the same module ID) will not work as expected. The problem is that JSP precompilation opens JAR files in your application but does not close them, and Windows prevents the undeployment from deleting those files or the redeployment from overwriting them.

Note that undeployment succeeds to a point, in that the application is logically removed from the Application Server. Also note that no error message is returned by the asadmin utility, but the application’s directory and the locked jar files remain on the server. The server’s log file will contain messages describing the failure to delete the files and the application’s directory.

Attempts to redeploy the application after undeploying fail because the server tries to remove the existing files and directory, and these attempts also fail. This can happen if you try to deploy any application that uses the same module ID as the originally deployed application, because the server uses the module ID in choosing a directory name to hold the application’s files.

Attempts to redeploy the application without undeploying it first will fail for the same reasons.

Diagnostics

If you attempt to redeploy the application or deploy it after undeploying it, the asadmin utility returns an error similar to the one below.

An exception occurred while running the command. The exception message is: CL

Solution

If you specify --precompilejsps=false (the default setting) when you deploy an application, then this problem will not occur. Be aware that the first use of the application will trigger the JSP compilation, so the response time to the first request will be longer than for later requests.

Note also that if you do precompile, you should stop and restart the server before undeploying or redeploying the application. The shutdown frees the locked JAR files so the undeployment or redeployment after the restart can succeed.

6172006

Unable to deploy WAR with Servlet 2.4-based web.xml that contains an empty <load-on-startup> element.

The optional load-on-startup servlet element in a web.xml indicates that the associated servlet is to be loaded and initialized as part of the startup of the web application that declares it.

The optional content of this element is an integer indicating the order in which the servlet is to be loaded and initialized with respect to the web application’s other servlets. An empty <load-on-startup> indicates that the order is irrelevant, as long as the servlet is loaded and initialized during the startup of its containing web application.

The Servlet 2.4 schema for web.xml no longer supports an empty <load-on-startup>, meaning that an integer must be specified when using a Servlet 2.4 based web.xml. If specifying an empty <load-on-startup>, as in <load-on-startup/>, the web.xml will fail validation against the Servlet 2.4 schema for web.xml, causing deployment of the web application to fail.

Backwards compatibility issue. Specifying an empty <load-on-startup> still works with Servlet 2.3 based web.xml.

Solution

Specify <load-on-startup>0</load-on-startup> when using a Servlet 2.4 based web.xml to indicate that servlet load order does not matter.

6184122

Unable to compile JSP page on resource constrained servers.

The JSP page is accessed but fails to compile, and the server log contains the error message "Unable to execute command" with the following stack trace:

at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.j

at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:427)

at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExte

at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute(JavacExterna

at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842)

at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)

at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:396)

Solution

Set the JSP compilation switch "fork" to "false."

This can be done either of two ways:

  • Globally, by setting the fork init parameter of the JspServlet in

${S1AS_HOME}/domains/domain1/config/default-web.xml to false:

<servlet> <servlet-name>jsp</servlet-name>

<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> .... <

<param-name>fork</param-name> <param-value>false</param-value> </init-para

  • On a per-web application basis, by setting the fork JSP configuration property in sun-web.xml to false:

<sun-web-app> <jsp-config> <property name="fork" value="false" /> </jsp-co

Either setting will prevent ant from spawning a new process for javac compilation.

6188932

Application Server does not support auth-passthrough Web Server 6.1 Add-On.

The Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Update 2 adds support for the functionality provided by the auth-passthrough plugin function available with Sun Java System Application Server Enterprise Edition 7.1. However, in Application Server Enterprise Edition 8.1 2005Q2 Update 2, the auth-passthrough plugin feature is configured differently.

The auth-passthrough plugin function in Application Server Enterprise Edition 7.1 has been useful in two-tier deployment scenarios, where:

  • Application Server instance is protected by a second firewall behind the corporate firewall.
  • No client connections are permitted directly to the Application Server instance.

In such network architectures, a client connects to a front-end web server, which has been configured with the service-passthrough plugin function and forwards HTTP requests to the proxied Application Server instance for processing. The Application Server instance can only receive requests from the web server proxy, but never directly from any client hosts. As a result of this, any applications deployed on the proxied Application Server instance that query for client information, such as the client’s IP address, will receive the proxy host IP, since that is the actual originating host of the relayed request.

In Application Server Enterprise Edition 7.1, the auth-passthrough plugin function could be configured on the proxied Application Server instance in order to make the remote client’s information directly available to any applications deployed on it; as if the proxied Application Server instance had received the request directly, instead of via an intermediate web server running the service-passthrough plugin.

In Application Server Enterprise Edition 8.1 2005Q2 Update 2, the auth-passthrough feature may be enabled by setting the authPassthroughEnabled property of the <http-service> element in domain.xml to TRUE, as follows:

<property name="authPassthroughEnabled" value="true"/>

The same security considerations of the auth-passthrough plugin function in Application Server Enterprise Edition 7.1 also apply to the authPassthroughEnabled property in Application Server Enterprise Edition 8.1 2005Q2 Update 2. Since authPassthroughEnabled makes it possible to override information that may be used for authentication purposes (such as the IP address from which the request originated, or the SSL client certificate), it is essential that only trusted clients or servers be allowed to connect to an Application Server Enterprise Edition 8.1 2005Q2 Update 2 instance with authPassthroughEnabled set to TRUE. As a precautionary measure, it is recommended that only servers behind the corporate firewall should be configured with authPassthroughEnabled set to TRUE. A server that is accessible through the Internet must never be configured with authPassthroughEnabled set to TRUE.

Notice that in the scenario where a proxy web server has been configured with the service-passthrough plugin and forwards requests to an Application Server 8.1 Update 2 instance with authPassthroughEnabled set to TRUE, SSL client authentication may be enabled on the web server proxy, and disabled on the proxied Application Server 8.1 Update 2 instance. In this case, the proxied Application Server 8.1 Update 2 instance will still treat the request as though it was authenticated via SSL, and provide the client’s SSL certificate to any deployed applications requesting it.

6314126

If running or installing any Sun Application Server on the Windows platform, it is a requirement that the file system be NTFS and not FAT or FAT32.

Load Balancer

User has to specify the following entries to the CLI while configuring Load Balancer in Configure Manually After Installation mode

The Load-Balancer Plug-in is configured to use ports 1111 and 1112 in the server used for AS_WSINSTANCENAME in the ASConfigurator.properties file. Following entries must be specified to the command line interface before configuring Load Balancer in Configure Manually After Installation mode:

Workaround

None.

The Load-Balancer Plug-in is configured to use ports 1111 and 1112

The Load-Balancer Plug-in is configured by default to use ports 1111 and 1112 in the ASConfigurator.properties file.

Workaround

None.

Application Server installation behavior and Application Server components do not correspond to JES 3 FCS Solaris/Linux build (6290539)

In Windows, if Application Server is selected, all the subcomponents will get selected by default. This is the behavior of MSI. Users have to deselect the specific sub components that are not needed, like load balancer and node agent.

In Windows Application Server has hard dependency in HADB. So the user can not install Application Server by unselecting the HADB in Configure Automatically During Installation mode. However the user can unselect HADB in Configure Later After Installation mode.

Configuration

Initial configurator in Configure Manually after Installation does not have GUI

The initial configurator used in Configure Manually after Installation mode does not have a GUI support.

Workaround

CLI is provided to the user for configuring in Configure Manually after Installation mode.

User has to accept default setting for nodeagents while configuring Application Server using Configure Manually after Installation (6372244)

Workaround

Accept the default value (nodeagents) for Nodeagent name during configuration in Configure Manually after Installation mode.

Cannot start server with –server option (6369978)

Workaround

Change the forward slashes to back slashes of the value of variable AS_NATIVE_LAUNCHER_LIB_PREFIX in the <Application_Server_Home>\config\asenv.bat file

i.e. change the value /jre/bin/client to \jre\bin\client

User can use \jre\bin\server also according to performance requirements.

In Configure Automatically During Installation, when Application Server is used as container, instance name used for deploying the applications is 'Appserver1'. This is different from Solaris where the instance name used is 'server' (6287671)


Redistributable Files

Sun Java System Application Server Enterprise Edition 8.1 does not contain any files that can be redistributed.


How to Report Problems and Provide Feedback

Use the following resources to handle problems you may encounter with the Application Server product:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:

Please provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of these Release Notes document is 819-4264-10.


Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations:


Copyright � 2006 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

SUN PROPRIETARY/CONFIDENTIAL.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.


Copyright � 2006 Sun Microsystems, Inc. Tous droits r�serv�s.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Propri�t� de SUN/CONFIDENTIEL.

L'utilisation est soumise aux termes du contrat de licence.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.