This document contains Release Notes for WebSphere Application Server - Express Version 5.1.1.x for iSeries. The Release Notes contain information about known problems and the work arounds. This document also includes some supplemental information for topics covered in the WebSphere Application Server - Express documentation. This version replaces all earlier versions of the release notes.
These notes will be updated periodically. Please see the WebSphere Application Server - Express for i5/OS Web site for the most up-to-date information.
When troubleshooting, be sure to search the WebSphere Application Server - Express for i5/OS Frequently Asked Questions (FAQ) database.
Several features have been deprecated in Version 5.1. The Deprecated Version 5.1 features document in the Version 5.1 InfoCenter describes these deprecated features.
See the Installation documentation for the most up-to-date, step-by-step instructions on installing the product and creating the initial configuration.
Table of Contents
 What's New
Documentation
Fix Warning
PTF Information
Known Problems and Restrictions
WebSphere Application Server - Express, Version 5.1.1 provides the following new features and updates:
- Support of the Mozilla 1.x browser for use with administrative console and Samples applications.
- Support of the client application for a Linux PowerPC platform on WebSphere Application Server - Express for i5/OS.
- Web Services Client was updated to support HTTP 1.1.
- Client Cache was added to Web Services.
-
The ability to detect hung threads in J2EE applications. When WebSphere Application Server - Express detects that a thread has been active longer than the time defined by the thread monitor threshold, the application server will:
- Log a warning in the WebSphere Application Server - Express System.Out log file.
- Issues a Java Management Extensions (JMX) notification that enables third-party tools to catch the event and take appropriate action, such as issuing an electronic page or e-mail.
- Triggers changes in the performance monitoring infrastructure (PMI) data counters.
- A feature has been added to aid in debugging scenarios where sessions are accidentally swapped between users (known as session crossover). Please refer to the documentation for details on enabling this feature.
- With Version 5.1.1, WebSphere Application Server - Express Security now supports Lotus Domino Enterprise Server 6.5.1 (for Single Sign-on, LDAP server, etc). New security features for v5.1.1 include:
|
|
|
The most up-to-date documentation can be found on the WebSphere Application Server - Express for i5/OS Web site documentation page.
The WebSphere Application Server - Express for i5/OS and i5/OS Information Center is now available for download from the WebSphere Application Server - Express for i5/OS Web site. This downloadable version can be installed and viewed on a local system rather than remotely from the WebSphere Application Server - Express for i5/OS Web site.
The following instructions describe how to download and install the WebSphere Application Server - Express for i5/OS and i5/OS Information Center:
- Download the zip file for the Information Center from the Documentation page on the WebSphere Application Server - Express for i5/OS Web site.
- Create a new directory, called WASE51Docs, on the local system.
- Extract the contents of the downloaded zip file to this new directory.
You can access the WebSphere Application Server - Express for i5/OS and i5/OS Information Center by opening the index.htm page in the documentation subdirectory in a browser:
<install_drive>\WASE51Docs\index.htm
The WebSphere Application Server - Express - Support Web site provides individual fixes for critical problems that are not part of a WebSphere Fix Pack. These fixes have not been tested against WebSphere Application Server - Express Version 5.1 for iSeries. Unless otherwise noted, these fixes should not be applied to your iSeries server. These fixes will be included in official fix packs for the product.
If you have a critical requirement for a fix, please contact IBM Service.
After you install the WebSphere Application Server - Express Version 5.1 product, you should install the WebSphere Application Server - Express Group PTF (program temporary fix) for your OS/400 release. The Group PTF contains necessary fixes for WebSphere Application Server - Express, IBM Developer Kit for Java, DB2 Universal Database (UDB), and IBM HTTP Server (powered by Apache) products.
These release notes assume that you have applied the WebSphere Application Server - Express Version 5.1.1 Group PTF to your iSeries server.
-
Group PTFs SF99273 (V5R1), SF99274 (V5R2), and SF99275 (i5/OS V5R3) are available. The preferred time to apply them is after installing WebSphere Application Server Version 5.1 for iSeries and preferably before the WebSphere Application Server - Express environment is first started or any additional WebSphere instances are created.
-
PTF requirements for WebSphere Application Server - Express Version 5.1 for iSeries are posted to the product Web site:
Check this site often to verify that you are running the product with the latest required PTFs.
Installation Instructions for WebSphere Application Server - Express for i5/OS V5.1.1 Group PTF
The following instructions describe how to install the V5.1.1 group PTF:
|
|
|
- The integrated GUI cannot be used to administer an application server that is also being managed concurrently with the wsadmin utility or the administrative console.
- The name 'server1' is not allowed for a WebSphere - Express Application Server instance. Applications will not install properly into an Express server named 'server1'.
|
|
|
|
|
- The heap size values and descriptions in the Java Virtual Machine of the Process Definition of an Application Server are misleading or incorrect:
- The default value of 0 for the Initial Heap Size field will result in an actual initial (or minimum) heap size of 96 on OS/400. The help that says the default is 64 for OS/400 is incorrect.
- The default value of 0 for the Maximum Heap Size field will result in an actual maximum heap size of 0 (or *NOMAX) on OS/400. The field description that says "The default is 256." is incorrect for OS/400.
- The following AdminApp commands are not supported in wsadmin when it is attached to a remote server process:
- install
- installInteractive
- The administrative console help text provides information about features and functions that are not supported by WebSphere Application Server - Express. For example, EJB help documentation is provided, but not supported by WebSphere Application Server - Express.
- Using a WebSphere Application Server, Version 5.0.2 or later wsadmin scripting client to connect to a Version 5.0.2 or later server to create or update the native type configuration data Symptom This note documents a restriction using a WebSphere Application Server Version 5 or Version 5.0.1 wsadmin scripting client, to connect to a Version 5.0.2 or later server. Exception occurs when you create or modify configuration attribute that uses Java native type. The following exception occurs when you update a boolean type attribute:
WASX7015E: Exception running command: "$AdminConfig modify $targetMappings {{enable false}}"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7239E: Unexpected error setting attribute "enable" of type "boolean" to value "false." Additional information may be found in the trace log
The reason for this exception is that certain WebSphere Application Server, Version 5.0.2 or later configuration data use Java native types that are not recognized by a WebSphere Application Server, Version 5 or Version 5.0.1 wsadmin scripting client. The known Java native types include boolean, int, and long. Recommended response To work around this problem, use a WebSphere Application Server, Version 5.0.2 or later wsadmin scripting client to connect to a Version 5.0.2 or later server to create or update the native type configuration data.
- Version 5.1.1.2 Only When installing an application using the admin console and the 'Server Path:' is specified for the application, the application EAR or WAR file will be deleted from it's original location, if the following conditions are true:
- The Application Server's "run as user" profile, which defaults to QEJBSVR, owns the EAR/WAR
file, has object existence (*OBJEXIST) authority to the EAR/WAR file, and *WX authority to
the directory where EAR/WAR file is located.
This doesn't affect applications in /QIBM/ProdData/WebAS51/<Edition>/installableApps directory, as QEJBSVR does not have authority to delete them
- The name 'server1' is not allowed for a WebSphere - Express Application Server instance. Applications will not install properly into an Express server named 'server1'.
- The WebSphere Application Server - Express only supports one application server per server instance. Note that you can create multiple server instances, each running one application server.
|
|
|
|
|
-
Caching of connection handles across servlet methods is limited to Java Database Connectivity (JDBC) and Java Message Service (JMS) resources. Other non-relational resources, such as Customer Information Control System (CICS) or IMS, currently cannot have their connection handles cached in a servlet. This limitation only applies to single-threaded servlets because multi-threaded servlets do not allow caching of connection handles.
To work around this problem, you need to get, use, and close the connection handle within each method invocation.
-
When you create a data source of DB2 Universal Java Database Connectivity (JDBC) driver and set the driverType property to 4, you must provide the serverName property. If you do not provide the serverName property, DB2 throws a NullPointerException instead of an exception with meaningful message.
-
Starting with WebSphere Application Server - Express Version 5.1, the administrative console no longer displays any deprecated JDBC Provider names. The new providers differ only in names from the old deprecated ones. The new providers are more descriptive and less confusing.
The deprecated JDBC Provider names continue to exist in the jdbc-resource-provider-templates.xml file for migration reasons, for example, for the existing Jacl scripts. However, you can use the new and more descriptive JDBC Provider names in the Jacl scripts.
|
|
|
-
While debugging JavaServer Pages (JSP), WebSphere Application Server can issue a NullPointerException exception in the JavaScript code using Bean Scripting Framework (BSF). The servlet engine fails with a double open on a reader or writer stream.
The Java servlet application programming interface (API) does not define behavior upon reopen in a reader or writer stream. Stop and restart WebSphere Application Server - Express before debugging to verify that a clean instance of WebSphere Application Server - Express is running.
Note: The JSP debugging function of BSF is deprecated in WebSphere Application Server - Express Version 5.1.
|
|
|
|
|
-
A WebServicesFault exception is thrown by the application server runtime for certain Web Services Description Language (WSDL) files that define operations with the document style and literal use and use the Simple Object Access Protocol (SOAP) header to transmit the input data.
If the WSDL files define an operation with document style and literal use and this operation maps the input to the SOAP header, the Web services runtime fails to find the right operation for the target service, and a WebServicesFault exception is thrown.
To solve the problem, you must change the WSDL files so that the previously noted operation does not have any input that uses the SOAP header to transmit the data.
-
When hosting Web services on WebSphere Application Server, you can receive the following exception:
java.lang.SocketTimeOutException: Read Timed Out
A slow network connection between the client and the Web service causes this problem. In such cases, the HTTP socket may timeout before the Web service engine completely reads the Simple Object Access Protocol (SOAP) request. Sudden increases in overall network activity cause this problem in most cases. Or, when the client is accessing the Web services from a slow network connection, the problem occurs. It can also occur in cases where the amount of data in the SOAP request is very large.
Increase the ConnectionIOTimeOut parameter for your Web container HTTP transport. The default value is 5 seconds. You can increase the value to 30 seconds or greater.
You can reset the value using the administrative console by clicking Servers --> Application Servers --> server_name --> Web Container --> HTTP Transports --> port_number --> Custom Properties --> New.
Enter the following property name and value:
- Name:
ConnectionIOTimeOut
- Value:
30
|
|
|
|
|
-
Communication between the HTTP server plug-in and WebSphere Application Server - Express can be done through either HTTP or HTTPS. The additional products that are necessary to run HTTPS may or may not already be installed on the iSeries.
If the following message appears in the HTTP server job log, the WebSphere HTTP server plug-in detected that it is configured to use HTTPS when communicating with the application server, but the required products for HTTPS communication are not installed on the iSeries.
Joblog message:
Plugin will continue to startup, however, SSL transport did not initilize.
Secure communication between app server and plugin will NOT occur.
To run with SSL, additional products may need to be installed:
1) OS/400 Digital Certificate Manager (5722-SS1 or 5769-SS1, option 34)
2) Cryptographic Access Provider 5769-AC1 (40-bit), 5722-AC2 or 5769-AC2
(56-bit), 5722-AC3 or 5769-AC3 (128-bit)
- Triplet characters (such as %20 etc...) within a Location header query string may not be converted correctly. If you encounter a problem, apply the following HTTP Server PTF:
V5R2 5722DG1 SI13564
V5R3 5722DG1 SI14243
In addition, If your HTTP server is running as a single byte language such as 37 or 819 then also specify DefaultNetCCSID 1208 directive in your HTTP server configuration.
|
|
|
-
If you are accessing Domino data from your WebSphere - Express applications and need NCSO.JAR in your classpath, you may have to point to it in a different place after upgrading Domino to version 6.5 or 6.0.3 or later versions. The prior Domino releases had NCSO.JAR in /QIBM/ProdData/lotus/notes/shared, which is being removed in the 6.0.3 and 6.5 releases of Domino.
Beginning with Domino versions 6.0.3 and 6.5, you should use /QIBM/ProdData/Lotus/Notes/DATA/Domino/Java/NCSO.JAR or instance_root/data/Domino/Java/NCSO.JAR (where instance_root is the root directory of the Domino server instance.
|
|
|
|
|
-
In WebSphere Application Server - Express Version 5.0.1, Version 5.0.2, and Version 5.1, the distinguished name is normalized according to the Lightweight Directory Access Protocol (LDAP) specification. In WebSphere Application Server, Version 5.0, the normalization of the distinguished name is not done. The normalization consists of removing spaces in the base distinguished name before or after commas and equal symbols.
An example of a non-normalized base distinguished name is o = ibm, c = us or o=ibm, c=us.
An example of a normalized base distinguished name is o=ibm,c=us.
It is preferred that the distinguished name is manually normalized when you enter the base distinguished name in the configuration. With WebSphere Application Server - Express Version 5.1, the normalization occurs automatically at the runtime.
When a WebSphere Application Server - Express Version 5.0.1, Version 5.0.2, or Version 5.1 system (which always has a normalized distinguished name) sends a security token to a WebSphere Application Server - Express Version 5.0 system that contains a non-normalized distinguished name, the request is rejected because of the mismatched distinguished names during authorization.
To ensure the interoperability between WebSphere Application Server - Express versions, manually normalize the base distinguished name in the LDAP configuration on a Version 5.0 system by removing all the spaces before and after the commas and equal symbols.
-
WebSphere Application Server - Express goes into recursion and fails when -Djava.security.debug=all or -Djava.security.auth.debug=all is enabled. If Java 2 Security is enabled and IBM Developer Kit, Java Technology Edition, Version 1.4 Java 2 Security debug (-Djava.security.debug=all or --Djava.security.auth.debug=all or both) is enabled, a recursive loop results and eventually the WebSphere Application Server crashes with a Java core dump. This problem is recognized in the IBM Developer Kit, Java Technology Edition Version 1.4.
Do not use the IBM Developer Kit, Java Technology Edition, Version 1.4 security debug with the all or domain options until the issue in IBM Developer Kit, Java Technology Edition, Version 1.4 is addressed.
- When implementing your own custom Java classes for WebSphere security (TAI, user registry, system login modules, ..., etc), you are instructed to create directory
USER_INSTALL_ROOT/classes (where USER_INSTALL_ROOT is the root directory of your instance) and place your class files under that directory. For example, to modify the default instance with custom security classes, you would create directory /QIBM/UserData/WebAS51/Base/default/classes. However, when Java 2 Security is enabled, java.security.AccessControlException may be thrown when methods of your custom classes are invoked. Similarly, AccessControlException may be thrown if Java classes have been placed under the USER_INSTALL_ROOT/lib/ext directory.
The solution is to grant the following permissions to file USER_INSTALL_ROOT/properties/server.policy and restart the server:
grant codeBase "file:${user.install.root}/lib/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${user.install.root}/classes/-" {
permission java.security.AllPermission;
};
|
|
|
-
The help search in the administrative console does not return search results for Latin-1 terms that contain diacritical markings (for example, German für, where the u includes an umlaut). To work around this problem, use the decimal representation of the character in the search term (for example, für).
IBM, iSeries, OS/400, RS/6000, AIX, Lotus, and WebSphere are trademarks of International Business Machines Corporation in the United States and/or other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
|
