IBM WebSphere Application Server, Version 5.0.2 Release Notes

WebSphere Application Server for z/OS, Version 5.0.2

This document contains the Release Notes for IBM WebSphere Application Server, Version 5.0.2.

Documentation for Version 5.0.2

You can find the Getting started information, which includes an overview and installation instructions for IBM WebSphere Application Server, Version 5, on the product CD-ROM as a PDF file. This PDF file is provided in English only. For the latest information on installing and using the product, see the online InfoCenter located at: http://www.ibm.com/software/webservers/appserv/zos_os390/library/ .

WebSphere Application Server for z/OS Support page

To review any recommended or mandatory interim fixes for the latest release of WebSphere Application Server for z/OS, visit the WebSphere Application Server Support page at the following Web site:

http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .

From the main page, there are a variety of self-help tools available from this page, including a comprehensive APAR table that provides a listing of the available maintenance, as well as the ability to report service issues via the Web.

Known problems and workarounds

Getting started

Installation

In a warm-start scenario, verify your acceptance of the new WebSphere Application Server for z/OS v5.0 licensing terms & conditions.

A new license information document governs your use of WebSphere Application Server for z/OS V5.0 (Cumulative Fix W502000). It contains new terms and conditions related to new excluded components and new third party code contained in the program. Before executing the runtime environment, you must read and accept these additional terms, which appear in the Customization Dialog. If you do not accept the terms, the Dialog will not allow you to continue with customization. If you are warm-starting, you must also complete an additional step that proves your acceptance of the terms.

Symptom: If you are applying WebSphere Application Server for z/OS v5.0 on top of existing WebSphere Application Server for z/OS v5.0 configurations (warm-start), your server fails to start after you customize the product and you receive the following error: BBOO0270E WEBSPHERE APPLICATION SERVER FOR Z/OS LICENSING AGREEMENT NOT MET.

Problem: You will receive this error if you fail to run through the option that verifies your acceptance of the new licensing terms & conditions that appear upon invocation of the Customization Dialog, despite accepting (by specifying "Y") the terms after you initially read them.

Response: Follow these steps to run the option that verifies your acceptance of the new licensing terms & conditions:

  1. Invoke the Customization Dialog using the upgraded dialog data sets. (You will see the new licensing terms & conditions right away.)
  2. After reading the terms, you will see the acceptance prompt. Type "Y" to accept the new licensing terms & conditions. (If you do not accept the terms, customization will not continue and the code will not execute.)
  3. Once you accept, the main panel of the Dialog will appear. Select the option "Configure v5.0 License Agreement Refresher."
  4. Follow through the steps in the "Configure v5.0 License Agreement Refresher" option to generate the jobs.
  5. Follow the instructions generated from the "Configure v5.0 License Agreement Refresher" option.
  6. Repeat steps 4 and 5 for each WebSphere configuration directory (for example, /WebSphere/V5R0M0/AppServer or /WebSphere/V5R0M0/DeploymentManager), that you have configured.
  7. After you have run the license refresh process, you can start the servers at the new cumulative fix level.

Samples

A ++HOLD(ACTION) is included in the w502000 PTF that documents the updates to samples, including instructions on how the samples can and should be installed in the server.

Servers

No known issues.

Application servers

No known issues.

Object Request Brokers

No known issues.

HTTP servers

No known issues.

Applications

No known issues.

EJB modules

The batchUpdate new feature cannot work for an EJB container-managed persistence bean when it mapped to more than one table

WebSphere Application Server, Version 5.0.2 now has a new feature, batchUpdate, for EJB container-managed persistence (CMP) bean. However, the new feature cannot work for an EJB CMP bean when it mapped to more than one table. For example, when mapping inherited enterprise beans as root-leaf to a database, the subclass enterprise beans are mapped to two tables.

A single access-intent read ahead hint might not refer to the same bean type in more than one relationship

A single access-intent read ahead hint might not refer to the same bean type in more than one relationship. For example, if a Department enterprise bean has a relationship employees with the Employee enterprise bean, and also has a relationship manager with the Employee enterprise bean, then a read ahead hint cannot specify both employees and manager.

Enterprise bean deployment and Sybase IMAGE type restrictions

When deploying enterprise beans with container-managed persistence (CMP) types that are non-primitive and do not have a natural Java Database Connectivity (JDBC) mapping, the deployment tool maps the CMP type to a binary type in the database, where it is stored as a serialized instance. For Sybase, the JDBC type LONG VARBINARY is used, which the Sybase driver maps to the native type IMAGE. You cannot use VARBINARY, which has fewer restrictions than IMAGE in Sybase, because it is limited to a size of 255 bytes, which is too small for typical serialized Java objects.

The specific restrictions on the IMAGE type are:

To work around this problem, edit the EJB mappings in the WebSphere Studio Application Developer toolset and do either of the following:Refer to the WebSphere Studio Application Developer documentation for more information about using composers.

The CMP11 custom finder execution is interrupted by an exception

Symptom:

When a client executes a CMP11 custom finder returning a lazy collection or enumeration with greater than 25 elements, an internal failure can occur when WebSphere Application Server loads the 26th or higher referenced element from the database.

Problem:

The custom finder execution is interrupted by an exception similar to the following:

[6/19/03 19:43:10:345 PDT] 6d6ae585 EJSJDBCFinder E CNTR0040E: Finder failure as a resultof exception java.lang.NullPointerException
    at com.ibm.ejs.container.ContainerManagedBeanO.setCMP11LoadedForUpdate(ContainerManagedBeanO.java:262)
    at com.ibm.ejs.container.EJSHome.getBean(EJSHome.java:1463)
    ...

Description:

This failure causes a problem within the transaction the custom finder is called within, causing a transaction rollback.

Response:

To resolve this problem, apply interim fix PQ75634 that is available from the following Web site:

http://www.ibm.com/software/webservers/appserv/was/support/.

From the main page, click All code fixes and support tools in the Software downloads section. This takes you to the page to search for a specific download package.

Client modules

Install Application Client features before installing the interim fixes or the fix packs to avoid component regression problems

Problem:

When installing Application Clients V5.0.0 features from the product CD-ROM onto an existing Application Clients V5.0.x system, the installer reinstalls related components at the V5.0.0 level, which is a regression for those components back to the V5.0.0 level.

Response:

There are two possible installation states in regard to the regression problem:

IBM Software Development Kit is not upgraded successfully when you apply Application Client, Version 5.0.2 on Windows platforms

Symptom:

When you apply Application Client, Version 5.0.2 fix pack on Windows platform, one of the following errors might occur:

Problem:

IBM Software Development Kit is not upgraded successfully when you apply Application Client Version 5.0.2 fix pack on Windows platforms.

When Application Client is installed from the V5 Application Client CD-ROM, all the files in the <install_root>\java directory and its subdirectories are read-only. This causes a problem when you apply Application Client V5.0.2 fix pack. The installation of the fix pack fails or files in the <install_root>\java directory and its subdirectory are not replaced properly.

Response:

If you have Application Client V5.0.2 fix pack installed, you must first uninstall the fix pack. It is recommended that you preform the following steps before applying the Application Client V5.0.2 fix pack:

  1. Open the Command Prompt.
  2. Issue the command attrib -r <install_root>\java.
  3. Issue the command attrib -r <install_root>\java\*.* /S /D.
  4. Issue the command xcopy <cdrom>\nt\jdk\java\*.* <install_root>\java /E /Y.
  5. Apply the fix pack.

Replacing the wrong $(WAS_ROOT) value with the correct client installation root directory name

Symptom:

Wrong values are specified for the com.ibm.ssl.keyStore and com.ibm.ssl.trustStore properties in the sas.client.props files located in the client installation properties directory.

Problem:

The $(WAS_ROOT) value should be substituted with the location of the client installation root.

Response:

If the sas.client.props file contains $(WAS_ROOT) as part of the value for the com.ibm.ssl.keyStore and com.ibm.ssl.trustStore properties, edit the sas.client.props file in the properties directory and replace $(WAS_ROOT) with the following client installation root directory name:

Web services

Errors occur if you stop and restart the UDDI registry application from the administrative console and then use the user console

If you stop and restart the UDDI registry application from the administrative console, and then try to access the registry through the user console, an Error 500 - object is not an instance of a declaring class displays on the user console, and the error message SRVE0026E displays in the system log. You cannot access the UDDI registry until you restart the IBM WebSphere Application Server.

To avoid seeing this problem when you restart the UDDI registry application, perform the following steps using the IBM WebSphere Application Server administrative console:

  1. Click Applications > Enterprise Applications.
  2. In the list of applications, locate and click the UDDI application link.
  3. Scroll down to the Related Items section and click Web Modules.
  4. Click gui.war.
  5. Change the Classload Mode value to PARENT_LAST (instead of PARENT_FIRST).

An UDIN2041I error might occur with the wsadmin appserversetupuddi.jacl command

The following scripting error might display when you run the wsadmin appserversetupuddi.jacl command:

UDIN2041I: Starting UDDI application. UDIN8019E: startApplication command for appname caught exception Exc. Values are: appname=UDDIRegistry, Exc=com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke  

During installation, if you see the previous error after running the appserversetupuddi.jacl command, you can ignore the error. It is recommended that you start, or stop and restart the application server and then continue.

The Web services Gateway technology preview is not supported on WebSphere Application Server, Version 5.0.2

The Web services technology preview is not supported on WebSphere Application Server, Version 5.0.2. WebSphere Application Server, Version 5.0.2 includes Web services support that supersedes the Web services technology preview

Web services gateway technology preview: known restrictions

The Web services gateway provided with WebSphere Application Server Version 5.0.2 for z/OS is a technology preview. It is not intended for production use, and is subject to the following known restrictions:

A Java API XML-based remote procedure call Simple Object Access Protocol handler is unable to access EJB container resources

Symptom:

A Java API XML-based remote procedure call (JAXRPC) Simple Object Access Protocol (SOAP) handler deployed on the server-side to an EJB-based Web service is unable to access the resources of the EJB container. A JAXRPC SOAP handler does not execute in the EJB container.

Problem:

A JAXRPC SOAP handler executes in the Java 2 Platform, Enterprise Edition (J2EE) 1.3 Web container of a router-module. The router module directs the SOAP request to the target enterprise bean. The environment of the router module container is visible to the handler, while the environment of the EJB container is not visible. This lack of visibility might cause unexpected and possibly misleading results to handlers accessing the container environment.

Response:

J2EE 1.3 does not require the execution of Web services JAXRPC SOAP handlers in an EJB container. J2EE 1.4 requires handlers to execute in the context of the target EJB container.

The messages that display are always in English regardless of the locale when the wsdeploy tool is run

Symptom:

The messages that display are always in English regardless of the locale when the wsdeploy tool is run.

Problem:

The translated messages are not available when the wsdeploy tool is run.

Response:

Consult the articles for the wsdeploy tool in the InfoCenter for the usage and message information. The information in the InfoCenter is translated.

A Web Services Description Language file containing a Java Message Service endpoint URL fails the validation in the Web Services Description Language validator inside WebSphere Studio Application Developer

Symptom:

A Web Services Description Language (WSDL) file containing a Java Message Service (JMS) endpoint URL fails the validation in the WSDL validator inside WebSphere Studio Application Developer.

Problem:

If the JMS endpoint URL contains vertical bar ("|") characters as the property delimiters within the URL string, the WSDL validator treats the WebSphere Studio Application Developer document as invalid. The following example illustrates such a URL string:

jms:/queue?destination=jms/Q1|connectionFactory=jms/QCF1|targetService=Method1

The error occurs because the WSDL validator does not treat the "|" character as a valid delimiter within the URL string.

Response:

To avoid this error, use the ampersand ("&") character as the property delimiter within the JMS URL string. For example:

jms:/queue?destination=jms/Q1&connectionFactory=jms/QCF1&targetService=Method1

The following list describes the ways in which the JMS endpoint URL string is entered into the WSDL document :

Editing the HTTP basic authentication and Secure Sockets Layer configuration for the Web or EJB modules

Description:

You need to edit the HTTP basic authentication (user ID and password) and Secure Sockets Layer (SSL) configuration for the HTTP outbound request in the client security bindings of the Web services using the administrative console after you deploy the Web services application.

Response:

You can edit the HTTP basic authentication and SSL configuration for the Web services from the administrative console by performing the following steps:

  1. Click Enterprise Applications > application_name.
  2. Under Related Items, click Web Module or EJB Module > URI_file_name > Web Services: Client Security Bindings.
  3. Once the page is opened, look for HTTP Basic Authentication and HTTP SSL Configuration to the right.
  4. To configure the HTTP basic authentication, click edit and enter the user ID and password.
  5. Click OK.
  6. To configure the HTTP SSL configuration, click edit.
  7. Select HTTP SSL Enabled.
  8. Select a SSL alias for the HTTP SSL configuration.
  9. Click OK.

Migrating applications developed with the WebSphere Application Server, Version 5 Web services technology preview to WebSphere Application Server Version 5.0.2

Problem:

Migrating applications developed with the WebSphere Application Server, Version 5 Web services technology preview to WebSphere Application Server Version 5.0.2.

Response:

This section describes how to migrate from the Web services technology preview to WebSphere Application Server, Version 5.0.2.

You can normally reuse the Web Services Description Language (WSDL) file. If you created the WSDL file using the Java2WSDL command in the Web services technology preview and you encounter problems, regenerate the file. You must regenerate all Java classes generated by the WSDL2Java command in the technology preview. These classes fall into two categories, the development classes and the deployment classes. The development classes include the enterprise beans and exception classes generated by the WSDL2Java command. These classes are regenerated by running the wsdl2java -role develop-client (or -role develop-server) command. The deployment classes include *Stub.java, *Locator.java, *_Ser.java, *_Deser.java, and *_Helper.java classes. After you verify that no deployment class source code is included in the application EAR file, you can regenerate the deployment classes either by using the wsdeploy command, or by selecting Deploy Web Services on the application installation panels of the administrative console. Classes generated by the WSDL2Java command are identified by a comment at the top of the source file. You can reuse the original Web service client code and server implementation code. If you have any JAX-RPC handlers, rewrite the code to conform with SAAJ 1.1 (see http://java.sun.com/xml/saaj/ ). You can reuse the original webservices.xml and webservicesclient.xml deployment descriptors. Any information added to the original ibm-webservices-bnd.xml and ibm-webservicesclient-bnd.xml files need to be migrated to the new ibm-webservices-bnd.xmi and ibm-webservicesclient-bnd.xmi files.

In the Web services technology preview, all application exceptions extended IBM WebServicesFault. Now all application exceptions extend java.lang.Exception to comply with the J2EE specification.

A WebServicesFault exception is thrown by the application server run time for certain Web Services Description Language files

Symptom:

A WebServicesFault exception is thrown by the application server run time for certain Web Services Description Language (WSDL) files that defines 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 run time fails to find the right operation for the target service and a WebServicesFault exception is thrown.

Response:

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.

Assembly tools

All platforms

Help files are viewable only from a locally installed browser

If you access any of the IBM WebSphere Application Server tools from a remote machine, for example, the Application Assembly Tool, the remote browser cannot display the help files. You can only view the help files from a locally installed browser.

To work around this problem, close all the Netscape sessions on the remote machine and click Help. A new Netscape session starts and you can then view the Help files.

Application Assembly Tool displays unsupported type for application client resource reference

When configuring a resource reference for an application client module in the Application Assembly Tool, the Type field menu lists javax.resource.cci.ConnectionFactory as an available resource reference. This type is not supported by the J2EE application client run time. The supported types are:

The EJB application using container-managed persistence beans might fail to run with the sql syntax

Symptom:

The EJB application using container-managed persistence beans might fail to run with the sql syntax. This is an Oracle syntax error dealing with an SQL CAST operation. You can see the following exception in the system:

log java.sql.SQLException: ORA-00910:specified length too long for its datatype

Problem:

The problem is a bug in the EJBDeploy program.

Description:

An incorrect CAST operator is generated into SQL for EJB entity beans. This happens when there are multiple EJB-RDB mappings in the EJB or JAR file and one of the mappings is for DB2 and another of the mappings is for another database such as Oracle. When there are multiple mappings, the EJBDeploy tool incorrectly assumes that all mappings are for DB2 and generates incorrect sql for the Oracle case.

Response:

You can work around the problem by removing the unused mappings for the EJB or JAR file.

J2EE resources

All platforms

Misleading scope when installing RAR file at the server level

When installing a RAR file, by clicking Resources > Resource Adapters > Install RAR, the scope you define on the Resource Adapters page has no effect on where the RAR file gets installed. You can only install RAR files at the node level. The scope on the Install RAR page determines the node to install. However, the scope you set on the resource adapters panel determines the scope of the new Resource Adapters, which you can install at the server, node, or cell level.

Selecting the Java Messaging Service resources when deploying the WAR file

When you deploy a WAR file and select the Java Message Service (JMS) resources that you defined, you receive a warning message without selecting the JMS resources.

Information you should know about using server-side and client-side selectors

The default behavior for the internal JMS broker is to use server-side selectors. The default behavior for external brokers is to use client-side selectors. The reason for the latter is that not all brokers support server-side filtering. Those that do, are not all JMS compliant in their implementation process.

Component-managed authentication alias not specified

When using Java Message Service (JMS), informational messages similar to the following can occur:

[10/31/02 9:13:20:438 EST] 6a55451c ConnectionFac I J2CA0107I: Component-managed authentication

If the named connection factory ends in JMSManagedConnection@nnnn, where nnnn is a multi-digit number, the informational message can be ignored. A connection factory with this type of name is created internally by the JMS server and does not require a component-managed authentication alias.

Limited connection caching available for servlets

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 since multithreaded 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.

Problems with Xerces versions that are not Java 2 Platform, Enterprise Edition compliant

Programs containing the Xerces parser routine that work on IBM WebSphere Application Server, Version 4.0.x might not work on IBM WebSphere Application Server, Version 5.

Versions of Xerces prior to 2.0.0, including the versions shipped with IBM WebSphere Application Server, Version 4.0.x, were not J2EE1.3 compliant. To meet J2EE1.3 certification constraints (DOM2/SAX2/JAXP1.1 (and no higher)), IBM WebSphere Application Server, Version 5 requires XML4J4.0.0 (Xerces 2.0 bug fixes).

In Xerces versions prior to 2.0.0 and Xalan versions prior to 2.2, the DOM, SAX, and JAXP APIs were bundled inside of the xerces.jar and xalan.jar files. In the most recent versions, these non-Apache XML APIs have moved into a separate JAR file in the XML common apache project. These common XML APIs are required by the specifications and contained within the IBM WebSphere Application Server, Version 5 j2ee.jar file.

The cause of the problem is that the class loader behavior mixes the classes that are required by J2EE1.3 with those of the older Xerces implementation.

To work around this problem, use the version that ships with IBM WebSphere Application Server, Version 5.

Messaging and Extended Messaging

No known issues.

Data access

Databases-DB2

No CLOB data is inserted into the database when you use the DB2 UDB V7.2 FP7 client to connect to a DB2 on the z/OS database

Symptom:

No CLOB data is inserted into the database when using the DB2 UDB V7.2 FP7 client to connect to a DB2 on z/OS database.

Problem:

This problem happens because of an error in the DB2 UDB Connect code. Instead of inserting the CLOB data into the column, the data inserted is an empty string. The problem is fixed in DB2 UDB V7.2 FP8 or FP9. It is also fixed in DB2 UDB V8.1.

Response:

Update to the correct version of DB2 UDB FP to resolve this problem.

An error is thrown if you use the ws_ant command to perform the database customization for Structured Query Language in Java on HP platforms

Symptom:

If you use the ws_ant command to perform the database customization for Structured Query Language in Java (SQLJ) on HP platforms, you can receive an error similar to the following:

[java] [ibm][db2][jcc][sqlj] 
[java] [ibm][db2][jcc][sqlj] Begin Customization
[java] [ibm][db2][jcc][sqlj] encoding not supported!!

Problem:

The cause of this error might be that your databases were created using the HP default character set. The Java Common Client (JCC) driver depends on Software Development Kit to perform the codepage conversions. However, the HP default codepage is not supported by the Software Development Kit shipped with WebSphere Application Server.

Response:

Set your LANG to the ISO locale before creating the databases. It should be similar to the following:

export LANG=en_US.iso88591 

Refer to the DB2 Tech Notes at http://www-3.ibm.com/software/data/db2/udb/ad/v8/bldg/t0004877.htm for details.

Enabling batchUpdate when running WebSphere Application Server with the DB2 Legacy CLI-based JDBC driver is ignored by the run time

Enabling batchUpdate when running WebSphere Application Server with the DB2 Legacy CLI-based JDBC driver is ignored by the WebSphere Application Server run time due to a problem in DB2 which can cause data integrity problems.

If you want to use batchUpdate for WebSphere Application Server, Version 5.0.2, run WebSphere Application Server with the DB2 Universal JDBC driver instead of the DB2 Legacy CLI-based JDBC driver.

Known limitations when you connect a DB2 8.1 client to a back level server using a DB2 XA data source

Problem:

Limitations exist when you connect a DB2 8.1 client to a back level server, for example, DB2 7.2 FP8, using a DB2 XA data source:

Response:

Upgrade the DB2 server level to the same level as the DB2 client.

Consult the document located at http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8infocenter.d2w/report?target=mainFrame&fn=r0010969.htm . The document is under the section XA-compliant transaction managers.

The WebSphere Application Server Java virtual machine crashes after you execute the force application command in the DB2 command line

Symptom:

The WebSphere Application Server Java virtual machine (JVM) crashes when you execute force application in DB2 UDB Server.

Problem:

When you use DB2 XA data source in WebSphere Application Server with DB2 UDB Server, the WebSphere Application Server JVM crashes after you execute the force application command in the DB2 command line.

If you use the DB2 Legacy CLI-based JDBC Driver Provider (XA), you can see the WebSphere Application Server JVM crash as soon as you execute the force application command. If you use the DB2 Universal JDBC Driver Provider (XA), you might or might not see the WebSphere Application Server JVM crash right after executing the force application command. However, you might see the WebSphere Application Server JVM crash later.

This problem has been reported to DB2. The APAR number is JR18535.

Upgrading DB2 V8.1 FP2 or a later version to avoid receiving an exception when the Java 2 security is enabled

Problem:

If you enable Java 2 security in WebSphere Application Server and try to use the DB2 Universal JDBC provider to connect to DB2 V8.1 FP1 or an older version, a java.security.AccessControlException exception similar to the following is thrown from the DB2 Java Combined Client (JCC) driver.

java.security.AccessControlException: access denied (java.lang.RuntimePermission 
accessClassInPackage.sun.io)
       at java.security.AccessControlContext.checkPermission(AccessControlContext.java(Comp
iled Code))
       at java.security.AccessController.checkPermission(AccessController.java(Compiled 
Code))
       at java.lang.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
       at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java(Com
piled Code))
       at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java(Compiled 
Code))
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java(Compiled Code))
       at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
       at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
       at com.ibm.db2.jcc.c.o.a(o.java:153)
       at com.ibm.db2.jcc.a.d.a(d.java:1069)
       at com.ibm.db2.jcc.a.be.a(be.java:1549)
       at com.ibm.db2.jcc.a.be.m(be.java:513)
       at com.ibm.db2.jcc.a.be.i(be.java:217)
       at com.ibm.db2.jcc.a.be.c(be.java:54)
       at com.ibm.db2.jcc.a.s.c(s.java:53)
       at com.ibm.db2.jcc.a.bq.h(bq.java:118)
       at com.ibm.db2.jcc.c.cf.i(cf.java:893)
       at com.ibm.db2.jcc.c.cg.a(cg.java:1540)
       at com.ibm.db2.jcc.c.cg.executeQuery(cg.java:312)

Problem:

This problem is due to the fact that the DB2 JCC driver does not have a doPrivileged call when it tries to load some classes.

Response:

Upgrade your DB2 server to DB2 V8.1 FP2 or a later version. If you cannot upgrade your DB2 server, grant the permission, java.lang.RuntimePermission "accessClassInPackage.sun.io", to your applications. However, the second solution is NOT recommended.

Databases-IBM Cloudscape

A NullPointerException occurs when you run WebSphere Application Server against Cloudscape (Version 5 and Version 5.1) and use callable statements

Symptom:

When running WebSphere Application Server against Cloudscape Version 5 and Version 5.1 and using callable statements, you might receive the following NullPointerException (message text in English only):

Unexpected exception ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while evaluating an expression, possible causes: not calling registerOutputParameter and calling setNull on BIT VARYING output parameter.
       at com.ibm.db2j.protocol.Database.Errors.StandardException.newException(StandardException.java:386)
       at com.ibm.db2j.protocol.Database.Errors.StandardException.unexpectedUserException(StandardException.java:567)
       at com.ibm.db2j.impl.BasicServices.ClassManager.Reflect.ReflectMethod.invoke(ReflectMethod.java:53)
       at com.ibm.db2j.impl.Database.Language.Execution.Generic.CallStatementResultSet.open(CallStatementResultSet.java:75)
       at com.ibm.db2j.impl.Database.Language.Interface.Generic.GenericPreparedStatement.execute(GenericPreparedStatement.java:351)

Problem:

This is a rare case and is usually an application error that is caused by the application not calling registerOutputParameter but calling setNull on the Bit Varying type parameter.

Response:

If you encounter this problem and use callableStatements, ensure that you call the registerOutputParameter Method.

Cannot see the descriptive error messages when running WebSphere Application Server, Version 5.0.2 against the Cloudscape Network Server or the DB2 universal driver

When running WebSphere Application Server, Version 5.0.2 against the Cloudscape Network Server or the DB2 universal driver, you cannot see the descriptive error messages from the database unless the retrieveMessagesFromServerOnGetMessage data source custom property is set to true. By default, the full message text is not returned to the client when a server-side error occurs. This property is disabled by default. See the DB2 release notes for more information on this.

Setting the driverType data source custom property to 4 when you run WebSphere Application Server, Version 5.0.2 with Cloudscape using the Network Server framework

Symptom:

When running WebSphere Application Server, Version 5.0.2 with Cloudscape using the Network Server framework, you can receive the following exception if you either forget to set the driverType data source custom property or set it to 2:

com.ibm..db2.jcc.b.SQLException: Unexpected throwable caught java.lang.UnsatisfiedLinkError:  DBConnect

Response:

To avoid receiving the exception, set the driverType data source custom property to 4.

Consult with InfoCenter articles for more information.

Cloudscape Version 5.0.x is deprecated in WebSphere Application Server, Version 5.0.2

Cloudscape Version 5.0.x is deprecated in WebSphere Application Server, Version 5.0.2 and will not be supported or shipped with any future releases of WebSphere Application Server.

Information about how to uninstall Cloudscape Version 5.1.x

You can issue the java -jar cloudscapeUninstall.jar command to unistall Cloudscape Version 5.1.x if going back to Cloudscape Version 5.0.x after installing Cloudscape Version 5.1.x. You can find the cloudscapeUninstall.jar file in the install_root/cloudscape51/Uninstaller, and the file is only created after installing Cloudscape Version 5.1.x.

See the WebSphere Application Server InfoCenter for the information on how to install Cloudscape Version 5.1. You need to be aware of the fact that after migrating your database to run with the new Cloudscape (using upgrade=true connectionAttributes) you can no longer run it with Cloudscape Version 5.0.

The administrative console displays DB2 settings instead of Cloudscape when you create a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider

Problem:

When creating a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider through the administrative console in WebSphere Application Server, Version 5.0.2, you need to be aware of the problem that the administrative console fills in the DB2 universal data sources settings by default instead of the Cloudscape Network Server ones. Those settings include:

  1. the DataStoreHelper class
  2. the data source custom properties

The incorrect settings do not include the implementation class, which is just like the DB2 Universal one.

Response:

If you want to create the Cloudscape JDBC Provider Network Server using the universal JDBC driver provider, you are required to manually modify the entries in the administrative console as follows:

  1. You should change the DataStoreHelper class to:
    com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper
  2. You only need the following custom properties:
    - driverType       4 (type 4 driver is the only valid value for Network Server)
      - serverName       server TCP/IP address or name.  required
      - databaseName     database name  (e.g. c:\mydb). required
      - retrieveMessagesFromServerOnGetMessage:  required by WAS not the database: Defaults to false by the database, but must be set to true in WAS.
    

    The following data source custom properties are optional:

    portNumber  port number where Network Server listens for connection       
     requests.  required.  (Note: by default Network Server listens on port 1527.) 
        logWriter
        traceLevel       
        traceFile
        traceFileAppend
        deferPrepares              
    Works as documented except that  the prepare on EXECUTE STATEMENT is never deferred (those are cloudscape native stuff)
     resultSetHoldability           Defaults to CLOSE_CURSORS_AT_COMMIT for    Cloudscape.  This is the only valid value for  Network Server. Use the JDBC 3.0 API's for setting holdability.
     securityMechanism           Network Server supports the following   security Mechanisms.
     com.ibm.db2.jcc.DB2BaseDataSource.CLEAR_TEXT_PASSWORD_SECURITY    -- default
     com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_PASSWORD_SECURITY 
    

Cloudscape throws an exception when you access the result set after the transaction is committed

When you run WebSphere Application Server with Cloudscape using the Cloudscape network server framework, Cloudscape throws an exception when you access the result set after the transaction is committed despite the fact that the cursor holdability is false by default.

This problem does not exist when you run in Cloudscape embedded. This problem has been reported to Cloudscape.

Ensure that your application does not rely on an exception that is thrown.

Adding quotes to the installCloudscape51.bat or installCloudscape51.sh file around the if the install_root path includes spaces

If the install_root path includes spaces, for example, c:\program files\WebSphere\AppServe, you must modify the installCloudscape51.bat or installCloudscape51.sh file to add quotes ("") around the install_root path as follows:

Security

Setting up a non-SAF registry

Setting up a non-SAF registry in an ND environment requires the addition of controller and servant region started task identities. After initial authentication is complete, secondary requests are intermittently propagating the local OS identity of the various server processes as assigned by the STARTED procedure. In order for authorization of administrative functions, those identities must be added to your configured registry, and authorized to the set of console users.

Java clients and Server-as-client (IIOP) are restricted to use LocalOS identities.

Java clients and Server-as-client (IIOP) are restricted to use LocalOS identities. A Distinguished Name may be passed as an asserted identity, and be mapped to a SAF identity. In addition, LTPA tokens are not supported as authenticators using IIOP.

Credential cache of Web of web requests and SSO tokens is currently disabled

Credential cache of Web of web requests and SSO tokens is currently disabled. LTPA tokens and userid password credentials for Web and administrative requests are valid only for the current transaction.

Changing the active user registry requires Global Security to first be disabled.

Changing the active user registry requires Global Security to first be disabled. If you have activated Global Security given one registry and wish to change the active registry, unpredictable errors occur. You must disable global security and restart the servers before changing an active registry.

Enabling SSL on the Daemon process is not separately configurable.

Enabling SSL on the Daemon process is not separately configurable. If this support is desired, the customization dialog creates an SSL Keyring for the daemon process, otherwise if Global Security is enabled, SSL initialization will be always be attempted and an error will be generated with the following message.

 ./bbossgsk.cpp+853 ... BBOO0036E FUNCTION gsk_environment_init FAILED WITH RC=202 
This message can be ignored in the Daemon process.

Application level Synctothread support is not enabled.

Application level Synctothread support is not enabled. All MVS system resource accesses (e.g., files, socket access) from WebSphere applications execute under the task level identify of the WebSphere servant region.

SSL is not available for Web Applications unless Global security is Enabled.

SSL is not available for Web Applications unless Global security is Enabled. This is inconsistent with the behavior of WebSphere on Distributed platforms. Using WebSphere Application Server for distributed platforms, Web Applications can be protected by SSL even if global security is disabled, if the SSL communications are initiated independent of J2EE security constraints. The only requirement is for an SSL repertoire configured for the WebContainer. WebSphere Application Server for z/OS initializes SSL, if and only if, Global Security is enabled.

Ensure accessibility for cells enabled to use a Customer User Registry

Caution must be used if a WebSphere Application cell is enabled for security and is configured to use a custom User Registry implementation. This requires code to be placed in a classpath accessible by the MVS controller, which is considered to be system code. It is recommended that unless trust can be established in the integrity of this code, a separate LPAR be used for WebSphere servers running in this configuration.

Secure interoperability between WebSphere Application Server, Version 5 and WebSphere Application Server, Version 5.0.2 fails when the Lightweight Directory Access Protocol base distinguished name in not correctly normalized in the WebSphere Application Server, Version 5 configuration

In WebSphere Application Server, Version 5.0.1 and Version 5.0.2, the distinguished name is normalized according to the Lightweight Directory Access Protocol (LDAP) specification. In WebSphere Application Server, Version 5, 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. In WebSphere Application Server, Version 5.0.1 and higher version, the normalization occurs automatically at the run time.

When a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 system, which always has a normalized distinguished name, sends a security token to a WebSphere Application Server, Version 5 system that contains a non-normalized distinguished name, the request is rejected due to the mismatched distinguished names during authorization. A common example of a request that fails is when a WebSphere Application Server, Version 5 node is synchronizing the configuration from a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 deployment manager. Another example is that a request fails when a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 servlet or enterprise bean makes a downstream request to a WebSphere Application Server, Version 5 enterprise bean. However, a request going from a WebSphere Application Server, Version 5 system to a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 system does not fail.

To ensure the interoperability between WebSphere Application Server, Version 5, Version 5.0.1, and Version 5.0.2, manually normalize the base distinguished name in the LDAP configuration on a WebSphere Application Server, Version 5.0 system by removing all the spaces before and after the commas and equal symbols.

A Web services security enabled application fails to start

Symptom:

A Web services security enabled application fails to start. You can receive an error message similar to the following:

[6/19/03 11:13:02:976 EDT] 421fdaa2 KeyStoreKeyLo E WSEC5156E: An exception while retrieving the key from KeyStore object: java.security.UnrecoverableKeyException: Given final block not properly padded

Problem:

The cause of the problem is that the keypass (password) provided for a particular key in a Key Store is invalid. The Key Store passwords are specified in the KeyLocators elements of the bindings file(s) (ws-security.xml, ibm-webservices-bnd.xmi or ibm-webservicesclient-bnd.xmi).

Response:

Check the keypass values for keys specified in the KeyLocators elements of the bindings file(s) and correct any that are incorrect.

Problems with the Java Message Service protocol within Web services when security is enabled

Symptom:

The following exception occurs when you are creating a URL connection using the Java Message Service (JMS) protocol within Web services when global security is enabled:

java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.sun.net.www.protocol.jms)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java(Compiled Code))
 at java.security.AccessController.checkPermission(AccessController.java(Compiled Code))
 at java.lang.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
 at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
  at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java(Compiled Code))

If this permission is granted into the was.policy file of the application, the error that occurs is a MalformedURLException.

Problem:

Some security code sets the java.protocol.handler.pkgs system property, overriding what is already specified for the JMS protocol.

Response:

You can disable the global security to avoid receiving the exception. You can also programmatically add the protocol back to the java.protocol.handler.pkgs system property by appending the following string to the end of the value already set in this system property using a | character as a delimiter:

com.ibm.ws.protocol
You must do this prior to making the Web service invocation.

A 500 type error is thrown when you click Import Keys in the Lightweight Third Party Authentication panel multiple times and save the changes each time in the administrative console

Symptom:

In the administrative console, when you click Import Keys in the Lightweight Third Party Authentication (LTPA ) panel multiple times in the same session and save it each time, the following message might be displayed on the console intermittently:

Error 500
An error occurred while processing request: /syncworkspace.do
Message: Server caught unhandled exception from servlet [action]: 
java.lang.IllegalStateException

Note: When you enter a wrong password in the LTPA panel during importing the keys and save the password, the save operation displays error messages in the WebSphere Status Window at the bottom of the administrative console. The keys are not updated in the run time and the old set of keys is used. However, the keys and the wrong password are saved in the configuration. This configuration is used during the next startup of the server(s)

Therefore, if you save a wrong password accidentally, do not restart the server(s) unless the password is changed because the server(s) can fail to start if the keys and the password do not match.

Problem:

The cause for this error is that an invalidated session is referred to under some circumstances.

Response:

To avoid receive this error, log out and log in back to the administrative console using a new window. Import the keys if necessary. If the problem persists, use the wsadmin tool.

If you enter a wrong password and save the passowrd during importing the keys, you can use the following wsadmin commands to change the password to the correct value (the keys should be saved during the save operation). Do not restart any servers unless the password is changed for each of them.

set LTPA [$AdminConfig list LTPA]

set ltpaPw theCorrectPassword

$AdminConfig modify $LTPA [list [list password $ltpaPw]]

$AdminConfig save

Web services security is not supported in a pure Java client (also known as a non-managed client)

Symptom:

Web services security is not supported in a pure Java client (also known as a non-managed client). Web services security is only supported in a managed client in Fix Pack 2.

Problem:

The Web services security constraints do not apply to the outbound client or Web services acting as the client Simple Object Access Protocol (SOAP) message if the application code does not use the Java 2 Platform, Enterprise Edition (J2EE) programming model, so the J2EE environment (including security handlers) is not available to the client. This includes Web services security. You might configure to digitally sign, encrypt, and generate the security tokens. For the outbound message for a client or Web services acting as a client, the SOAP message is not digitally signed, encrypted or the security is not token inserted into the message.

Response:

Change the application to a managed client application and use the J2EE programming model to invoke Web services.

The JavaMail-related Java 2 security exceptions might be reported in the system log file when the Web services applications run with attachments in the Simple Object Access Protocol messages

Symptom:

The following JavaMail-related Java 2 security exceptions might be reported in the system log file when the Web services applications run with attachments in the Simple Object Access Protocol (SOAP) messages.

java.security.AccessControlException: access denied (java.io.FilePermission c:\WebSphere\AppServer\java\jre\lib\javamail.providers read)
java.security.AccessControlException: access denied (java.io.FilePermission c:\WebSphere\AppServer\java\jre\lib\javamail.address.map read)

Problem:

These exceptions are benign. This is not an application or system problem because the JavaMail anticipates the exceptions and handles them appropriately. The WebSphere SecurityManager is rather verbose in logging possible violations of the Java 2 security access control exceptions.

Response:

If this situation is a problem, add the following permission settings to the <install_root>\config\cells\<node_name>\nodes\<node_name>app.policy.

The permission settings grant the permissions that the SecurityManager is falsely warning about.

permission java.io.FilePermission "${was.install.root}${/}java${/}jre${/}lib${/}javamail.providers", "read";    
permission java.io.FilePermission"${was.install.root}${/}java${/}jre${/}lib${/}javamail.address.map", "read";

For further details, consult with the InfoCenter article, "JavaMail security permissions best practices."

System administration

Issuing the addNode command can replace the plugin-cfg.xml file

After federating the Node, the addNode command backs up the plugin-cfg.xml file from the <install_root>/config/cells directory to the config/backup/base/cells directory. The addNode command in Fix Pack 2 regenerates a new plugin-cfg.xml file at the Deployment Manger and the nodeSync operation copies the files to the node level.

Empty NetworkDeploymentCell directory is left in the configuration directory

When you install IBM WebSphere Application Server, and you run addNode then removeNode, sometimes an empty NetworkDeploymentCell directory is left in the configuration directory making the wsadmin tool think there are two cells configured.

The WebSphere Application Server product cannot delete the directory because the directory is locked by another application. The most common reason for this situation is that another application uses that directory or its subdirectory as the current working directory, or another application opens a file under that directory or subdirectory. This problem is most commonly seen on Windows platforms, but it can happen on other platforms.

To work around this problem, manually delete the empty directory structure, then restart the servers that use this configuration directory.

System performance degrades when you configure the nodeagent failover with a certain script

If you configure the nodeagent failover with the script created by {intall_root/bin/startServer.sh nodeagent -script startnodeagent.sh -background script, the system performance degrades. A message similar to the following displays:

Feb 28 14:48:37 wastst12 init: Id "was" respawning too fast: disabled for 5 minutes

Configure the nodeagent failover with the script created by the {install_root} /bin/startServer.sh nodeagent -script startnodeagent.sh file to work around the problem..

Console

All platforms

Netscape browser

All platforms

Resolve the administrative console port conflict

If the administrative console port is in conflict with an application already running on the machine, you can change this port in the following files:

  • <install_root>/config/cells/<cellname>/nodes/<nodename>/servers/<servername>/server.xml
  • <install_root>/config/cells/<cellname>/virtualhosts.xml
Change all occurrences of port 9090 (or whatever port was selected during installation time in an IBM WebSphere Application Server coexistence scenario) to the desired port for the administrative console.

Alternatively, shut down the other application using this port before starting the IBM WebSphere Application Server.

Resizing the Netscape browser results in an error

If you resize your Netscape browser, you could get a Data Missing error.

The error message disappears in 60 seconds.

Resizing the Netscape browser causes an error 404 message

When connecting to the IBM WebSphere Application Server administrative console from a Netscape browser, resizing the browser can cause an error 404 message to occur. This situation occurs because the browser reloads the frame when resizing the window.

To avoid getting the error message, you can refrain from resizing the Netscape browser window, or you can connect to the IBM WebSphere Application Server administrative console using an Internet Explorer browser.

Netscape screen blanks out while using the administrative console

While working with the right-hand panel of the administrative console to do regular administrative tasks, the browser screen blanks out intermittently.

To work around this problem, do one of the following:

  • After the problem occurs, close the Netscape browser, log in again, and continue working.
  • Use the Internet Explorer browser from a Windows machine.
  • Use Netscape 7.x, Mozilla 1.x, Opera 5, or Konquerer browsers on the platform, depending on which is available. Although there is not formal support for these browsers, they have all been used successfully with the product and in many cases work better than the previous 4.7.x series of Netscape browsers.

Resizing Netscape Version 4.7 causes errors

You receive the following error messages when resizing Netscape Version 4.7:

Error 0
  An error occurred while processing request: http://localhost:9090/admin/upload.do

  message:

  Details
  com.ibm.webshpere.servlet.error.ServletErrorReport:
         at java.lang.Class.newInstance0(Native Method)
         ... 

After resizing Netscape 4.7, Netscape has to reload the page just as it initially loads the page on the first request. For pages that do not expect POST data, it is not a problem. But for pages that do, Netscape 4.7 cannot retain the data.

Netscape browser displays ---???--- instead of a blank line for the drop down lists

Symptom:

If you use the Netscape browser to access the Web Services Security GUI panels, the drop down lists which are supposed to contain a blank line display "---???---" instead of the blank line.

Problem:

This is because Netscape Version 4.79 does not properly interpret "" or " " as a blank.

Description

This is in the signature method(), digest method(), canonicalization method() drop downs, and others when Netscape 4.79 is used to access the panels on an AIX system. This problem does not occur when you use Internet Explorer, which properly displays a blank line.

Response

There is no workaround if you use Netscape 4.79, which is the supported level of Netscape for this release.

Scripting

Commands testConnection and getPropertiesForDataSource are deprecated

Problem:

This note documents two commands as deprecated. The two commands are testConnection and getPropertiesForDataSource commands in the AdminControl scripting object.

Description:

$AdminControl TestConnection configId props

This command is deprecated.

This command might give false results and does not work when connected to a nodeagent. As of WebSphere Application Server, Version 5.0.2, the preferred way to test a data source connection is the testConnection command passing in the data source configuration ID as the only parameter.

Running this command in WebSphere Application Server, Version 5.0.2 returns the following message:

WASX7390E: Operation not supported - testConnection command with config id
and properties arguments is not supported. Use testConnection command with
config id argument only.

$AdminControl getPropertiesForDataSource configId

This command is deprecated and there is no replacement.

This command incorrectly assumes the availability of the configuration service when you run it in the connected mode.

Running this command in WebSphere Application Server, Version 5.0.2 returns the following message:

WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.

Using a WebSphere Application Server, Version 5.0.2 wsadmin scripting client to connect to a Version 5.0.2 server to create or update the native type configuration data

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

Symptom:

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.

Problem:

The reason for this exception is that certain WebSphere Application Server, Version 5.0.2 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.

Response:

To work around this problem, use a WebSphere Application Server, Version 5.0.2 wsadmin scripting client to connect to a Version 5.0.2 server to create or update the native type configuration data.

Performance data and tools

Editing the plugin-cfg.xml file and changing the value of the ESIEnable variable

For performance purposes, edit the plugin-cfg.xml file and change the value of the ESIEnable variable, if it exists, from false to true.

<Property Name="ESIEnable" Value="true"/>

Setting the maximum pool size to the advised value and set the minimum pool size to half of the advised value

Symptom:

The Tivoli Performance Viewer (TPV) Advisor and the Runtime Performance Advisor (RPA) might issue a message telling you to change the thread pool size, without specifying whether to change the minimum or maximum size. An example of such a message is Tune 0202W: Increasing the ORB thread pool to 1 may improve performance.

Problem:

The rule does not specify whether to change the minimum or maximum size of the thread pool

Response:

You should set the maximum pool size to the advised value and set the minimum pool size to half of the advised value.

The prepared statement recommendation might be too large

Symptom:

The Tivoli Performance Viewer (TPV) Advisor or the Runtime Performance Advisor (RPA) issues advice telling you to increase the size of the prepared statement cache to an unreasonably large value, for example, 3000. On some systems this can cause a system crash or out of memory error.

Problem:

If the application has a very large number of prepared statements that are all consistently used, there are a lot of discards from the cache. The advisors see the number of discards from the cache and recommend increasing the size of the prepared statement cache. The advisors do not currently take into account the memory resources used by the prepared statement cache entries.

Response:

You should not increase the prepared statement cache above 1000 unless you are sure that you have appropriate resources.

Tivoli Performance Viewer cannot connect to a running server if security is enabled

Symptom:

Tivoli Performance Viewer (TPV) cannot connect to a running WebSphere Application Server. The SystemOut.log file of the server located at the $install_root/logs/<servername> directory might display errors similar to the following:

SECJ0305I: Role based authorization check failed for security name <null>, accessId 
no_cred_no_access_id while invoking method.

Problem:

If security is enabled in WebSphere Application Server, Version 5, TPV cannot connect to the server if the proper user login and password are not set in the Simple Object Access Protocol (SOAP) properties file.

Response:

Set the user name and password in the soap.client.props file located at the $install_root/properties directory. You should set the values for the keys com.ibm.SOAP.loginUserid and com.ibm.SOAP.loginPassword. You can find more information by searching the article, "Running your monitoring applications with security enabled" in the WebSphere Application Server, Version 5 InfoCenter.

Tivoli Performance Viewer cannot set all Performance Monitoring Infrastructure levels to None if the Runtime Performance Advisor is enabled

Symptom:

When trying to set the monitoring level for a Performance Monitoring Infrastructure (PMI) module to None through Tivoli Performance Viewer (TPV), you can find that the monitoring level for the module continually reverts back to High.

Problem:

If the Runtime Performance Advisor (RPA) is enabled on the server, it sets the monitoring level for PMI modules back to High. This behavior is by design, since the RPA requires data for certain modules.

Ignoring the NotSerializableException when setting a servlet session manager Performance Monitoring Infrastructure module to level maximum

Symptom:

When setting a servlet session manager Performance Monitoring Infrastructure (PMI) module to level maximum (or enabling session object advisor rule), you can receive a message similar to the following:

"SessionContex E Exception is: java.io.NotSerializableException: ....."

Response:

The session manager throws this exception when a declared serializable object in the session is not serializable. From PMI usage only, you can ignore the exception. However, if the exception object is from a user application, you must figure out if the wrong declaration of serialization has any other side effects.

Setting the monitoring level for the the Servlet Session Manager modules to Medium or higher

Symptom:

The Tivoli Performance Viewer (TPV) advisor might display the following error message:

"TUNE0324W: There was an unknown error  detected in the Runtime Performance Advisor.  Check the application server logs and  enable trace."

Problem:

If the monitoring level for the servlet session manager Performance Monitoring Infrastructure (PMI) modules is set to None or Low, and if session persistence is enabled under Web Container > Session Management > Distributed Environment Settings, the error message is displayed because not enough session data are available for the advisor to give advice about the session size.

Response:

You must set the monitoring level for the the servlet session manager modules to Medium or higher. You can do this either through TPV or through the administrative console.

Diagnosing and fixing problems and troubleshooting

The correct directory of the pwbs_GetUrlPrefixesHelp.html file

Currently, the pwbs_GetUrlPrefixesHelp.html file is incorrectly installed into the ..../adminconsole.war/com.ibm.ws.console.perftuningadmin/nl/en/pwbs_GetUrlPrefixesHelp.html directory and the .../adminconsole.war/com.ibm.ws.console.servermanagement/nl/en/pwbs_GetUrlPrefixesHelp.htmldirectory.

To find the pwbs_GetUrlPrefixesHelp.html file from the Publish WSDL panel, you need to copy the the file into the .../adminconsole.war/com.ibm.ws.console.webservices/nl/en/pwbs_GetUrlPrefixesHelp.html directory.

Documentation

More information on configuring the Edge-Side Include processor is located in the documentation article, "Configuring Edge Side Include caching"

Edge Side Include (ESI) is configured through the plugin-cfg.xml file. However, a link to reference material that describes this file is missing from "Configuring Edge Side Include caching." To find this material in the InfoCenter, select the Quick reference view and then Files. Find "plugin-cfg.xml file" in the list and click to open.




Searchable topic ID:   relnotes
Last updated: Jun 21, 2007 10:43:20 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/

Library | Support | Terms of Use | Feedback