WebSphere Application Server Express, Version 5.0.2
This document contains the Release Notes for IBM WebSphere Application Server, Version 5.0.2. For the very latest updates, view the English online version of the Release Notes located at http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp .
Tips: If you use Internet Explorer on Windows 2003 platforms, you need to change the security settings of Internet Explorer. The default security settings are restrictive to the information center.
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 information center located at: http://www-3.ibm.com/software/webservers/appserv/infocenter.html .
To find installation information for Fix Pack 2, Version 5, see http://www-3.ibm.com/software/webservers/appserv/support/ .
WebSphere Application Server Enterprise, Version 5 customers must wait for the Enterprise Fix Pack 2 before applying Fix Pack 2 to the WebSphere Application Server product or to the WebSphere Application Server Network Deployment product. The WebSphere Application Server Enterprise product must be at the same fix level as the base product or the Network Deployment product that it extends.
Applying Fix Pack 2 to the WebSphere Application Server product without applying it to the WebSphere Application Server Enterprise product causes the Enterprise environment to fail.
WebSphere Application Server support for Linux platforms on iSeries and pSeries servers is now available. Please refer to http://www-3.ibm.com/software/webservers/appserv/was/requirements/ and http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html for hardware and software requirements.
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 Updates (Fixes, patches, etc.) in the Download section. This action takes you to the page to search for a specific download package.
Table of contents
All platforms
Applicability of the following list:
Tips: For other installation and uninstallation problems associated with WebSphere embedded messaging, see Messaging and Extended messaging release notes.
The updateWizard interface does not recognize the existing WebSphere Application Server product
Symptom | On some platforms, the updateWizard interface to the update installer program does not recognize the existing WebSphere Application Server product. |
Problem | The problem is due to a limitation in the InstallShield for MultiPlatforms (ISMP) program that the update installer program uses. The ISMP program does not recognize previous installations of WebSphere Application Server on some operating platforms. |
Recommended response | To work around the problem, click Specify product information and type the fully qualified installation root directory for the existing product in the Installation directory field of the updateWizard panel. |
Stop all running Java processes before you install or remove fix packs or interim fixes to avoid a corrupted system
Symptom | The fix pack installer does not warn you to stop all running Java processes before you install or remove fix packs or interim fixes. Your system gets corrupted if you do not manually stop all running processes. |
Problem | unidentified |
Recommended response | It is recommended to stop all applications (IBM and non-IBM) that
might be using the Java processes before installing or removing interim fixes
or fix packs. For example, in a co-existence scenario, if you have WebSphere
Application Server, Version 4 installed, stop its server too. Another example:
if you have Tomcat installed, it is recommended to stop this too. You must manually stop all running Java processes before installing or removing fix packs or interim fixes. See the Readme files for Fix Pack 1, Fix Pack 2, or the update installer; or see the following information center topics for more information:
|
WebSphere Application Server, Version 5.0.2 only updates IBM HTTP Server 1.3.26.x
The update installer only updated IBM HTTP Server 1.3.26.x not IBM HTTP Server 2.0. The update installer does not do any IBM HTTP Server version checking so it is important to ensure that you are applying WebSphere Application Server, Version 5.0.2 to the IBM HTTP Server 1.3.26.x.
Uninstall the Web services technology preview before installing Fix Pack 2
Symptom | The uninstaller for the Web services technology preview does not cancel the registration of the administrative console panels when run. |
Problem | When the installer is created for the Web services technology preview in the WebSphere Application Server, Version 5 stream, the installation process is verified, but the uninstallation process is not. It is now a prerequisite for the Web services technology preview to be uninstalled prior to the application of Fix Pack 2. |
Recommended response | Perform the following steps to work around this problem:
|
WebSphere Application Server products at level 5.0.0 might not support your operating system
![]() |
![]() |
To support some operating system platforms, you must install WebSphere Application Server Version 5 from the CD-ROM and then apply a fix pack. You must install Fix Pack 1 or 2 to support AIX 5.2. Fix Pack 2, which is product level 5.0.2 supports the Solaris Operating Environment 9. To install on either an AIX 5.2 or a Solaris 9 platform, follow the procedure in the information center topic, "Installing the product" to download and use an updated prereqChecker.xml file to install the V5 installation image. Using the current prereqChecker.xml file verifies that you have all required operating system patches. After installing the product at the V5 level , you can install the appropriate fix pack for your operating system.
Problems with Xerces versions that are not Java 2 Platform, Enterprise Edition compliant
Problem | 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. |
Recommended response | To work around this problem, use the version that ships with IBM WebSphere Application Server, Version 5. |
Applicability of the following list:
Applicability of the following list:
Help links for Application Assembly Tool, Application Resource Client Tool and Tivoli Performance Viewer bring up the English files
Problem | Help for the Application Assembly Tool, Application Resource Client Tool and Tivoli Performance Viewer appears only in English. |
Response | Change the path to the preferred language version to display the appropriate language (include list for languages if possible) list separately, if the paths are not the same. |
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"). |
Cannot access readme and PDF installation files for Traditional Chinese and German languages through the LaunchPad
Problem | You cannot access readme and PDF installation files for Traditional Chinese and German languages through the LaunchPad. |
Response | In any Web browser, view the following files located on the product
CD. The readme file for Traditional Chinese is located at: <cd drive>\readme\readme_zh_tw.html The installation PDF file for Traditional Chinese is located at: <cd drive>\doc\installguide_zh_tw.pdf The readme file for German is located at: <cd drive>\readme\readme_de.html The installation PDF file for German is located at: <cd drive>\doc\installguide_de.pdf |
Avoid missing characters in license agreement
Before installing the IBM WebSphere Application Server on a Traditional Chinese AIX machine, type the following to avoid missing characters within the license agreement:
cd /usr/lib/nls/loc/iconv/ mv IBM-eucTW_CNS11643.1986-1 IBM-eucTW_CNS11643.1986-1.save mv big5_CNS11643.1986-1 big5_CNS11643.1986-1.save
Product registration displays as English when installing in Brazilian Portuguese
Problem | When registering your product from the installation in Brazilian Portuguese, the product registration page displays in English. |
Response | To view the registration page in Brazilian Portuguese, you can enter the following URL, <install_root>\prt\PRT_Welcome_ptb.html or register the product using FirstSteps in Brazilian Portuguese. |
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. |
Persisted Session Time is displayed as a kanji character and ????? in Traditional Chinese locales
Symptom | The advice name, Persisted Session Time, in the Runtime Performance Advisor (RPA) configuration in the administrative console is shown as a kanji character and ????? in Traditional Chinese locales only. |
Problem | You can access to the advice configuration setting on the administrative console by clicking Servers > Application Servers > server_name > Runtime Performance Advisor Configuration > Advice Configuration. The advice name, Persisted Session Time, is shown as kanji character and ????? if you select the Traditional Chinese as the language on the Web browser to get access to the administrative console. |
Recommended response | Treat the advice item displayed as a kanji character and ????? as Persisted Session Time. |
Insufficient prerequisites cause warning messages during installation with AIX 4.3.3
Symptom | When installing the Simplified Chinese version of the IBM WebSphere Application Server on AIX 4.3.3, warning messages display because of insufficient prerequisites. The error message indicates that the file levels X11.fnt.ucs.ttf, X11.fnt.ucs.ttf_TW, and X11.fnt.ucs.ttf_KR do not match the level of file X11.fnt.ucs.ttf_CN. |
Problem | The last file has a level of 4.3.3.25, while the others have the level 4.3.3. |
Recommended response | To work around this problem, force the installation by modifying the prereqChecker.xml file to the required file level. |
Evaluating the product on National Language Version operating systems
![]() |
![]() |
![]() |
![]() |
The following steps are workarounds to evaluate IBM WebSphere Application Server and IBM WebSphere Application Server Network Deployment, Version 5 on National Language Version operating systems.
Tips:Do not change locale settings to original non-English settings until you finish the evaluation.
Tip:Do not change locale settings to original non-English settings until you finish the evaluation.
Open Terminal and run the following command before you install the IBM WebSphere Application Server, Version 5. Every time that you open a new terminal, you need to invoke this command:
# export LANG=en_US
Open Terminal and run the following command before you install the IBM WebSphere Application Server, Version 5. Every time you open a new terminal, you need to invoke this command:
# LANG=en_US # export LANG
Japanese not recommended on Red Hat Advanced Server Version 2.1
The Red Hat Advanced Server Version 2.1 GUI language selection menu displays two selections for Japanese: Japanese (eucJP) and Japanese (SJIS).
Click Japanese (eucJP) to install and run the IBM WebSphere Application Server in a Japanese environment. Using Japanese (SJIS) is not recommended.
For reference see the Red Hat Japanese Web site at http://www.jp.redhat.com/support/7.2/sla/rh72faq.html .
Patches needed for correct character display of the installation panel on Asian language platforms
Symptom | The installation panel displays garbled characters on Asian language platforms, including Korean, traditional Chinese, Japanese, and simplified Chinese, for the HP-UX 11i operating system. | ||||||||||||||||
Recommended response | Verify that the following patches are installed on your HP-UX 11i
machine:
You can find these patches at the following URL: http://www.hp.com/products1/unix/java/infolibrary/patches.html#1. |
ImagePath entry not updated in registry when you change the document root
When you change the document root in the IBM HTTP Server Version 1.3.28 administration server, the ImagePath entry in the registry, corresponding to the HTTP server, is not updated. There are no reported functionality problems caused by this registry entry.
Forms Proxy Settings and Proxy Cache do not behave correctly
Problem | When using Internet Explorer Version 6.0 to view the IBM HTTP Administration server, the Forms Proxy Settings and Proxy Cache do not behave correctly. If you select the radio buttons that display editable fields, the fields do not display. |
Recommended response | To work around this problem, use another version of the browser. |
Using IBM HTTP Server IKEYMAN to create a key database causes a core
Symptom | A core occurs while using the IKEYMAN or IKEYCMD utility, or during the IBM HTTP Server Secure Sockets Layer (SSL) initialization. |
Problem | An incompatibility exists between functions in various C or C++ run-time libraries. Depending on the order that the libraries are loaded, a core can occur or IBM HTTP Server fails to initialize. This problem is seen on various RedHat Intel versions, and SuSE SLES and RedHat on OS/390. |
Description | The GSKit libraries used by the IKEYMAN utility and the IBM HTTP Server SSL module require the C++ library libstdc++-libc6.1-1.so.2 file on the Intel platform and the libstdc++-libc6.1-2.so.3 file on the OS/390 platform. If the libraries do not exist, the IKEYMAN utility might provide only limited functionality and the IBM HTTP Server SSL fails to initialize. If another version of this library, or another library with a common function, loaded first, it might result in the use of an incompatible library routine. |
Recommended response | If you encounter this problem, set the environment variable LD_PRELOAD to
the following values before starting IBM HTTP Server or IKEYMAN:
|
Specifying the Listen 0.0.0.0.443 directive to the configuration file when you run IBM HTTP Server Version 2.0.42.2 on the Linux for PowerPC operating system
Note:This problem and response scenario is relevant to Secure Sockets Layer (SSL) or secure connection configuration.
Problem | A PEER_ID_NOT_SET error occurs in the error log if you run IBM HTTP Server Version 2.0.42.2 on the Linux for PowerPC operating system without first specifying the Listen 0.0.0.0.443 directive to the configuration file to enable SSL. |
Recommended response | You must specify the Listen 0.0.0.0.443 directive to the configuration file when you connect to IBM HTTP Server Version 2.0.42.2. |
Bringing up the IKEYMAN administrative console with the Conversational Monitoring System option for IBM HTTP server 1.3.28 and IBM HTTP Server 2.0.47
Symptom |
|
Problem | IKEYMAN is changed in Global Security Kit (GSKit) 7 to integrate
IKEYMAN for Java Secure Socket Extension (JSSE) that is Java-based and GSKit
that is C++-based. IKEYMAN is a tool used to manage digital certificates.
You can now use the same IKEYMAN for WebSphere Application Server and IBM
HTTP Server. For example, creating a Java Key Store (JKS) or a CMS key database
from the same panel within IKEYMAN. A key database enables a client application to connect to those servers that have digital certificates signed by those certificate authorities (CAs). You must perform extra steps to use the same IKEYMAN with the CMS option in addition to the JKS option. The CMS option is needed when you set up IBM HTTP Server for Secure Sockets Layer (SSL) transactions. |
Recommended response | Set the JAVA_HOME variable to the location of the IBM Software
Development Kit on the machine. If you are using WebSphere Application Server,
set the JAVA_HOME variable to the Java Runtime Environment (JRE) that
is shipped with WebSphere Application Server. For example:
If you cannot bring up IKEYMAN after the previous steps, perform the following steps:
|
A null pointer exception is thrown during the interactive installation of IBM HTTP Server on AIX systems
Symptom | When installing IBM HTTP Server as a standalone installation through the administrative console on the AIX platform, you can receive a null pointer Java error on the installation panels, when the installer begins to copy files to your machine. |
Problem | This situation is caused by an unstable AIX Object Data Manager (ODM) registry. |
Recommended response | To work around this problem:
Note: To remove the installation silently, add the -silent parameter to the regular uninstall command from the IBM HTTP Server installation location, for example: java -jar _uninst/uninstall.jar -silent |
Cannot start IBM HTTP Server 2.0.47 on AIX 5.2 systems
Symptom | A potential IBM HTTP Server 2.0.47 startup failure exists on AIX
5.2 systems when a non-default AIX resolver configuration is used (for example,
in /etc/netsvc.conf), and the IBM HTTP Server configuration file
(for example, httpd.conf), uses Listen directives that do
not specify an Internet Protocol address. The following is an example of
the error messages issued by IBM HTTP Server:[crit] (78) A remote host did not respond within the timeout period.: alloc_listener: failed to set up sockaddr for :: Syntax error on line 130 of /usr/IBMIHS/conf/httpd.conf Listen setup failed. |
Problem | This error is caused by a defect in the AIX resolver library. |
Recommended response | The defect is fixed by APAR IY40908 for AIX 5.2. The fix is shipped
with AIX52B Gold and later. Alternatively, you can take one of the following actions to solve the problem:
|
IBM HTTP Server 2.0.47 supports the AIX 5.1 and 5.2 Fast Response Cache Accelerator feature
IBM HTTP Server 2.0.47 supports the AIX 5.1 and 5.2 Fast Response Cache Architecture (FRCA) feature through the mod_afpa_cache.so plug-in module. However, you must apply the interim fix IY49388 for AIX 5.2. IBM HTTP Server 1.3.28 does not support the AIX FRCA feature.
Certificate revocation lists are not supported for IBM HTTP Server on HP-UX and Linux/s390
![]() |
![]() |
Using certificate revocation lists (CRLs) with IBM HTTP Server HP-UX and Linux/s390 is not supported at this time.
Unable to use the default service names created by the installer because they are common
Problem | In a same version coexistence scenario for IBM HTTP Server Version 1.3.28 or Version 2.0.47 on a Windows platform, you are unable to use the default service names created by the installer because they are common. |
Recommended response | To work around this problem, perform the following steps:
Note: The custom service names previously mentioned must be unique on your system and are not required to be those exact strings. |
The batchUpdate new feature cannot work for an EJB container-managed persistence bean when it is 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 is 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
Problem | 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:
|
Recommended response | To work around this problem, edit the EJB mappings in the WebSphere
Studio Application Developer toolset and do either of the following:
|
Web services engine
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. |
The correct directory of the pwbs_GetUrlPrefixesHelp.html file
Problem | 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. |
Recommended response | To find the pwbs_GetUrlPrefixesHelp.html file from the Publish WSDL panel, you need to copy the file into the .../adminconsole.war/com.ibm.ws.console.webservices/nl/en/pwbs_GetUrlPrefixesHelp.html directory. |
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. |
Recommended response | Consult the articles for the wsdeploy tool in the information center for the usage and message information. The information in the information center 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. |
Recommended 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 :
|
Web services clients using the Java Development Kit 1.4.1 on some operating systems fail to initialize
Problem | A WebSphere Application Server Web services client, which uses the
Java Development Kit (JDK)1.4.1 fails to initialize on some operating systems.
The same client using JDK 1.3.1 does not experience this problem. Currently,
this problem has only occurred on Solaris Operating Environment 9 and SuSE
Linux systems. On these systems, the client receives an exception similar
to the following:WSCL0100E: Exception received: java.lang.ExceptionInInitializerError at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java:173) at com.ibm.ws.webservices.engine.encoding.DefaultTypeMappingImpl.class$(DefaultTypeMappingImpl.java:128) at com.ibm.ws.webservices.engine.encoding.DefaultTypeMappingImpl.<init>(DefaultTypeMappingImpl.java:311) at com.ibm.ws.webservices.engine.encoding.DefaultTypeMappingImpl.getSingleton(DefaultTypeMappingImpl.java:138) at com.ibm.ws.webservices.engine.description.PortDesc.<init>(PortDesc.java:186) at com.ibm.ws.webservices.engine.deployment.wsdd.WSDDPort.<init>(WSDDPort.java:147) at com.ibm.ws.webservices.client.ClientXMLProcessor.addServiceRef(ClientXMLProcessor.java:523) at com.ibm.ws.webservices.client.ClientXMLProcessor.processFileContents(ClientXMLProcessor.java:297) at com.ibm.ws.webservices.client.ClientXMLProcessor.loadWebServicesClientXML(ClientXMLProcessor.java:334) at com.ibm.ws.webservices.component.WSClientImpl.start(WSClientImpl.java:131) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543) at com.ibm.ws.client.applicationclient.ClientComponentInitImpl.start(ClientComponentInitImpl.java:73) at com.ibm.ws.client.applicationclient.ClientContainer.initializeComponents(ClientContainer.java:579) at com.ibm.ws.client.applicationclient.ClientContainer.init(ClientContainer.java:174) at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:590) at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:371) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94) Caused by: java.lang.IllegalArgumentException: Unterminated quote at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:712) at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:511) at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:460) at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:441) at at com.ibm.ws.webservices.engine.types.Time.<clinit>(Time.java:89).null(Unknown Source) In addition to the com.ibm.ws.webservices.engine.types.Time class, this error can also occur in the com.ibm.ws.webservices.engine.encoding.ser.CalendarDeserializer class. |
Recommended response | Apply interim fix PQ75766 to solve this problem. |
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. |
All platforms
Help files are viewable only from a locally installed browser
Problem | If you access any of the IBM WebSphere Application Server tools from a remote machine, for example, the Assembly Toolkit, the remote browser cannot display the help files. You can only view the help files from a locally installed browser. |
Recommended response | 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. |
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:
Running the Assembly Toolkit on UNIX platforms causes errors
Problem | When you run the Assembly Toolkit on UNIX platforms, a sample of
errors that display follows:...Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific] Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific] ... |
Recommended response | The Assembly Toolkit or installer functions are not affected by these errors. These messages display in the command shell that spawned the Java GUI. You can disregard these messages. |
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." |
In the single server environment, the embedded Java Message Service server and IBM WebSphere Application Server run on the same single Java virtual machine
Problem | In the single server environment, the embedded Java Message Service (JMS) server and IBM WebSphere Application Server run on the same single Java virtual machine. Due to this architecture, if the MQ process (such as amq*.exe - not JMS process but MQ native process) dies and restarts while the JMS server is running, you must restart IBM WebSphere Application Server (ordinarily named server1) manually. This shutdown also can affect other installed applications. |
Recommended response | Restart the application server (server1). Note: In the distributed server environment, the JMS server and the application server run in separate processes. Therefore, the JMS server is not required to restart the application server. |
Selecting the Java Message 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 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.
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. |
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.
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.
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. |
Recommended response | Update to the correct version of DB2 UDB FP to resolve this problem. |
Upgrading to DB2 V8.1 to avoid a memory leak during the stress run using DB2 V7.2 on Windows 2000 platforms
You can upgrade to DB2 V8.1 to avoid a memory leak during the stress runs when you use DB2 V7.2 on Windows 2000 platforms.
Enabling the batchUpdate feature when running WebSphere Application Server, Version 5.0.2 with the DB2 Legacy CLI-based JDBC driver is ignored by the run time
Problem | Enabling the batchUpdate feature when running WebSphere Application Server, Version 5.0.2 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. |
Recommended response | If you want to use the batchUpdate feature 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:
|
Recommended 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 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. |
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. |
A NullPointerException exception is thrown if the serverName property is not provided when running type 4 DB2 Universal Java Database Connectivity driver
Problem | When you create a data source of DB2 Universal Java Database Connectivity (JDBC) driver and set the driverType property to 4, you must provide the serverName property. |
Description | If you do not provide the serverName property, DB2 throws a NullPointerException instead of an exception with meaningful message. |
Databases-IBM Cloudscape
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. |
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.
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
Problem | 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 |
Recommended response | To avoid receiving the exception, set the driverType data source custom property to 4. Consult with information center topics 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 is not 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 uninstall 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 information center 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, the administrative console fills in the
DB2 universal data sources settings by default instead of the Cloudscape Network
Server ones. Those settings include:
|
Recommended response | If you want to create the Cloudscape JDBC Provider Network Server
using the universal JDBC driver provider, perform the following steps to manually
modify the entries in the administrative console:
|
Cloudscape displays an exception when you access the result set after the transaction is committed
Problem | When you run WebSphere Application Server with Cloudscape using the Cloudscape network server framework, Cloudscape displays an exception when you access the result set after the transaction is committed despite the fact that the cursor holdability is false by default. |
Recommended response | This problem does not exist when you run in Cloudscape embedded.
This problem has been reported to Cloudscape. You can consult Cloudscape
Support. Ensure that your application does not rely on an exception that occurs. |
Adding quotes to the installCloudscape51.bat or installCloudscape51.sh file 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:
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. |
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
WebSphere Application Server security help files incorrectly mapped
Problem | Some of the links from the following WebSphere Application Server security windows to their corresponding help files are incorrectly mapped: Environment > Naming > CORBA Naming Service Users Environment > Naming > CORBA Naming Service Users > Add Environment > Naming > CORBA Naming Service Groups Environment > Naming > CORBA Naming Service Groups > Add System Administration > Console Groups > Add
|
||||||||||||
Recommended response | If you access a help file that does not correspond to the appropriate
WebSphere Application Server window, use the following table to locate the
correct help information. When you access the incorrect help file, find the
listing of help files located under Core Console on the left side
of your current help file window and click the appropriate link.
|
Secure interoperability between WebSphere Application Server, Version 5 and WebSphere Application Server, Version 5.0.1 or later fails when the Lightweight Directory Access Protocol base distinguished name in not correctly normalized in the WebSphere Application Server, Version 5 configuration
Problem | WebSphere Application Server, Version 5.0.1 or later system has a normalized distinguished name. When a WebSphere Application Server, Version 5.0.1 or later version 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 or later deployment manager. Another example is that a request fails when a WebSphere Application Server, Version 5.0.1 or later 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 or later system does not fail. |
Explanation | In WebSphere Application Server, Version 5.0.1 or later, 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 or later, the normalization occurs automatically at the run time. |
Recommended response | To ensure the interoperability between WebSphere Application Server, Version 5 and Version 5.0.1 or later, manually normalize the base distinguished name in the LDAP configuration on a WebSphere Application Server, Version 5 system by removing all the spaces before and after the commas and equal symbols. |
WebSphere Application Server does not start when Java 2 security is enabled using the IBM Software Development Kit 1.4.1 beta release
Symptom | WebSphere Application Server does not start when Java 2 security is enabled using the IBM Software Development Kit 1.4.1 beta release. |
Problem | WebSphere Application Server goes into a recursion and a final core
dump when Java 2 security is enabled using the IBM Software Development Kit
1.4.1 beta release. Note: This problem applies to IBM Software Development Kit 1.4.1 beta release of the WebSphere Application Server. This is not a problem for WebSphere Application Server running on the IBM Software Development Kit 1.3.X. |
Recommended response | To avoid the error, do not enable Java 2 security. By default, Java 2 security is disabled, but automatically enabled when global security is enabled through the administrative console. You should disable the Java 2 Security checkbox to disable Java 2 security. If you fail to do this in the administrative console and have already saved your changes and tried to restart the server, you can use the wsadmin tool to disable Java 2 security. wsadmin -conntype NONE wsadmin>$AdminConfig modify "(cells/<node name>/security.xml)" {{enforceJava2Security {false}}} wsadmin>$AdminConfig save wsadmin>exit |
The Federal Information Processing Standards security is enabled through the Secure Sockets Layer settings and the deployment manager cannot communicate with the node agent using the Simple Object Access Protocol connector
Symptom | The Federal Information Processing Standards (FIPS) security is enabled through the Secure Sockets Layer (SSL) settings and the deployment manager cannot communicate with the node agent using the Simple Object Access Protocol (SOAP) connector. |
Problem | The provider is not set properly for the SOAP client connector. |
Explanation | The SOAP client must use a FIPS (Java Secure Sockets Extension) JSSE provider when the server is listening on a FIPS enabled socket. |
Recommended response | You must modify the java.security file to provide the FIPS
properties to JSSE in both the deployment manager and each node. In the WebSphere/AppServer/java/jre/lib/security/java.security directory and in the WebSphere/DeploymentManager/java/jre/lib/security/java.security directory, modify the following provider list: security.provider.1=sun.security.provider.Sun security.provider.2=com.ibm.crypto.fips.provider.IBMJCEFIPS security.provider.3=com.ibm.crypto.provider.IBMJCE security.provider.4=com.ibm.fips.jsse.IBMJSSEFIPSProvider security.provider.5=com.ibm.jsse.IBMJSSEProvider security.provider.6=com.ibm.security.cert.IBMCertPath security.provider.7=com.ibm.crypto.pkcs11.provider.IBMPKCS11 |
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. |
Recommended 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 password 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 WebSphere Application Server, Version 5.0.2 or later. |
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, therefore 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 or encrypted and the security is not token inserted into the message. |
Recommended response | Change the application to a managed client application and use the J2EE programming model to invoke Web services. |
AccessControlExceptions exceptions might be reported in the system log file that are associated with the JavaMail-related configuration files
Symptom | In the system log file, WebSphere Application Server might report AccessControlExceptions exceptions that are associated with certain JavaMail-related configuration files such as .mailcap, mailcap, javamail.providers, and so on. |
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. |
Recommended response | To reduce this redundant reporting, you can grant read access to each reported JavaMail configuration file. For more information, see information center topics, "AccessControlException" and "Configuring app.policy files." |
Federal Information Processing Standards are supported in WebSphere Application Server, Version 5.0.2 or later
WebSphere Application Server, Version 5.0.2 or later supports a configuration option to use only Federal Information Processing Standards (FIPS) 140-2 certified cryptography modules including IBM Java Cryptography Extension Federal Information Processing Standards (IBMJCEFIPS) and IBM Java Secure Socket Extension Federal Information Processing Standards (IBMJSSEFIPS).
When WebSphere Application Server, Version 5.0.2 or later has FIPS-certified cryptography modules enabled, it uses the IBMJCEFIPS provider exclusively and does not use the IBMJCE provider. Also, when these cryptography modules are enabled, you can configure WebSphere Application Server to use the IBMJSSEFIPS provider on a per port basis.
The IBMJCEFIPS and IBMJSSEFIPS providers that are packaged in WebSphere Application Server, Version 5.0.2 or later are currently in the FIPS certification process. The IBMJCEFIPS and IBMJSSEFIPS modules in WebSphere Application Server, Version 5.0.2, are being certified using the IBM Software Development Kit, Version 1.3.1. The modules are undergoing certification for the Windows and AIX platforms and Solaris Operating System only.
IBM is firmly committed to FIPS certification and to meet the Government Security Standards. The IBMJSSEFIPS and IBMJCEFIPS providers are undergoing FIPS 140-2 certification. For more information, see the Cryptographic Module Validation Program FIPS 140-1 and FIPS 140-2 Pre-validation List.
Applications with Web services security enabled cannot interoperate between Version 5.1 and Version 5.0.2 Application Servers
Problem | Applications with Web services security enabled cannot interoperate between Version 5.1 and Version 5.0.2 Application Servers. The error message "digest mismatch" is displayed. |
Description | An error exists in the canonicalization algorithm for XML digital signatures, which is fixed in WebSphere Application Server, Version 5.1. For Web services security to interoperate between WebSphere Application Server Version 5.1 and Version 5.0.2 application servers, you must update Version 5.0.2.. |
Recommended response | Download the latest cumulative interim fix for WebSphere Application Server, Version 5.0.2 security. You can download this update by accessing the WebSphere Application Server support Web site and clicking All Updates (Fixes, patches, etc.). The update containing this interim fix will be available after the Version 5.0.2.1 interim fix. |
Interoperability issue exists between WebSphere Application Server for z/OS and WebSphere Application Server distributed packages when Secure Sockets Layer is supported, but not required
Symptom | An interoperability issue exists between WebSphere Application Server for z/OS and WebSphere Application Server distributed packages when Secure Sockets Layer is supported, but not required. |
Problem | WebSphere Application Server distributed packages set an integrity required flag for the Common Secure Interoperability Version 2 (CSIv2) inbound configuration to true by default because Secure Sockets Layer (SSL) requires integrity at a minimum. However, WebSphere Application Server for z/OS interprets this flag as an SSL requirement. |
Recommended response | In the security.xml file for WebSphere Application Server
distributed packages system, change the following line from:<CSI xmi:id="IIOPSecurityProtocol_1066667906706"> <claims xmi:type="orb.securityprotocol:CommonSecureInterop" xmi:id="CommonSecureInterop_1066667906706" stateful="true"> ... <requiredQOP xmi:type="orb.securityprotocol:TransportQOP" xmi:id="TransportQOP_1066667906706" establishTrustInClient="false" enableProtection="false" confidentiality="false" integrity="true"/> ... </claims> to <CSI xmi:id="IIOPSecurityProtocol_1066667906706"> <claims xmi:type="orb.securityprotocol:CommonSecureInterop" xmi:id="CommonSecureInterop_1066667906706" stateful="true"> ... <requiredQOP xmi:type="orb.securityprotocol:TransportQOP" xmi:id="TransportQOP_1066667906706" establishTrustInClient="false" enableProtection="false" confidentiality="false" integrity="false"/> ... </claims> You also can make the previous change using the WebSphere Application Server administrative scripting commands. |
The location of the Simple Object Access Protocol security properties file is incorrect in the setupClient.bat and setupClient.sh files
Problem | Note: This issue concerns the application client's installation
of WebSphere Application Server, Version 5 Fix Pack 1. The setupClient.bat file on Windows platforms and the setupClient.sh file on UNIX platforms incorrectly specify the location of the Simple Object Access Protocol (SOAP) security properties file. |
Explanation | In the setupClient.bat file, the correct location should
be: set CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:%WAS_HOME%/properties/soap.client.props In the setupClient.sh file, the CLIENTSOAP variable should be: CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:$WAS_HOME/properties/soap.client.props |
Recommended response | In the setupClient.bat and setupClient.sh files,
complete the following steps:
|
All platforms
Applicability of the following list:
Netscape browser
All platforms
Resolve the administrative console port conflict
Problem | The administrative console port is in conflict with an application already running on the machine. |
Recommended response | You can change this port in the following files:
|
The correct directory of the pwbs_GetUrlPrefixesHelp.html file
Problem | 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. |
Recommended response | 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. |
Resizing the Netscape browser results in an error
Problem | If you resize your Netscape browser, you can get a Data Missing error. |
Recommended response | You can ignore the error message; it disappears in 60 seconds. |
Resizing the Netscape browser causes an error 404 message
Symptom | 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. |
Problem | This situation occurs because the browser reloads the frame when resizing the window. |
Recommended response | 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
Problem | While working with the right-hand panel of the administrative console to do regular administrative tasks, the browser screen blanks out intermittently. |
Recommended response | To work around this problem, do one of the following:
|
Resizing Netscape Version 4.7 causes errors
Problem | 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.websphere.servlet.error.ServletErrorReport: at java.lang.Class.newInstance0(Native Method) ... |
Explanation | 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. |
Explanation | 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. |
Recommended response | There is no workaround if you use Netscape 4.79, which is the supported level of Netscape for this release. |
Enabling Netscape Version 4.7 to display double-byte character set correctly
![]() |
![]() |
Problem | When using Netscape on AIX platforms without the translated package, the English version of Netscape is available for all locale environments as the default package. However, the English version of Netscape does not display double-byte character set (DBCS) characters on the browser radio buttons and title bars because the fonts are mismatched. |
Recommended response | To work around this problem, you can install the message resource
to make the translated version of Netscape available on a DBCS environment.
Use the translated version of Netscape to display the corrupted DBCS correctly.
Change the locale from English to the expected DBCS locale before starting
Netscape. For example, issue the following commands to display the Japanese
contents on Ja_JP (AIX Shift JIS locale):$ export LANG=Ja_JP $ netscape& How to check the installed package For the AIX platform:
For the Red Hat Linux Version 7.2 platform: Run the rpm-ql netscape-common command to get the list of installed files. In case of Netscape Version 4.78 on Red Hat Linux Version 7.2, the translated packages for seven languages including four DBCS languages (Japanese, Korean, Simplified Chinese, and Traditional Chinese) are included in a common package. How to install the package For the AIX platform: Install the Netscape.msg.%L.communicator.rate package where %L is the locale information for the System Management Interface Tool (SMIT) or SMITTY to use. This message resource is provided by the Bonus Pack CD or the Expansion Pack CD for AIX platform, which provides the Netscape common package. Perform the following steps to install the package:
For Red Hat Linux Version 7.2 platform: The default Netscape installation can install each translated resource as part of the common package. There is no way to install the translated package individually. However, TrueType fonts (TTF packages) require installation for each language to correctly display the translated resources on Netscape. Use the following to check if the required font files are correctly installed: $ rpm -qa | grep ttf resources.0-4 ttfm-0.9.1-8 ttfonts-ja-1.0-6 ttfonts-ko-1.0-10 ttfonts-zh_CN-2.11-5 ttfonts-zh_TW-2.11-5 |
Using Netscape Version 4.79 on a Solaris Operating Environment causes problems
Problem | Using Netscape Version 4.79 on a Solaris Operating Environment to access the administrative console causes problems with some key text translations with the zh_TW.EUC locale. |
Recommended response | This situation is not a problem when you use Netscape Version 4.7. The officially supported version of Netscape on a Solaris Operating Environment is Version 4.79, but in this case the workaround is to use Netscape Version 4.7. |
Limitations occur when using Netscape with Solaris Operating Environment
Symptom | If you click Troubleshooting > Logs and Trace > <server> > Diagnostic Trace > Modify, the window that pops up allowing you to select the Components and Groups to trace might not display a scroll bar, preventing you from viewing all the components and groups. |
Problem | The text area displaying the selected components, groups, and trace levels does not have a vertical scroll bar. This omission is a limitation of Netscape on a Solaris Operating Environment. |
Recommended response | To work around this problem, refresh the window to show the scroll bar. |
Netscape browser must be capable of launching from a terminal window on all UNIX platforms
To make sure the Netscape browser can launch from a terminal window, edit or create a file called profile in the /etc directory and add the Netscape directory to the system path. For example:
PATH=$PATH:/opt/Netscape export PATH
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. |
Explanation | $AdminControl TestConnection configId props This command is deprecated. This command might give false results and does not work when connected to a node agent. As of WebSphere Application Server, Version 5.0.2 or later, 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 or later 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 or later returns the following message: WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported. |
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. |
System performance degrades when you configure the node agent failover with a certain script
Problem | 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 |
Recommended response | 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.. |
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. |