WebSphere Application Server Express, Version 5.1.1
This document contains the Release Notes for IBM WebSphere Application Server - Express, Version 5.1.1. For the very latest updates, view the English online version of the Release Notes located at http://www.ibm.com/software/webservers/appserv/library/ .
Documentation for Version 5.1.1
For the latest information on installing and using the product, see the online information center located at the following Web site:
http://www-3.ibm.com/software/webservers/appserv/infocenter.html .
For convenience, the product CD-ROM contains an English "Getting started" PDF file containing an overview and installation instructions.
For additional installation instructions, including fix pack details, visit the Support Web site: http://www-3.ibm.com/software/webservers/appserv/support/ .
WebSphere Application Server Support page
To review, download, and install any recommended or mandatory interim fixes, visit the WebSphere Application Server Support page at 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.
What Is New in Version 5.1.1
WebSphere Application Server, Version 5.1.1 provides prerequisite upgrades for the following features:
Table of contents
Applicability of the following list:
Help search does not return hits for Latin-1 terms with diacritical markings
Problem | The help search in the administrative console does not return search results for Latin-1 terms that contain diacritical markings (for example, German "fur", where the "u" includes an umlaut). |
Response | To work around this problem, use the decimal representation of the character in the search term (for example, "für"). |
The Java virtual machine cannot translate coded Character Set Identifier used by the embedded messaging queue manager
Symptom | When running the IBM WebSphere Application Server with global security
enabled, the embedded messaging provider can fail to start with a MSGS0504E
message and an UnsupportedEncodingException exception:MSGS0504E: JMS Server Security Service Thread received Socket Exception: java.io.UnsupportedEncodingException: Cp5050 |
Problem | This message indicates that the Java virtual machine (JVM) cannot translate the Coded Character Set Identifier (CCSI) used by the embedded messaging queue manager. |
Recommended response | To work around this problem, set a locale and language value that map to a code page supported by the JVM. Refer to the WebSphere MQ messaging platform-specific books Web site at http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html for a "WebSphere MQ Platform Quick Beginnings V5.3" manual that is relevant to your platform. Look for a table in the manual with a list of locale and language to CCSI mappings supported by the queue manager. Then, select a locale and language that maps to a CCSID that is supported by the JVM. Set the selected locale and language, and restart the IBM WebSphere Application Server. |
Cannot display newly created Windows domain users during application management for the non-English locales only
Symptom | The newly created domain users are not retrieved when you perform application management. The newly created groups display correctly, however, and the newly created local users also display correctly. |
Problem | If you map users to roles by clicking A Role > Choose Users > Find Users, only users created on Primary Domain Controller before adding the client machine to the domain are displayed. If a new user is created while the client machine is already on the domain, the getUser function does not retrieve the new users created on Primary Domain Controller. |
Description | The getUser application programming interface (API) works correctly for the English locales, but does not work correctly for the non-English locales. |
Receiving a NullPointerException exception while debugging JavaServer Pages in the Javascript code using Bean Scripting Framework
Symptom | WebSphere Application Server might issue a NullPointerException exception
while debugging a JavaServer Pages (JSP) file in the Javascript code
using Bean Scripting Framework (BSF). The servlet engine fails with a double open on a reader or writer stream. |
Description | The Java servlet application programming interface (API) does not define behavior upon reopen in a reader or writer stream. |
Recommended response | Stop and restart WebSphere Application Server before debugging to
verify that a clean instance of WebSphere Application Server is running. Tip: The JSP debugging function of BSF is deprecated in WebSphere Application Server, Version 5.1. |
Location of the UDDI Utility tools
The Java archive (JAR) file for the UDDI Utility tools is located in the <DeploymentManager-install-dir>/UDDIReg/scripts> directory.
Switching between secured and unsecured UDDI publish access
You can run the IBM WebSphere UDDI Registry with WebSphere Application Server security either enabled or disabled. However, you can see unpredictable results if you change between the two settings. For example, if you publish an entity with security disabled, that entity might not be present in the list of registered entities (from the get_registeredInfo request), because the user ID can be different.
Potential problem using UDDI with Cloudscape on AIX systems
Problem | On AIX systems, over time, and depending on the volume of work, Simple
Object Access Protocol (SOAP) application programming interface (API) applications
might experience the following errors:HTTP Error: 500 Internal Server Error <errInfo errCode='E_fatalError">E_fatalError (10500) Serious technical error has occurred while processing the request. </errInfo> The SystemOut.log file might display the following exceptions: [16/09/03 16:01:45:186 BST] 2b7dcd4c SystemOut 0 Error 40XT0 : An internal error was identified by RawStore module. [16/09/03 16:01:45:186 BST] 2b7dcd4c SystemOut 0 at db2j.em.b.newException(Unknown Source) [16/09/03 16:01:45:187 BST] 2b7dcd4c SystemOut 0 at db2.v.g.setActiveState(Unknown Source) [16/09/03 16:01:45:187 BST] 2b7dcd4c SystemOut 0 at db2.v.g.openContainer(Unknown Source) |
Recommended response | Issue the following command to disable the optimization for the method
that causes the problem, before starting the application server in question:export JITC_COMPILEOPT=NQOPTIMIZE{db2j/b/r}{_ko} The fix for this problem is available in AIX PPC32, 1.4.1. Service Release 2, FCS_Refresh. |
Ignoring the error messages when running the Web services application using an HTTP or a Java Messaging Service transport
Problem | When running the Web services application using an HTTP or a Java
Messaging Service (JMS) transport in WebSphere Application Server, Version
5.1 and later, the following error messages are displayed in the SystemOut.log file: [9/30/03 17:58:20:387 CDT] 140727a PrivMBeanRegi E J2CA0108E: the parent MBean for [9/30/03 17:58:20:387 CDT] 140727a PrivMBeanRegi E J2CA0108E: the parent MBean for <null> could not be found, the identifier used to find the MBean is cells/svtlnx2/nodes/svtlnx2/resources.xml#builtin_jmsprovider. [9/30/03 17:58:35:611 CDT] 17d1b24 ConnectionMan W J2CA0075W: An active transaction should be present while processing method allocateMCWrapper. [9/30/03 17:58:35:625 CDT] 17d1b24 ConnectionMan W J2CA0075W: An active transaction should be present while processing method initializeForUOW. |
Recommended response | Ignore the error messages. |
Session management of deployed target services in the Web services gateway
Problem | The Web services gateway does not support session management and maintenance of deployed target services using HTTP cookies. |
Recommended response | Use Simple Object Access Protocol (SOAP) headers to support session management and maintenance of deployed target services. |
Ignoring the error messages when you click Add or Remove on the Define Certificate Store page
Symptom | When you update one of the certificate stores after restoring the
gateway security configuration using the restore function on the gateway administrative
client, and remove the old entry, for example, /opt/WebSphere/AppServer/etc/ws-security/samples/intca2.cer,
by clicking Remove on the Define Certificate Store page, you receive
the following messages: The page cannot display. If you go back to the original page, the entry is removed. If you add the new entry by cutting and pasting the path, for example, /usr/WebSphere/AppServer/etc/ws-security/samples/intca2.cer, into the blank field and clicking Add, the next page is returned with an Error 500 message. However, the new entry is added. When the page is returned with errors, the SystemOut.log file contains the following stack trace: [10/16/03 11:04:55:137 CDT] 2126a573 WebGroup E SRVE0026E: [Servlet Error]-[]: java.lang.NullPointerException at org.apache.jsp._certStore._jspService(_certStore.java:172) at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service (HttpJspBase.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper. service(JspServlet.java:344) at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile (JspServlet.java:662) at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet. java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService (StrictServletInst |
Recommended response | Ignore these error messages because you can use the Add or Remove function in the certificate store. |
An HTTP 401 error and a Web services exception occur when you attempt to access a protected resource without any HTTP basic authentication information
Symptom: | For Web services clients running with HTTP or HTTPS but without Web services security, any attempt to access a protected resource without any HTTP basic authentication information might result in an HTTP 401 error and a Web services exception. |
Problem | The service request does not run because of the HTTP 401 error. The cause of the problem is a failed authentication due to the missing HTTP basic authentication information. |
Recommended response | Configure a challenge prompt by using a Java system property named
com.ibm.ws.webservices.loginSource to enter the HTTP basic authentication
user ID and password. The valid values of the property are prompt or stdin,
respectively for an administrative console type or a text-based challenge
prompt. You can also specify the user ID and password in the deployment descriptor
or practically in the Stub or Call instance. See the information center for
details. Tip: Use HTTPS to protect the user ID and password with basic authentication. |
Assembly Toolkit displays unsupported type for application client resource reference
When configuring a resource reference for an application client module in the Assembly Toolkit, the Type field 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:
Ignoring the warning message when deploying an application coded in WebSphere Studio Application Developer Integration Edition, Version 5 to WebSphere Application Server
Symptom | When deploying an application coded in WebSphere Studio Application
Developer Integration Edition, Version 5 to WebSphere Application Server,
a warning message similar to the following example is displayed: "ADMA0087W: Warning from EJBDeploy: The static field should be accessed in a static way [severity 1]" |
Problem | This warning message displays because the static class variables are used incorrectly in the generated session bean coded by WebSphere Studio Application Developer Integration Edition, Version 5. The WebSphere Application Server Deployment Tool for the Enterprise JavaBeans (EJBDeploy) tool catches this wrong usage previously mentioned during the application deployment time. |
Response | Ignore the warning message; this problem does not affect the installation or the deployment of the application. |
All platforms
Embedded Java Message Service provider installation fails
Problem | It is possible for the embedded Java Message Service (JMS) provider installation to fail without any visible warning. This situation can occur as a result of the JMS provider prerequisite checker returning an error that the IBM WebSphere Application Server installation is not expecting. The IBM WebSphere Application Server installation completes, but the JMS provider is not installed. |
Recommended response | If the JMS installation fails, look for details in the mq_prereq.log file in the /tmp directory and in the create_mq.log and mq_install.log files in the install_root/log directory. When you have corrected the situation, install the embedded JMS provider separately by clicking Custom installation then selecting either one or both of the following options, as required: Embedded Messaging Server and Embedded Messaging Client. For more information about installing the embedded JMS provider, see the information center topic, "Installing WebSphere embedded messaging as the JMS provider." |
Information you need to know about using server-side and client-side selectors
The default behavior for the internal Java Message Service (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.
WebSphere Application Server, Version 5.1 or later does not work with the zh_CN.EUC locale
Symptom | With the locale set to zh_CN.EUC, in a WebSphere Application Server,
Version 5.1 or later environment with the Embedded Messaging Server installed,
any attempt to start an application server (for example, server1) fails with
messages including: [04-5-13 13:02:11:511 CST] c26b16 JMSEmbeddedPr A MSGS0050I: ???? Queue Manager [04-5-13 13:02:33:820 CST] c26b16 JMSEmbeddedPr A MSGS0051I: ????? Queue Manager [04-5-13 13:02:33:867 CST] c26b16 JMSEmbeddedPr A MSGS0052I: ?????? |
Problem | The embedded messaging broker cannot run with the zh_CN.EUC locale, and causes the application server startup to fail. |
Description | If you set the zh_CN.EUC locale, you cannot run WebSphere Application Server with the Embedded Messaging Server option. |
Recommended response | Change the server locale to something other than zh_CN.EUC locale before starting an application server. With the locale zh, zh.UTF8, or zh_CN.UTF8 , the application server can be started successfully. |
Component-managed authentication alias not specified
Problem | 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 |
Recommended response | 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. |
Stopping the queue manager while running the embedded Java Message Service provider stops IBM WebSphere Application Server
Problem | When you run the embedded Java Message Service (JMS) provider and the queue manager stops, IBM WebSphere Application Server is also stopped. |
Recommended response | To recover the queue manager and IBM WebSphere Application Server, you must start the application server. |
Databases-DB2
The WebSphere Application Server Java virtual machine stops after you run the force application command in the DB2 command line
Symptom | The WebSphere Application Server Java virtual machine (JVM) stops when you run the force application command 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 stops after you run 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 stop as soon as you run 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 stop right after running the force application command. However, you might see the WebSphere Application Server JVM stop later. |
Recommended response | DB2 is aware of this problem. You can consult DB2 Support. The APAR
number is JR18535. This problem is fixed in DB2 V8.1 FP4. Upgrade to DB2 V8.1 FP4 to avoid the problem. |
Upgrading DB2 V8.1 FP2 or a later version to avoid receiving an exception when the Java 2 security is enabled
Symptom | 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 example is displayed 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(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)) 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. |
Recommended 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. |
Cannot run the DB2 legacy call level interface-based Java Database Connectivity driver and the DB2 Universal Java Database Connectivity driver in the same Java virtual machine
Symptom | WebSphere Application Server fails if you use the DB2 legacy call level interface (CLI)-based Java Database Connectivity (JDBC) driver and the DB2 Universal JDBC driver in the same WebSphere Application Server Java virtual machine (JVM). |
Problem | The failure occurs when using DB2 V8.1 FP5 and lower. The failure is because of a DB2 problem with coexistence of the DB2 legacy CLI-based JDBC driver and the DB2 Universal JDBC driver that are used in the same JVM. |
Recommended response | Upgrade to DB2 V8.1 FP6 and higher. |
Applications might stop when you use the DB2 V8.1 FP3 Universal Java Database Connectivity driver type 2 XA data source
Symptom | Applications might stop when you use the DB2 V8.1 FP3 Universal Java
Database Connectivity (JDBC) driver type 2 XA data source. You might see the
following message in the SystemOut.log file: Transaction [transaction number] has timed out after xxx seconds. |
Problem | This defect is in the DB2 V8.1 FP3 Universal JDBC driver. This defect is fixed in DB2 V8.1 FP4. |
Recommended response | Upgrade your DB2 database to DB2 V8.1 FP5. If you cannot upgrade your database to DB2 V8.1 FP5, use the legacy call level interface (CLI)-based JDBC driver XA data source. |
Using the correct user ID and password to connect to the DB2 Universal Java Database Connectivity driver
Symptom | If you do not use a user ID and password, or if you use some combination of an invalid user ID or password to connect to the DB2 Universal Java Database Connectivity (JDBC) driver, you still can get the connection. However, when the connection is used in an XA transaction, an XAException exception is displayed with an XAER_PROTO error code. |
Problem | The DB2 Universal JDBC driver requires the correct user ID and password to acquire a connection that is unlike the legacy call level interface (CLI)-based JDBC driver. |
Recommended response | Verify that you use the correct user ID and password to connect to the DB2 Universal JDBC driver. DB2 is aware of the problem. |
Using DB2 V8.1 FP3 on the HP-UX platform might cause defunct processes
Symptom | When you use DB2 V8.1 FP3 on the HP-UX platform, the defunct processes
are displayed in the system. The following example illustrates the defunct
processes:db2admin 3162322 393328 1 <0:00 defunct> |
Problem | Using DB2 V8.1 FP3 on the HP-UX platform might cause defunct processes. The defunct processes can accumulate over time and consume system resources. |
Recommended response | DB2 has fixed this problem. Upgrade your DB2 database to DB2 V8.1 FP5. |
Configuring a preTestSQLString customer property if using the pre-test connection function with DB2 Legacy CLI-based type 2 Java Database Connectivity Provider Driver (XA)
Problem | When using the pre-test connection function with DB2 Legacy CLI-based type 2 Java Database Connectivity Provider (JDBC) Driver (XA), you need to provide an SQL statement to the preTestSQLString customer property. If you do not provide an SQL statement to the preTestSQLString customer property, WebSphere Application Server uses the default SQL string for the pre-testing the connection, which might cause applications to display a javax.transaction.xa.XAException exception. |
Recommended response | DB2 has fixed this problem. Upgrade your DB2 database to DB2 V8.1 FP5. |
A NullPointerException exception 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 exception (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.execu te(GenericPreparedStatement.java:351) |
Problem | This case is rare and is usually an application error that is caused by the application not calling registerOutputParameter but calling setNull on the Bit Varying type parameter. |
Recommended response | If you encounter this problem and use callableStatements, ensure that you call the registerOutputParameter method. |
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 is not supported or shipped with any future releases of WebSphere Application Server.
An error occurs when enlisting a global transaction and subsequent calls to the ResultSet.next method might stop
Symptom | An error occurs when enlisting a global transaction. Subsequent
calls to the ResultSet.next method might stop. The error is an XAException
with error code -3 (XAER_RMERR) and is similar to the following errors:javax.transaction.xa.XAException at com.ddtek.jdbcx.sequelink.SequeLinkImplXAResource.start(Unknown Source) at com.ddtek.jdbcx.slbase.BaseXAResource.start(Unknown Source) at com.ddtek.jdbcspy.SpyXAResource.start(Unknown Source) |
Problem | This error is caused by a bug in the SequeLink Java Database Connectivity (JDBC) driver. Case 15007076 is opened against DataDirect Technologies for this problem. |
Description | The XAResource.start error causes the stop in the ResultSet.next method. |
Recommended response | To work around this problem, switch to the Connect JDBC driver to
connect to the Microsoft SQL server. When a patch is received from DataDirect
Technologies, a corresponding patch for the WebSphere embedded SequeLink driver
is available on the DataDirect Driver Updates download page of WebSphere Application
Server: ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm |
The Connection.setReadOnly method of Oracle database behaves differently in WebSphere Application Server
Problem | Oracle does not support readonly connections. However, you can still call the connection.setReadOnly(true) method. After the connection.setReadOnly(true) method is called, the connection.isReadOnly() method returns true but the connection is still a non-readonly connection. When the connection.setReadOnly(boolean) method is called, the Oracle database starts a transaction. |
Description | The connection.setReadOnly(boolean) method of Oracle database behaves differently in WebSphere Application Server from the Oracle behavior previously described. When the connection.setReadOnly(true) method is called, an SQLException exception is displayed to indicate that the Oracle database does not support readonly connections. When the connection.setReadOnly(false) method is called, Application Server does not call the setReadOnly(false) method to the native Oracle connection. In either the connection.setReadOnly(false) method or the connection.setReadOnly(true) method, no Oracle transaction can start. |
Applying the Oracle ojdbc14.jar driver file when running WebSphere Application Server, Version 5.1 or later with an Oracle database
Problem | If you run WebSphere Application Server, Version 5.1 or later with an Oracle database, use the Oracle driver that supports IBM Software Development Kit 1.4.1. You must download the Oracle ojdbc14.jar driver file from the Oracle Web site. |
Recommended response | Download a driver that contains a recovery fix for the Oracle bug
2881276 from the following Web site: ftp://oracle-ftp.oracle.com/dev_tools/patchsets/languages/bug2881276/ If the link is broken, contact Oracle support. |
An issue with XA transactions and IBM Informix Dynamic Server is identified
Symptom | An issue with XA transactions and IBM Informix Dynamic Server is identified. This issue might cause a number of exceptions including, but not limited to: "java.sql.SQLException: Could not position within a table" or "java.sql.SQLException: Could not do a physical-order read to fetch next row." This problem might affect a number of WebSphere Application Server applications that require XA transactions support from IBM Informix Dynamic Server. |
Recommended response | Currently, no solution exists for the problem. IBM Informix Dynamic Server is working to resolve the issue. |
All platforms
Do not use the IBM Developer Kit, Java Technology Edition Version 1.4.x security debug with all or domain options
Problem | WebSphere Application Server goes into recursion and fails when -Djava.security.debug=all or -Djava.security.auth.debug=all is enabled. |
Description | If Java 2 Security is enabled and IBM Developer Kit, Java Technology Edition, Version 1.4.x 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 stops with a Java core dump. This problem is recognized in the IBM Developer Kit, Java Technology Edition Version 1.4.x. |
Recommended response | Do not use the IBM Developer Kit, Java Technology Edition Version 1.4.x security debug with the all or domain option until the issue in IBM Developer Kit, Java Technology Edition Version 1.4.x is addressed. |
The Tivoli Access Manager Java run time and the Tivoli Access Manager for WebSphere Application Server, Version 5.1 and later are not supported on the HP-UX platform
Symptom | On the HP-UX platform, the SvrSslCfg utility that might be called
by the $WAS_HOME/bin/pdwascfg command fails with the following message: java.lang.IllegalStateException: java.lang.IllegalStateException: java.lang.ClassCastException |
Problem | The Java run time for the Tivoli Access Manager for WebSphere Application Server, Version 5.1 and later are not supported on the HP-UX platform. |
Netscape browser
All platforms
Netscape 4.7 cannot identify the parameters with a space (" ") character in the Web address
Symptom | Netscape 4.7 cannot identify the parameters with a space (" ") character in the Web address, but it can identify the parameters if the space is concatenated with "%20". For example, the parameters that need to pass through the Web address to the server side must be something like "ABC%20XYZ", not "ABC XYZ". |
Problem | This problem is because the "ExecutionState.UNKNOWN" default status is always set. If the parameter is "ABC XYZ" with a space character in the Web address, only "ABC" is received at the server side, which means the browser cannot identify the parameter. |
Recommended response | To avoid this problem, perform one of the following tasks:
|
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. |
Problem | 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. |
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"/>
The node agent SystemOut.log message repeats continuously on an AIX platform when the Performance Monitoring Infrastructure is enabled
Problem | On an AIX platform when the Performance Monitoring Infrastructure
is enabled, the following node agent SystemOut.log message repeats
continuously:No PMI Module found for the Mbean systemModule |
Recommended response | To avoid receiving the message, install the bos.perf file set on an AIX platform. |
Install the bos.perf.libperfstat and bos.perf.perfstat files on an AIX platform
Problem | On an AIX platform, Tivoli Performance Viewer does not show the counters and performance data from the system data module. |
Recommended response | Install the bos.perf.libperfstat and bos.perf.perfstat files
on an AIX platform. To verify if both files are on your system, issue the following commands: lslpp -achq bos.perf.libperfstat lslpp -achq bos.perf.perfstat If you see a message similar to Fileset bos.perf.libperfstat not installed, install the required bos.perf.libperfstat and bos.perf.perfstat files from the AIX base installation Web site. |
Using tools on the HP platform to check the memory usage of the WebSphere Application Server process might show a high memory usage
Problem | Using tools on the HP platform to check the memory usage of the WebSphere Application Server process might show a high memory usage (with the maximum set to 256 MB). |
Description | The virtual number shown in glance and other tools does not represent the actual physical memory committed in use. This behavior is normal on the HP platform. |