Last updated 3/07/01
This document contains the Release Notes for IBM WebSphere Application Server Version 3.5 with Fix Pack 3 (also known as Version 3.5.3) for Linux, Windows NT (Windows 2000 supported), Sun Solaris, AIX and HP-UX.
These Release Notes cover both the Advanced and Standard Editions. Because the Standard Edition functions are a subset of the Advanced Edition functions, note that some information in these Release Notes (for example, the mention of enterprise beans) applies only to the Advanced Edition.
Note: This file is best printed in a landscape format. Also, if you find that all text does not fit on a printed page, a suggestion is to decrease the scaling before printing. To change the scaling, access the print properties. Setting the scaling to 80 has proven successful.
See InfoCenter article 0.0.7 to learn more about these additions to Fix Pack 3.
The Release Notes contain information about known defects and the workarounds. This document also includes some supplemental information for topics covered in the Application Server documentation.
Installation and Configuration
Starting Application Server Components
Administrative Console (GUI) and Command Line Tools
Enterprise Beans
Object Request Brokers (ORBs)
Servlets
Java Server Pages Files (JSP files)
XML and XSL
Connection Pooling
HttpSession
Workload Management
Networking
Security
Performance and Stability
OLT and Debugging
Tracing
National Language Version Issues/Limitations
Samples
InfoCenter
Problem | Op System | Workaround |
---|---|---|
If you named your Microsoft SQL Server instead of using the default name (hostname), you will need to configure Sequelink. | Windows NT/2000 | Follow these steps to configure Sequelink: Note:The non-default Microsoft SQL Server name is STLAB20\SQLEJS in this example.
|
The following error messages appear in the browser window when trying to access
static HTML pages served by the File Serving Enabler in WebSphere Application Server
Version 3.5.3, Advanced Edition: A recursive error was detected. The server cannot use specified error page. Please check the application error-path. Original Error: Error Message: File not found: null Error Code: 403 Target Servlet: File Serving Enabler All
| Apply efix pq46735.jar by doing the following:
|
Note:If you applied efix pq46735, make sure you remove this efix. If you leave this efix in place, you may not see an error but the server code you are running may be back-leveled. You can remove this by taking pq46735.jar out of your com.ibm.ejs.sm.adminserver.classpath. |
On Unix, permissions of DBConfig.sh need to be changed to make it executable after unzipping the DBConfig.zip. When a radio button for a particular database is selected, the tool does not automatically fill in the correct database driver and database prefix. | AIX, Solaris | Choose the right database driver from the pull down menu and change the database prefix to the appropriate value. |
On Unix, DBConfig tool changes the permissions of $WAS_HOME/bin/startupServer.sh to nonexecutable. | AIX, Solaris | Change the permissions of startupServer.sh to make it executable before starting the administrative server. |
The IIS filter/extension mechanism requires that the dll be
on the virtual directory. Therefore install sets the virtual
directory to point to WebSphere bin directory. When setting the virtual directory to point
to WebSphere's bin directory, there are files that should not be accessed. For example: If
a user types "http://All
| To fix this problem: |
|
The Cancel button in the uninstall screen doesn't work. | AIX | If you need to cancel the install, press Ctrl+X. |
Upgrading from WebSphere Application Server Version 3.5 to Version 3.5.3 on Microsoft Windows NT, Enterprise Edition, SP6a fails. When running the
FixPak 3 install.bat the following error displays: Upgrading IBM JDK 1.2.2 The syntax of the command is incorrect. Invalid number of parameters Error in POProcessor: The directory specification, -targetdir D:\WebSphere\AppServer\java_ptf_3, seems not to be a directory. |
Windows NT | Press any key to continue. |
Distributed transaction which uses two datasources defined on separate WebSphere Application Server
nodes is failing. Both the data sources use JTA enabled DB2 7.1/FixPak 2 JDBC drivers. The following exceptions were thrown by the client: Failed to debit card: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: debitCard failed: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL30090N Operation invalid for application execution environment. Reason code = "06". SQLSTATE=25000 Note: "Debit card" in the above error message is the application used for testing. | All | |
For SQL Server 2000 on Windows NT, there is a problem with
Microsoft Data Access Componentry(MDAC) Version 2.6.
The ODBC driver for SQL Server, embedded with SequeLink 5.x, requires dlls that
are no longer shipped in MDAC Version 2.6. Therefore, if you install SQL Server 2000 on
a clean Windows machine, the following error displays: Specified driver could not be loaded due to system error 126 (MERANT MSSS Driver for SequeLink 5.0) | Windows NT | The SQL Server 7 driver requires dlls that are not required
by the SQL Server 2000 driver and no longer ship with MDAC Version 2.6 or higher. To fix this problem, install the MDAC version that is shipped on the DataDirect SequeLink CD(or version 2.1 from the Microsoft website). Here is a link to the Microsoft website for MDAC Version 2.1: http://www.microsoft.com/data/download_21242023.htm |
If WebSphere or its Web servers are running during the time of installing the Fix Pack, you will get errors. | All | To avoid errors, follow these steps:
|
When installing the Fix Pack on a machine with only the administrative console, it will not update. | Windows NT | Copy the admin.config file from a WebSphere machine and put it under |
WebSphere does not recognize multiple instances of IIS. It only recognizes the default instance. | Windows 2000 | Create two virtual directories in the second instance of IIS (IBMWebAS, sePlugins). Make these virtual directories identical to the first instance of IIS. Both virtual directories in both instances should be identical. You can do this for as many IIS instances you have. |
If you select the Lotus Domino plug-in during WebSphere Application Server installation, the new DSAPI filter is not enabled by default. | All | The new DSAPI filter file names, depending on the platform, are as follows:
Use the following steps to enable the new DSAPI filter. (These steps assume Solaris is the example operating system, but you can use the same steps on other operating systems).
|
In article 1.2.3.2.3 the section entitled "Setting up the administrative database in DB2/390" mentions that sample JCL can be found in the installation directory but does not specify where. | All | The db22390.sql JCL file is located in the bin directory. |
Unable to start the WebSphere Administrative Server with the
following message (Sybase): com.sybase.jdbc2.jdbc.SybSQLException: User name EJSADMIN does not exist in sysusers | All | When using a schema other than EJSADMIN with Oracle and Sybase, you need to
specify the following in admin.config: com.ibm.ejs.sm.adminServer.dbSchema= There are two important points to remember:
|
After uninstalling the Fix Pack, and trying to reinstall the same Fix Pack, your machine detects that the Fix Pack is still installed. When trying to exit, you are not able to, and the JDK is automatically updated. | All | After uninstalling the Fix Pack, delete the backup jar files and the uninstaller of the Fix Pack. |
During the WebSphere Application Server installation, the following error displays: ERROR-FUNCTION-entry not found on string table because you are missing a file "lodctr.exe" in the WINNT/SYSTEM32 directory. | Windows NT | WebSphere automatically installs IHS and, when this error occurs, the silent
install will stop and the WebSphere install will continue. IHS does not copy all of its needed files to the hard
drive of the machine, therefore it won't run at all. This may happen if you don't have IHS on your
machine and you install Full, Quick or Custom install with IHS.
To fix this: |
When installing WebSphere, if you are using a Web server or database that exceeds WebSphere's current required version of Web server or database, the pre-req checker runs and displays a message that you can't install with versions other than the required versions. | All | On Windows NT, click OK and continue.
On Solaris and AIX, you must cancel the install or choose the default version of the Web server or database. To avoid the problem, disable the pre-req checker. This is done by going to the pre-req.properties in the install files and changing prereq_checker=1 to prereq_checker=0 (line is in [WAS] block at top of the file). |
A new property was introduced in Fixpack 3. | All | There is a new property that can be added in the admin.config
file located in the bin directory of the WebSphere Installation directory. Example file location: c:\WebSphere\AppServer\bin\admin.config The property name is: com.ibm.ejs.sm.adminServer.dbInitialized=true If the admin.config file has the new "com.ibm.ejs.sm.adminServer.dbInitialized=true" entry the WebSphere Repository database tables will not be created. On subsequent stop and start of the administrative server, the AdminServer.java will verify whether this parameter is present in the admin.config file, and if the parameter is not present, the database tables are created if necessary. Note: If the WebSphere Administrator Server database is dropped after this property is added to the admin.config file, database exceptions will occur. To rebuild the database follow the steps below:
Note 2: Development and service frequently drop the WebSphere administrator database. It is obvious that the above entry has to be removed from the admin.config file in order to recreate the repository tables. Setting com.ibm.ejs.sm.adminServer.dbInitialized=false in the admin. confile file will not recreate the tables. Before recreating, the whole entry (com.ibm.ejs. sm.adminServer.dbInitialized=true) should be removed from the file. |
The admin.config entry com.ibm.ejs.sm.adminServer.dbInitialized=true (or false) is not present in the admin.config file after installing the base GM code and Fix Pack 3, and starting the server and adminclient. | All | If the admin.config file has the "com.ibm.ejs.sm.adminServer.dbInitialized=true" entry
(after initializing the database), the database tables will not be recreated.
On subsequent stop and start of the administrative server, the AdminServer.java will verify whether this parameter is present in the admin.config file. If the parameter is not present, the database tables are created. Thus, make sure this parameter is set in the admin.config file. Note: Development and service frequently drop the WebSphere Application database. It is obvious that the above entry has to be removed from the admin.config file in order to recreate the tables. Setting com.ibm.ejs.sm.adminServer.dbInitialized=false in the admin.config file will not recreate the tables. Before recreating, the whole entry (com.ibm.ejs.sm.adminServer.dbInitialized=true) should be removed from the file. |
When migrating from Version 3.02 to Version 3.5, Version 3.02 configurations are lost. | All | Before migrating from Version 3.02 to Version 3.5, you must migrate any application files first.
See InfoCenter article 3 for more information. Step 2 of the instructions tells you to migrate or upgrade to IBM WebSphere Application Server 3.5. You need to migrate, then upgrade. Follow steps 3-5 for migration, then go ahead with your upgrade. |
Using the "Programs" to uninstall WebSphere Application Server causes problems. | All | To uninstall WebSphere Application Server, use the Uninstall option.
For Windows NT, select Start->Programs->IBM WebSphere->Application Server Version 3.5->Unistall WebSphere Application Server. On Unix, execute the uninstall.sh script which is located in the WebSphere root installation directory (e.g./opt/WebSphere/AppServer). Other uninstall tips:
|
The exception NoSuitableDriver is displayed when you install
WebSphere Application Server using Oracle, Sybase or IDB as the WebSphere Application Repository.
The exception occurs when you use DataSource to access the DB2 database for application data by choosing the DataSource for Connection Pooling function or enterprise bean. |
AIX, Solaris | Set up the DB2 environment properly in the WebSphere Application Server
startupServer.sh if you plan to refer to Oracle, Sybase or IDB databases as administrative databases. To modify startupServer.sh, find the following line in startupServer.sh in a then clause: export LD_LIBRARY_PATH Next, add the following lines BEFORE the export LD_LIBRARY_PATH line: DB2_INSTANCE_HOME=/export/home/db2inst1 export DB2_INSTANCE_HOME .$DB2_INSTANCE_HOME/sqllib/db2profile LD_LIBRARY_PATH=$DB2_INSTANCE_HOME/sqllib/java12:$DB2_INSTANCE_HOME/sqllib/lib:$LD_LIBRARY_PATH LIBPATH=$LD_LIBRARY_PATH export LD_LIBRARY_PATH LIBPATH For $DB2_INSTANCE_HOME, specify your DB2 instance home directory. |
The README file at the end of the installation is not displayed, and Hotjava is the default web browser. | Solaris | Make sure that the Hotjava browser can be started. If not, use another browser to view the README file. |
Java applications will not run reliably where the LIBPATH length exceeds 1548 characters. | AIX | Reduce the LIBPATH length to less than 1548 characters. |
The Apache server will not start after installing the WebSphere Application Server plug-in for Apache server. | All | The plug-in installation added the
line ose.mode=out to your Apache configuration file srm.conf in the /<apache_home>/conf directory.
Open an editor on the srm.conf file, and remove
or comment out the ose.mode=out line. |
Connection is refused (error 500) when attempting to access servlets and JSP files.
The Web server and application server are under stress and the Web server log contains the following errors: Aug 30 14:52:53 1999 - Error ws_open_domain_client_socket connect return 146 error Mon Aug 30 14:52:53 1999 - Error Ws_open_domain_client_socket socket return 146 error |
Solaris | The default communications configuration between
the Web server and the servlet engine is using TCP/IP sockets. Each socket
represents a file descriptor. If the file descriptor limit per process is
set too low, attempts to open socket connections might be refused (error 146).
To resolve this condition, increase the file descriptor limit for the user from which the administrative server is started (ususally root). Edit the .profile for the user, and add the following: ulimit -n 1024 Depending on the number of connections needed, this number may need to be increased more. For this change to take effect, log off and then log on. To change the hard upper limit of the number of file descriptors in the kernel (which defaults to 1024 per CPU), you can edit the /etc/system config file to include a couple of entries: set rlim_fd_max=4096 set rlim_FD_cur=1024 After you save the file, restart the machine for the changes to take effect. |
Using Oracle, the following message displays, TransactionRolledBackException, when attempting to create a model. | All | Increase values of Oracle database initialization parameters open_cursors to 200. See the WebSphere Application Server InfoCenter "Configuring Databases" section for details. |
WebSphere Application Server installation fails even though you are logged in as root. An error is displayed that states the user does not have root authority. | Solaris | Ensure the "whoami" command or /usr/ucb is in the path for the root logon. |
The IBM HTTP Server will not install.
There are bad entries in the system file table: /etc/fstab. The swinstall fails in the analysis phase because the mount_all_file_systems option is true by default. |
HP-UX | Remove the bad entries from the /etc/fstab file and reinstall. If you cannot do so, edit the install_ihs_128.sh (or install_ihs_56.sh), adding the -x mount_all_file_systems=false option to the swinstall command. |
The install directory for DB2 7.1 has changed (x:\Program Files\SQLLIB) and
WebSphere Application Server Version 3.5 defaults to the old DB2 directory (x:/sqllib). The following
error displays when WebSphere Application Server is started: 2140:An internal Windows NT error occurred |
All | Check to make sure that the admin.config file is pointing to the new DB2 directory (x:\Program Files\SQLLIB). Otherwise the default will point to the old directory (x:/sqllib). Modify the admin.config pointer to the DB2 driver if you have already installed and tried to start WebSphere Application Server and are getting the error. |
Problem | Op System | Workaround |
---|---|---|
The WebSphere Application Server, when using
DB2, does not start and the following error displays: FATAL Failed to create a data source: {0} COM.ibm.db2.jdbc.app.DB2Exception: [IBM][CLI Driver] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 | All | Create the WebSphere Application Server database. On Solaris and AIX, run the shell file createdb2.sh. On Windows NT, the script is started automatically after you reboot. If the script file fails, start the database, then run the createdb2.bat file. The results are logged in the wasdb2.log file. |
The administrative server fails to start.
The failure is related to the lack of a new line character at the end of the wasdb2.log file. |
All | Add a newline character to the end of the admin.config file located in the bin directory under the product installation root ( such as C:\WebSphere\AppServer\bin\admin.config or Windows NT). |
The administrative server/application server runtime is running as non-root.
When running a servlet, the following message displays from the browser: |
AIX | See InfoCenter article 1.2.2.6 for the correct way to run as non-root. |
The administrative server is running as non-root on Solaris and the following error message displays: $ ./startupServer.sh operation failed,Not owner |
Solaris | Install Websphere as root user with the following steps:
|
The thin servlet redirector configuration cannot be run when you are logged in other than as root. | Solaris, AIX, HP-UX | Thin Servlet redirector configuration runs only when you log in as a root.. |
You have trouble starting a secured (that is, security is enabled) administrative server or an application server on a Windows machine configured as a part of a Windows domain and not connected via the network to the domain server. | Windows NT/2000 | Configure the Windows NT/2000 machine so that it is not part of a Windows NT/2000 domain. |
The IBM HTTP Server will not start when you attempt to add
a module using the Module Sequence form.
The following error message Invalid command 'LoadModule' displays and the server may not restart. |
All | Using the Module Sequence form added unwanted commands to the IHS httpd.conf file.
Edit the file and remove the following commands: |
Problem | Op System | Workaround |
---|---|---|
The administration of an WebSphere Application Server administrative domain will not properly work if all nodes within the domain are at different FixPak levels of a release. | All | WebSphere Application Server administrative domain requires that all nodes be at the same FixPak level for the administration of the domain to properly work. |
In a configuration with one node run as an administrative agent and another node as the administrative server, if the installation directory on the agent node is not the same as the installation directory on the administrative server node, starting an application server fails. | All | In the admininistrative console, edit the properties for the RemoteSRP bean under the Default Container of the administrative agent node so that the "Jar File" property specifies the correct path to the ibmwebas.jar (e.g. C:\WebSphere\AppServer\lib\ibmwebas.jar) |
When starting the Administrative Console, the following error stating that
the maximum number of open cursors is exceeded displays: 5803af6d DBMgr W Exception on database query: "select * from ejsadmin.REL_DEFN_TABLE where SOURCE_TYPE = ? or TARGET_TYPE = ?" com.ibm.ejs.cm.portability.ResourceAllocationException: ORA-01000: maximum open cursors exceeded at java.sql.SQLException. at com.ibm.ejs.cm.portability.PortableSQLException. at com.ibm.ejs.cm.portability.ResourceAllocationException. at java.lang.reflect.Constructor.newInstance(Native Method) at com.ibm.ejs.cm.portability.PortabilityLayerImpl.translateException(PortabilityLayerImpl.java:139) at com.ibm.ejs.cm.pool.ConnectO.translateException(ConnectO.java:861) at com.ibm.ejs.cm.proxy.ConnectionProxy.translateException(ConnectionProxy.java:84) at com.ibm.ejs.cm.proxy.OracleConnectionProxy.prepareStatement(OracleConnectionProxy.java(Compiled Code)) at com.ibm.ejs.sm.util.db.DBMgr.executePreparedQuery(DBMgr.java(Compiled Code)) at com.ibm.ejs.sm.beans.RelationBean.ejbFindByEndpoint(RelationBean.java:1033) at com.ibm.ejs.sm.beans.EJSRelationHomeBean.findByEndpoint(EJSRelationHomeBean.java:161) at com.ibm.ejs.sm.beans.EJSRemoteRelationHome.findByEndpoint(EJSRemoteRelationHome.java:170) at com.ibm.ejs.sm.beans._RelationHome_BaseStub.findByEndpoint(_RelationHome_BaseStub.java:371) at com.ibm.ejs.sm.beans._RelationHome_Stub.findByEndpoint(_RelationHome_Stub.java:374) at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getRelationships(RepositoryObjectImpl.java:1079) at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getModelRelation(RepositoryObjectImpl.java:1119) at com.ibm.ejs.sm.beans.RepositoryObjectImpl.isAClone(RepositoryObjectImpl.java:1318) at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getModelName(RepositoryObjectImpl.java:1342) at com.ibm.ejs.sm.beans.ServerBean.initializeConfig(ServerBean.java:564) at com.ibm.ejs.sm.beans.EJBServerBean.getConfig(EJBServerBean.java:183) at com.ibm.ejs.sm.beans.ServerBean.getActiveAttributes(ServerBean.java:1038) at com.ibm.ejs.sm.beans.ServerBean.readInstanceVariables(ServerBean.java:1004) at com.ibm.ejs.sm.beans.ServerBean.getAttributes(ServerBean.java:81) at com.ibm.ejs.sm.beans.EJBServerBean.getAttributes(EJBServerBean.java:122) at com.ibm.ejs.sm.beans.EJSRemoteEJBServer.getAttributes(EJSRemoteEJBServer.java:245) at com.ibm.ejs.sm.beans._EJSRemoteEJBServer_Tie._invoke(_EJSRemoteEJBServer_Tie.java:452) at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:505) at com.ibm.CORBA.iiop.ORB.process(ORB.java:2261) at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java:195) at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java(Compiled Code)) All |
To fix this problem: |
|
When the administrative console is downloaded from the Internet it doesn't run. | All | A JDK has to be present on the machine using the remote console. And/Or set the JAVA_HOME. And/Or put the JDK location in the PATH. |
Issuing a command such as % ./wscp.sh -c "ApplicationServer list" results in the following error being displayed: An action to perform on ApplicationServer must be specified. | AIX, Solaris, HP-UX | The argument quoting is being lost by one of the shell scripts involved in executing the
command -- wscp.sh and/or the script referenced by the JAVA_EXE environment variable. Check these scripts to ensure they use "$@" (i.e. the quotes are required) in order to preserve the argument quoting. |
In the HTTP Administrative Console, the Web application property sheet does not show up with the Netscape browser. | Windows | Use Microsoft Internet Explorer as your browser. |
The WebSphere Control Program (WSCP) command line uses Tcl. The Tcl variable is "errorCode" when command line commands are executed.The Tcl variable "errorCode" is used to store the result of a Tcl command that fails. The translation of a non-zero error message is no longer displayed. |
All | Previously, if a nonzero error occurred (and the Tcl interpreter's result string was not set), the translation of the error message was displayed. Now, both interactive users and script writers must check the errorCode variable to determine whether a command succeeded or failed. |
The Java administrative console is not displaying correctly after installing the product. You did not install the Java administrative console while installing the product and used adminclient.bat to view the Java administrative console. The Topology view shows green 'objects' listed, but they are not valid objects. They appear to be EJB-related methods. | Windows NT/2000 | Uninstall WebSphere Application Server and reinstall, including the Java administrative console. An alternative is to install the administrative console on a remote machine, which can be used to administer the remote administrative server. |
The Web-based browser administrative console is unavailable if the default server is stopped. | All | The Web administrative console runs under the default server. Stopping the default server makes the HTTP administrative console unavailable. Start the default server and then try restarting the HTTP administrative console. |
Screens are not repainting or resizing properly when running
the Java administrative console changes on a UNIX operating system with the Display
exported to a Windows NT/2000 system running a Hummingbird Exceed 6.0.1 X Windows
server. The window appears to be empty or missing panes. When you manually resize the window, the rest of the text and widgets are displayed. | Windows NT/2000 | Do one of the following:
$WAS_HOME/bin /adminclient.bat <remoteHostName> Window Manager: Window Manager = Native Use Native WM for embedded clients = No First Window to display = No Note: Hummingbird Exceed Version 6.2.0.18 and higher will also work. Follow the above instructions for configuring the window manager. Exceed requires a patch to work. Without the patch, windows are incorrectly sized. With the patch, some of the error and message dialog boxes still have clipped edges, so you need to manually resize these windows. Contact Robek Corporation for a patch to get to Exceed Version 6.2.0.18 or higher. To determine the Exceed patch level you need:
See InfoCenter article 1.2.2.4.1.1 for many more tips and instructions. |
Resizing the left panel of the Java administrative console causes the panel to become squashed and then cannot be resized. | All | Click the Topology view, then resize the left panel. |
The XML import feature of the Java administrative console does not completely handle security configurations. | All | Instead of the Java administrative console import, use the XMLConfig
command line utility for security configurations that include passwords.
The background for this recommendation is as follows: This adversely affects security, which requires the variable substitution feature of XML import to replace password variables in the XML file with actual values. Instead, password variables are exported and are expected to be replaced during import.This would limit password exposure to a single time while invoking the import command. Security configuration areas affected by this password limitation include administrator access, LTPA, LDAP, and enterprise application identities. |
The .wscprc file does not load when the WebSphere Control Program (WSCP)is invoked. | All | The Java property user.home is used to locate
the .wsprc file. Check the value for user.home and ensure that the .wscprc
file is located in the directory designated by user.home.
Optionally, when
you invoke WSCP, use the -p option to specify the user.home directory
and, thus, the location of the .wscprc file: Note: The user.home directory may differ among JDK version levels and platforms. On Windows NT/2000, the JDK 1.2.2 sets the user.home property based on the value of the USERPROFILE environment variable. |
After using the Java administrative console to delete a resource and create the resource again, the change is not immediately reflected in the WSCP. | All | To avoid problems due to inconsistent cached
information, avoid issuing concurrent operations on the same object from
within the WSCP and the console.
If you encounter the described problem, explicitly refresh all object references in the repository cache by issuing a "wscp list" operation for the object type of the instance. Alternatively, exiting and re-invoking the WSCP also refreshes the cache. |
After installing WebSphere Application Server, you elected to install the default configuration, and the fully-qualified domain name (FQDN) is not included in the Alias Host list of the default_host Virtual Host. Access by http://<FQDN>/servlet/snoop may fail. | All | Add a virtual host alias for the fully-qualified domain name (FQDN)
of your machine running the Web Server. The short name is automatically defined, but
some systems do not automatically define the FQDN:
|
Problem | Op System | Workaround |
---|---|---|
When a database does not support FOR UPDATE clause and
the following access pattern is frequent, deadlocks could occur in the database. | All | Transaction 1: Select * from tb1 where id=1 Select * from tbl2 where id=2 ---------------------------- x Update tbl2 .. where id = 2 Update tbl1 ... where id=1 Transaction 2: Select * from tb1 where id=1 Select * from tbl2 where id=2 ----------------------------- x Update tbl2 .. where id = 2 Update tbl1 ... where id=1 If both transactions are at point x, then both have obtained read locks on data item represented by id=2. Now neither transaction can upgrade to write locks necessary to execute the next update statements. Usually, the database detects the deadlock and aborts one transaction. FOR UPDATE clause on select statements allows us to obtain a write lock while executing the select statement before point x and prevents the deadlock. |
While configuring the Resource Security to an existing Enterprise application a HotSpot Virtual Machine Error might occur while adding a clone of an Enterprise Java Bean. This will cause your administrative server to restart. | HP-UX 11.0 (Advanced Custom Configuration) | Disabling the HotSpot compiler will resolve the issue. This can be done by removing the HotSpot compiler from the runtime path. For example: mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot.bak mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot.bak |
The following error displays when trying to deploy specific beans
within a jar file: Drive, com.transarc.systest.ejs.webpennies. EJBCount does not exist. Please verify the appropriate drive was given. Note: "Webpennies" and "EJBCount" in the above error message is the application used for testing. | Solaris, AIX, Linux | The error occurs when you try to deploy only one entity bean stored within a .jar file.
Select the entire *.jar file for deployment. You are then given the option to click Yes to deploying all the entity beans within the file. |
JNDI lookup EJBHome fails to return org.omg.CORBA.Object instance. Try: { tmpObj = ic.lookup ("V3Phone"); } catch (NamingException ne) { System.out.println("MyPhoneBookServlet FAILED to lookup \"EmployeeBean\":"); ne.printStackTrace(); } if (tmpObj instanceof org.omg.CORBA.Object) phoneHome = (V3PhoneHome)javax.rmi.PortableRemoteObject.narrow(tmpObj,V3PhoneHome.class); System.out.println("after phoneHome narrow" + phoneHome): Above println prints null for phoneHome because tmpObj is not an instance of a rg.omg.CORBA.Object. |
All | Comment out the condition //if (tmpObj instanceof org.omg.CORBA.Object) |
The required attributes of an enterprise bean include the DeploymentDescriptor and JarFile attributes. The DeploymentDescriptor has a new format. | All | The attribute value must be a string that includes the remote interface
name, a JAR file, and the node name, each separated by the @ symbol. The
syntax is as follows: bean_remote_interface [ @jar_file ] @node_name ] ] Where bean_remote_interface is the name of the bean's remote home interface, jar_file is the full path name of the JAR file on the node for which the enterprise bean is being defined, and node is the name of the node where the enterprise bean is being created. The JAR file and the node name are optional, and are automatically supplied if they are not specified. The value for jar_file is taken from the value of the JarFile attribute. The value for node name is extracted from the fully-qualified name of the enterprise bean. |
There is no BLOB or CLOB support for WebSphere Application Server Version 3.5 on HP using DB2 with Container Managed Persistence (CMP). | HP-UX | Any CMP bean which is to be run on the HP platform with DB2 as its persistent store CANNOT designate a Serializable object type as a CMP field. |
Some enterprise beans request more database connections on DB2 than are configured for the database, resulting in trap errors on 8-way Windows NT systems. | All | |
Enterprise bean clients are unable to interpret server-side exceptions in stack traces. | All | Enterprise bean clients must have access to server-side exception classes to interpret server-side exceptions in stack traces. Examine the server-side trace logs for the complete error information or make server-side classes available on the client. |
When trying to view a distributed transaction, the transaction monitor will not display and, if you persist in trying to access the transaction monitor, the Java administrative console hangs. | All | To stop the console from hanging, restart the administrative console. However, you still will not be able to access the transaction monitor. |
The Jetace tool displays this message when loading a JAR file: java.lang.NoClassDefFoundError |
All | When using the Jetace tool, make sure all dependent
classes (and dependencies those classes have) are on the classpath. See InfoCenter article 6.3 for guidance. |
The documentation regarding writing enterprise beans with bean managed persistence (BMP), located in "Chapter 9: More-advanced programming concepts for enterprise beans" in the PDF file adswpg00.pdf and in the HTML file atswpgad.htm, is incorrect. | All | In Figure 64, the lines: getEnvProps(); ds = initContext.lookup("jdbc/sample"); should be in the setEntityContext method (similar to Figure 61) rather than in the constructor. This is because the getEnvProps method needs the context to be set which is not yet set in the constructor. Since the container invokes the setEntityContext method to set the context, the other two methods, getEnvProps and lookup, can be safely done there. |
Because of application programming practices, an application getting an enumeration of objects from an enterprise bean gets fewer than the expected number of objects. | All | Whenever possible, invoke entity bean finders
and the iteration through a resulting enumeration within a single transaction.
Some benefits are:
If an entity bean finder is invoked within one transaction (for example, a transaction which a client started via UserTransaction or from a TX_REQUIRED session bean method), the resulting enumeration must be consumed within the same transaction. The result of a finder becomes invalid once the transaction completes. The following is an example of finder usage which does not meet the above
requirement:
The code should be rewritten as follows:
UserTransaction TX = ...; |
Data in non-persisted fields of an entity bean is not maintained across transactions. | All | Entity beans should not rely on data stored in non-persisted fields (particularly, references to other beans) being maintained across multiple transactions. Entity bean instances are stored in an object pool between transactions. Each time a new transaction begins, it retrieves one of the entity bean instances in the pool and loads persisted data for the requested bean. Non-persisted fields may contain values set by a different bean used previously. If necessary, you can reinitialize the data in the non-persisted field in the bean's ejbLoad() method. |
In an inheritance hierarchy involving CMP beans,
using the results of an enumerated finder outside the transaction the finder
was run in may lead to results which violate the inheritance behavior. The
behavior may be described by the following scenario:
Consider an inheritance hierarchy involving the CMP beans Bean P (Parent) and Bean C (child). Assume that there is one instance of P (P1) and one instance of C (C1). An enumerated finder on P will return P1 and C1. However, attempts to use C1 outside the transaction in which the finder was run would result in its behaving like an instance of P (ie, the methods would have P's behavior, not C's behavior). |
All | Clients should start a transaction before running enumerated finders on CMP hierarchies, and should use the results of the finder within the same transaction. If this is done, using the scenario on the left, attempts to use C1 will demonstrate C's behavior, as expected, instead of P's behavior. |
Problem | Op System | Workaround | Dynamic tracing from the Java administrative console (Console->Trace->Enabled) on a Windows NT workstation does start properly with javaw. | Windows NT | Edit the adminclient.bat file and make the following modification: Change javaw to java in the following line:
|
---|
WebSphere Application Server Version 3.5 supports the locales listed in the table below. The support is dependent on the availability of the TrueType fonts listed for the respective languages.
Language | Windows NT/2000 | Solaris | AIX | HP-UX |
---|---|---|---|---|
Brazilian Portuguese | IBM-850 | pt_BR | pt_BR.ISO8859-1 | No Brazilian Portuguese locale |
French | IBM-850
IBM-858 |
fr
fr.ISO8859-15 |
fr_FR.ISO8859-1
fr_FR.ISO8859-1@euro |
fr_FR.ISO8859-1
fr_FR.ISO8859-15@euro |
German | IBM-850
IBM-858 |
de
de.ISO8859-15 |
de_DE.ISO8859-1
de_DE.ISO8859-1@euro |
de_DE.ISO8859-1
de_DE.ISO8859-15@euro |
Italian | IBM-850
IBM-858 |
it
it @ISO8859-15 |
it_IT.ISO8859-1
it_IT.ISO8859-1@euro |
it_IT.ISO8859-1
it_IT.ISO8859-15@euro |
Japanese | IBM-943 | ja
ja_PC.PCK |
ja_JP.IBM.eucJP
Ja_JP.IBM-942 |
ja_JP.SJIS * |
Korean | IBM-1363 | ko | ko_KR.IBM.eucKR | ko_KR.eucKR * |
Simplified Chinese | IBM-1386 | zh | zh_CN.IBM.eucCN | zh_CN.hp15CN * |
Spanish | IBM-850
IBM-858 |
es
es @ISO8859-15 |
es_ES.ISO8859-1
es_ES.ISO8859-1@euro |
es_ES.ISO8859-1
es_ES.ISO8859-15@euro |
Traditional Chinese | IBM-950 | zh_TW
zh_TW.big5 |
zh_TW.big5 | zh_TW.big5 * |
Problem | Op System | Workaround |
---|---|---|
All Languages | ||
National language documentation sets in the full InfoCenter (other than the English set) contain known problems or limitations that are addressed in the English version of that documentation. Because some information was translated to languages other than English before the product was completed, the English version of the documents contain some corrections and additions which are available with the product but not yet translated. | All | These additions and corrections to the documentation
set will be translated and made available in other languages
after general availability of the WebSphere Application Server
product.
If you are using a national language version of the documentation other than English, check the product Web site Library page for information about obtaining a refreshed version in the language of your choice. Also, consider periodically referring to the English documentation set in the InfoCenter in addition to the language set you installed. See InfoCenter article 0.0.7 for a full account of the differences between English and translator versions. |
The word "True" is displayed in English on the Default Model Properties page in the Administrative Console. | All | Ignore the appearance. |
Installing WebSphere Application Server in more than one causes the different language versions to overwrite each other. Also, with native install (using SMIT), when more than one language is installed, an error displays. | AIX | The installation should allow you to install
more than one language and switch between languages. Currently, because
all of the languages are named the same in the same installation path, they
overwrite each other. Install only one language of WebSphere Application Server on AIX. If you need to install a different language, uninstall the previous language before installing the one desired. |
The Cancel button in uninstallshield does
not work. When you click Cancel in uninstallshield, the executable loops and the uninstallshield automatically reloads. |
AIX | To cancel the uninstall, press Ctrl+C at the command prompt in the shell from which the uninstall program was initiated. |
Brazilian Portuguese | ||
The time displayed with events on the administrative console is one hour earlier than the actual system time. | Windows NT/2000, AIX, Solaris | |
Japanese | ||
Japanese characters are distorted on the following
installation panels:
|
AIX |
|
When you install WebSphere Application Server on the Japanese Solaris operating system, the dialog on which you select the database home directory (DB_HOME) does not display the directory entry. startupServer.sh and admin.config are not updated. | Solaris |
|
Java administrative console pages do not display properly for Japanese AIX customers using the eucJP locale. | AIX | You will need to change some text files: If you see pages in the AdminConsole containing lots of ???????????????, install Japanese WebSphere on AIX. If ja_JP locale
is used, the following .txt files in the /web/help directory need to be
converted with the command (on one line): |
Spanish | ||
When using the Types tab, then selecting Model and create, and then choosing Application server, the properties window is initially too small. The right side of the window is cut off by about five characters. | AIX | Manually resize the window. |
Chinese Simplified | ||
On AIX V4.3.3:
|
AIX | Fix Pack U466148 is available on the 4.3.5 installation media. It is not necessary to upgrade the operating system to 4.3.3 to install this Fix Pack. |
Chinese Traditional | ||
Problems with character sets other than BIG5 on AIX V4.3.3. | AIX | WebSphere Application Server only supports the BIG5 Traditional Chinese Character Set for AIX V4.3.3. |
While using the product, corrupt panels and code page conversion errors appear. | Solaris | To install and use the WebSphere Application
Server with a minimal amount of corrupted panels, follow the procedure
below:
To uninstall WebSphere Application Server with a minimal amount of corrupted panels:
|
All Double-Byte Languages | ||
In the WebSphere Administrative Console, Asian characters show up as empty boxes. | HP-UX | The Java swing libraries require TrueType fonts. HP-UX does not provide
these fonts for Asian languages. The SDK release notes state that HP-UX is working to provide these fonts
in the future. In the meantime, Japanese, Korean, Chinese Traditional,
and Chinese Simplified customers must purchase their own TrueType fonts
from a third party vendor. They can also force the WebSphere Administrative
Console to run in English by running the following command from the command
prompt before starting the WebSphere Administrative Console: export LANG=en_US.iso88591 Also, for more information on this limitation, refer to the (HP-UX SDK Release Notes). |
Double-byte server name is corrupt in console messages. If you name a server with Asian-Pacific characters and start it, the name in the status message (starting, stopping) on the Administrative Console is garbage (question marks and square blocks). | All | Use only English characters and numbers for your server name. |
An application server will not start if named
with more than three Chinese characters. With more than three Chinese characters, the name in the status message (starting, stopping and others) is made up of meaningless characters (for examples, question marks and square blocks). |
All | Any combination of less than three Chinese characters or any number of English characters works fine. Use English or fewer than three double-byte characters. |