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.

September 2004

Sun Java System Application Server 8 2004Q4 Beta release.

Components

Application and Application Client

Implementation of standard deployment descriptors by means of XML schemas

Enterprise JavaBeans (EJB) 2.1

Time 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

Web services for J2EE 1.1

Portable Web-service descriptors

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 between 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 application 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

Management of standards

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

30646

Fixed implementation so that it compiles under J2SE 5.0. Changed the J2SE 5.0 reserved keyword "enum" to "enum_".

NOTE: the JAXP 1.2 classes will need to be specified with J2SE 5.0 since the 5.0 bundled JAXP 1.3 packages have been moved around and re-named.

30647

Followed the BluePrints Guidelines for web application project structure. Most IDEs assume the BluePrints structure so abiding by these guidelines will help them integrate the examples.

The following changes were made to the examples directory structure:

None

Sun Java System Application Server 8 2004Q4 Beta contains an implementation of JSTL 1.1.1 that uses the internally named com.sun.* JAXP classes. If you use another JSTL implementation, for instance from Apache, with J2SE 5.0 you will need to include a JAXP implementation with your web application.

Sun Solaris 9, 10 (SPARC)
Solaris 9, 10 (x86)

512 MB

1 GB

250 MB free

500 MB free

JDK 1.4.2_05
JDK 1.5

Redhat Enterprise Linux 2.1 Update 2, 3.0 Update 1

512 MB

1 GB

83 MB free

300 MB free

JDK 1.4.2_05
JDK 1.5

Microsoft Windows 2000 Advanced Server Service Pack 4+

512 MB

1 GB

250 MB free

500 MB free

JDK 1.4.2_05
JDK 1.5

Microsoft Windows Server 2003

512 MB

1 GB

250 MB free

500 MB free

JDK 1.4.2_05
JDK 1.5

i-net Software

Type 4

Oracle (R) 8.1.7, 9i, 9.2.0.3

i-net Software

Type 2

Oracle (R) 9i,

i-net Software

Type 4

Sybase ASE 12.5.2

i-net Software

Type 4

MS 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

Oracle

Type 4

Oracle (R) 9.2.0.3, 10G

Sybase

jConnector

Sybase ASE 12.5.1

Sun Java System Web Server

6.0 Service Pack 6+

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

Apache Web Server

1.3.27+

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

Microsoft IIS

5.0+

Windows Server 2003
Windows 2000 Advanced Server Service Pack 4+

Mozilla

1.4

Netscape Navigator

4.79, 6.2

Internet Explorer

5.5 Service Pack 2, 6.0

Release Notes

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

Compatibility Guide

Differences between the adjacent product releases and configuration options that may result in incompatibility with the product specifications.

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, such as sample applications, the Administration Console, and the high-availability components. Instructions for implementing a basic high-availability configuration are included.

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

Information and instructions on the configuration, management, and deployment of the Sun Java System Application Server subsystems and components, from both the Administration Console and the command-line interface. Topics include cluster management, the high-availability database, load balancing, and session persistence. A comprehensive Sun Java System Application Server glossary is included.

Reference

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

Migration Guide

Migrating your applications to the new Sun Java System Application Server programming model, specifically from iPlanet Application Server 6.x and from Netscape Application Server 4.0. Includes a sample migration.

Performance Tuning Guide

How and why to tune your Sun Java System Application Server to improve performance.

Troubleshooting Guide

Information on solving Sun Java System Application Server problems.

Diagnostics in Log Resource Bundles

Information on solving Sun Java System Application Server error messages.

Utility Reference Manual

Utility commands available with the Sun Java System Application Server; written in manpage style.

6165776

On Application Server Enterprise Edition 8, the bundled DataDirect driver does not work out-of-the-box.

The following additional steps are required to use the bundled DataDirect driver with the Application Server Enterprise Edition 8:

1.  Copy the relevant JAR files into the lib/ext directory for the domain.

2.  Restart the domain.

The bundled DataDirect drivers are located at install_dir/lib/jdbcdrivers directory.

Solution

Put smbase.jar, smutil.jar and smoracle.jar in the CLASSPATH.

6165776

Cascade connector undeploy fails in remote Enterprise Edition deployment scenarios.

When a connector module is deployed on a cluster which has instances on local and remote machine(s) and the user invokes undeploy of the connector module with the cascade option set to true, the undeployment fails with the following error:

CLI171 Command undeploy failed: ERROR - Stop Application in remote-server-instance Component not registered.

Solution

The cascade option in the undeploy command is used to automatically delete dependent resources of a connector module. Instead of using the cascade option in remote server instance deployments in the Enterprise Edition of the Application server, delete the dependent resources using the relevant asadmin command or the Admin Console, then invoke the undeploy command without the cascade option.

5052946

DBSCHEMA: 117 failures in CMP with new version of oracle inet driver

The capture-schema utility does not successfully capture all of the table information needed by the CMP container when using the inet Oraxno 2.06 or later driver. The maximum size of the LOB DataType on Oracle is 4GB. Starting with inet Oraxno release 2.06, the JDBC driver will not return the correct size of 4GB for a LOB via DatabaseMetaData.getColumns().

Solution

Use a previous version of the inet Oraxno driver with capture-schema. This does not effect the use of the Oraxno 2.06 driver with the Sun Java System Application Server after you capture the information for the schema.

5036156

On Windows, invoking the Sun-specific Settings CMP Database, then saving the changes causes the changes to be lost and a tmp#####.jar file to be created.

Changes may be lost for the Container Managed Persistence Enterprise Java Bean JAR after the CMP Database dialog has been invoked by any of the following ways:

1.  Click on Sun-specific Settings button on the EJB JAR General tab.

2.  Click on Sun-specific Settings button on EJB General tab. Select CMP Database from the View menu.

3.  Click on the CMP Database (Sun-specific) button on Entity tab.

Solution

When this problem occurs a tmp#####.jar is created in the same location as the original CMP EJB JAR file. The tmp#####.jar is the CMP EJB JAR file with the newly saved changes. The tmp#####.jar can be renamed and opened in Deploytool for editing. “#####” represents a random number - i.e., tmp46278.jar.

5045659

Deploytool incorrectly sets the fetch group for BLOB/CLOB column types.

If the user selects the Sun-specific Settings button to bring up the CMP Database dialog and hasn’t specified the fetch group for BLOB/CLOB column types in the sun-cmp-mappings.xml file, the fetch group for the BLOB/CLOB column types is incorrectly set to Default.

Solution

Set the BLOB/CLOB type column fetch group to None.

1.  Click on the Sun-specific Settings button in the EJB JAR General tab.

2.  For each Enterprise Bean that has “BLOB” or “CLOB” listed under the Type column in the Field Mappings table, select None in the Fetch column.

3.  Close the CMP Database dialog.

4.  Save the application.

6172135

The web application used in the Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta Quick Start Guide is not marked distributable; thereby causing HTTP session persistence to not work correctly for this application.

HTTP session persistence, as described in the Test HTTP Session Persistence section of the Quick Start Guide, does not work for the web application in the install_dir/samples/quickstart directory. Because of this, the HTTP session is lost after restarting an application server instance, so the application does not display the names of users which were entered before the server was restarted.

Solution

1.  Edit the file install_dir/samples/quickstart/web/WEB-INF/web.xml to add the element distributable/ after the display-name element.

2.  Save the file.

3.  Repackage the application by executing the command install_dir/bin/asant_core from the install_dir/samples/quickstart directory.

4.  Go to the install_dir/samples/quickstart/build/assemble/war directory and redeploy the application using the command asadmin deploy --force --availabilityenabled --target FirstCluster hello.war.

5.  Follow the steps in the Quick Start Guide for restarting the cluster and web server and for testing the HTTP session persistence.

5068348

On Solaris (Intel and SPARC), HADB processes get bad priority in J2SE 1.4.

The threads running within the Java Virtual Machine get medium priority by default. This causes the Management Agent thread to fork the HADB process with nice level 10.

Solution

This problem is eliminated if running HADB on J2SE 1.5.

5071947

Old configuration objects should be deleted from the repository.

The management repository grows without bounds if the configuration objects are not deleted.

Solution

None

5072704

JGroups ExitEvent causes the Management Agent to stop.

False events make Management Agents to stop at irregular intervals.

Solution

None

5074979

On Solaris 10, BGE does not compute checksums properly for UDP/IP packets.

On Solaris 10, faulty UDP multicast hardware package checksumming on V210 and V22x systems makes the HADB Management system unstable.

Solution

Switch OFF hardware checksumming.

5075387

Error “too many transactions,” occurs during node restart/repair and the server could not accept some new transactions.

If one node goes offline and does not recover before all transaction objects are in use, new transactions are aborted with error “too many transactions.”

Solution

Get the offline host as soon as possible. If this is not possible, run the hadbm clear command.

5079499

MsgChannelImpl.close is not synchronized.

The Management Agent may stop with the following message in stdout: MsgChannelImpl.close: illegal ref count Management agent stopped. Bye.

Solution

Restart the Management Agent.

5083160

Management Agent crashes.

During hadbm create domain, extend domain, create, add nodes command execution, the Management Agent may fail with the following message:
WARNING: RpcAdapter.waitForView:ChannelClosed.
SEVERE: MA$MA ThreadGroup.uncaughtException: Terminating process.

Solution

The Management Agents have to be restarted one by one, then each command should be re-issued.

5096062

On Windows, cannot stop ma.exe with Ctrl-C.

Solution

Use the Task Manager to end the task ma.exe or close the window where the command was executed.

5097447

Garbage collection in logstore does not work.

A database with high load, and/or long-lived transactions will run out of resources in the log buffer (also called tuple log) or data devices. This situation can be identified by the following error or warning message(s) in the history file:

HADB-E-04593: No unreserved blocks on data devices.
HIGH LOAD: about to run out of tuple log space.

Log buffer, allocated in the shared memory, holds the log records of user transactions. When it is compacted, any log records belonging to active transactions are moved to “log store.” Log store resides on the node’s data device (a disk file), together with user data. Log store is compacted when a transaction terminates.

Solution

Since the compaction of log store does not work, allocate a big enough log buffer so that logstore is never needed. When increasing the logBufferSize, increase the device size as well since a node’s devices reserve 4*logBufferSize for log store. Restarting a node having HIGH LOAD problems on log buffer/device space also clears the log store.

5097485

Creating domains using 8 or more hosts may show various stability issues. The problems are mainly seen through timeouts and hangs in definedomain and create.

Solution

This is resolved in the final release.

6064932

asadmin configure-ha-cluster shows NullPointerException for HADB.

When the asadmin configure-ha-cluster command is run on hosts that have IPv6 interface, the HADB Management Agent fails and throws exceptions. HADB does not handle IPv6 and does not filter out the IPv6 interfaces before further processing.

Solution

HADB supports IPv4. Do not use IPv6 addresses.

6155745

Unable to configure-ha-cluster. Network partition and reconnect detected messages display intermittently.

When two nodes belonging to two different management domains running on the same host with the same port numbers, messages from one domain may be delivered to nodes from another domain causing confusion and unexpected behavior.

Solution

HADB instances using the same machine must use DIFFERENT port numbers. When discarding an old HADB instance do not reuse port numbers unless ALL nodes (on all machines) of the old instance have been stopped. Rebooting all machines that will be used by the new instance does not remedy the situation.

6158393

HADB problem with RedHat AS 3.0 in co-located mode under load.

HADB runs on RedHat 3.0 co-located with AS. Transactions may get aborted and affect the performance. This is caused by the excessive swapping performed by the operating system.

Solution

The problems has been partly resolved in RedHat 3.0 Update 3 Beta; however, we are still seeing both performance and stability problems.

6159633

asadmin configure-ha-cluster hangs.

When the asadmin configure-ha-cluster command is used to create or configure a highly available cluster on more than one host, the command hangs. There are no exceptions thrown from the HADB Management Agent or the Application Server.

Solution

HADB does not support heterogeneous paths across nodes in a database cluster. Make sure that the HADB server installation directory and configuration directory are the same across all participating hosts. Also, clear the repository directories before running the command again.

5064098

On Windows, application server startup fails with error: appservDAS.exe - Entry Point Not Found.

While trying to start the Application server domain, the startup cannot be initiated using the Menu Item on the Start Menu or the asadmin start-domain command.

The server startup fails after displaying the following dialog box:

The procedure entry point PK11_DestryPBEParas could not be located in the dynamic link library nss3.dll
The procedure entry point SECKEY_PublicKeyStrengthInBits could not be located in dynamic link library nss3.dll

Solution

The problem is caused by presence of an older version of libnspr4.dll in Windows system location (for example, C:\WINDOWS\System32). In general, this file is left behind by older versions of the Sun Java System Web Server even after uninstallation. Rename the file to some other name to workaround this application server startup problem.

6165358

Synchronization file locking problem when starting the same instance without stopping it first.

When creating an instance and starting it, if the start-instance command is executed again, and subsequent start-instance commands return success while the list-instances command reports that the instance is not running. The instance is in fact running, however, when attempting to stop it an exception is thrown.

Solution

Stop the instance prior to starting the instance again. If the instance is still running, kill the instance then start the instance again.

6165818

The load balancer plug-in (XML) does not have context root entry for the .ear file.

If an application/module contains an alternate DTD file for one of its deployment descriptors, the loadbalancer.xml entry for that web module will not be generated.

Solution

Manually edit the web module elements that contain alternate deployment descriptors.

6170431

Load balancer not working if target server (also endpoint) is down before the AppClient comes up.

To enable load balancing, you must specify the endpoints in the following system property: com.sun.appserv.iiop.endpoints. For application clients, the endpoints list needs to be specified in the sun-acc.xml file. The target-server element in the sun-acc.xml file is of no consequence once the endpoints are specified. However, if the target-server element is specified as an endpoint and if it is down before the Application Client is started, the client fails.

Solution

The target-server element should not be down before the App Client starts.

6170584

A timing issue while loading physical destinations when a Message Queue broker in the cluster fails.

If there are many brokers in the cluster and queues are administratively created using maxNumConsumers=-1, these queues are accessed by both the client applications and the MDB. Kill and bring back one broker at a time and repeat 2-3 times.

While a killed broker is brought back, it loads the destinations that are created earlier. Before that point, if one of the JMS clients accesses that destination, the broker auto-creates that destination. Since the destination is automatically created, it looses its original properties.

Solution

Start the Message Queue broker with the following arguments so that the automatic creation of the destinations is turned off:

-Dimq.autocreate.queue=false -Dimq.autocreate.topic=false

6171512

MDB undeployment/appserver shutdown sometimes hangs after a connection to Message Queue cluster reconnects.

Solution

When the Application Server shutdown or MDB undeployment hangs, kill the Application Server process so that the node agent can bring it back up again.

6165344

On Enterprise Edition, dynamic reconfiguration on monitoring level change does not happen on the instance other than the Domain Administration Server.

Monitoring configuration works only for the Domain Administration Server instance. Monitoring on instances other than DAS happens only after the instance is restarted.

Solution

Restart the instance before reconfiguring the monitoring level.

6158411

The delete-resource-adapter-config command fails to delete the resource-adapter-config when the resource adapter configuration was created using resources_xml file.

Solution

Create the resource-adapter-config using the create-resource-adapter-config command instead of using the XML resource file. Once a resource-adapter-config is created this way, it can be deleted using the delete-resource-adapter-config command.

6159619

On Windows, CTS servlet/sepc/requestmap/URLClient.java#longestPathMatchTest2 fails.

If the user defines two URIs (servlet mappings) differing in case alone, they are treated as the same on Windows.

Solution

Users should not differentiate URI definitions based on case alone.

6157205

Certification Migration for 7.x Enterprise Edition not working.

When running the Upgrade utility and selecting the security certificate to migrate, the following problem is encountered:

libsmine3.so: version “NSS_3.4 not found.

Solution

Skip the certificate migration option when upgrading.

6157425

Failed to create a new instance in 7.x Enterprise Edition.

If Server 7.x Enterprise Edition has two instances (server1:7070, server2:7071), server2 is not converted correctly to the Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta.

Solution

This issue will be resolved in the final release of the Application Server Enterprise Edition 8 2004Q4 product.

6165528

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 or Standard Edition 8 2004Q4 Beta.

When running the Upgrade Utility and identifying the install_dir as the source installation directory, the upgrade process upgrades only those domains that are created under install_dir/domains directory. Domains created in other locations are not upgraded.

Solution

Before starting the upgrade process, copy all the domain directories from their different locations to the install_dir/domains directory.

6165505

servletRequest.getlocalName returns an IP address instead of a DNS name.

If a request has a servlet that makes the servletRequest.getlocalName method call, an IP address is returned.

Solution

There is no known workaround for this issue.

6116887

Cannot start domain as user different from install.

After installing the Application Server as root user and creating a domain using the create-domain command, the domain gets created, but starting the domain fails and the following error is logged:

{#|2004-07-23T21:21:34.351-0700|ALERT|sun-appserver-ee8.1|javax.enterprise.system.container.web|_ThreadID=10;|HTTP Service: security (27699) : CORE3259: Temporary directory /opt/SUNWappserver/temp (specified by the TempDir magnus.conf directive) is not owned by the server user. Please change TempDir or remove the directory and restart the server.|#]

Solution

Under the http-service element in the domain.xml (pertaining to the domain that is newly created), set the TempDir property to some location that the domain creator owns. For example:

<property name=”TempDir” value=”/home/kmeduri/ASDomains/domains/mydomain/temp” />

6155216

Different return values of javax.servlet.http.HttpServletRequest getHeader() and getHeaders() on Sun Java System Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.

Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta aggregates several HTTP request headers of the same name into a single HTTP request header with a comma-separated list of header values. Sun Java System Application Server Platform Edition 8 2004Q4 Beta does not perform this type of header aggregation.

This means that in Sun Java System Application Server Platform Edition 8 2004Q4 Beta, HTTP request headers with the same name are represented as individual items in the enumeration returned by javax.servlet.http.HttpServletRequest.getHeaders, whereas in Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta they are represented as a single enumeration item with their header values separated by comma.

Likewise, in Sun Java System Application Server Enterprise Edition 8 2004Q4 Beta javax.servlet.http.HttpServletRequest.getHeaders always returns the aggregated header values (separated by comma) if the HTTP request contains multiple headers with the specified name, whereas in Sun Java System Application Server Platform Edition 8 2004Q4 Beta, this method returns the first header in the request if there are multiple headers with the specified name in the request.

Either behavior is conformant with the HTTP 1.1 Specification (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).

6159663

Case differences in HTTP response header names between Sun Java System Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.

If a servlet developer adds an HTTP response header to the HTTP response, by calling one of the addXXXHeader() methods on javax.servlet.http.HttpServletResponse, the header name in the HTTP response returned to the client will differ in case between the Application Server Platform Edition 8 Beta and Enterprise Edition 8 Beta.

While Application Server Platform Edition 8 preserves the case of the HTTP response header named provided to addXXXHeader(), the Application Server Enterprise Edition 8 converts the first character to uppercase, and converts all remaining characters to lower case.

Notice that either behavior is compliant with the HTTP 1.1 specification which declares header names to be case-insensitive (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).

The same is true for all response headers added by the web container itself. For example, the standard “X-Powered-By” response header will be returned as “X-Powered-By” on the Sun Java System Application Server Platform Edition 8, and will be returned as “X-powered-by” on the Sun Java System Application Server Enterprise Edition 8.

Solution

Have the HTTP client perform s case-insensitive search for header names in the HTTP response.

none

Web container performance is sub-optimal for the beta release.

The web container performance is slow.

Solution

The final release will resolve this issue.