Defect Resolution
 

Installation

[Home]

Defect		Reference Number: PQ36342
Category:	Installation	PTF No.: WAS 3.0.2.1
Brief Description:	Installation of WebSphere Application Server causes a core dump on the IBM HTTP Server when the Java process is intiailized.
Platforms:	Solaris
Resolution		Status:[Resolved]
Now you can start the WebSphere Application Server without affecting the IBM HTTP Server.

 

Defect		Reference Number: 71791
Category:	Installation	PTF No.: WAS 3.0.2.1
Brief Description:	Uninstallation of WebSphere Application Server (128-bit) Advanced Edition fails in Solaris.
Platforms:	Solaris
Resolution		Status: [Resolved]
Uninstall program and its properties are updated. You can now uninstall the WebSphere Application Server with PTF 1 of the 3.02 Release for Solaris seamlessly.

 

Defect		Reference Number: 71821
Category:	Installation	PTF No.: WAS 3.0.2.1
Brief Description:	Did not find ‘classes’ directory under the WebSphere Application Server root directory.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Installing WebSphere Application Server automatically creates the classes directory under the WebSphere Application Server root directory ([WASRoot]). Now you can place your class files in the [WASRoot]\classes

 
 

Administration

[Home]

Defect		Reference Number: 72093
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	It was not possible to modify the Jar file attribute in the EJSConsole, because it was disabled.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The Jar file attribute in the EJS Console is now enabled, and you can modify the attributes of the Jar file.

 

Defect		Reference Number: 72252
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	Starting the Administrative Server as a service in Windows NT using the net start command line gives an erroneous message that the start failed.
Platforms:	NT
Resolution		Status:[Resolved]
You can start the Administrative Server using the net start command line without error messages.

 

Defect		Reference Number: 72304
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	If there is a full service administrative server and an administrative agent, and both have application servers with servlet engines and webapps in them, changing the webapp classpath for one changes it in the other.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now you change the classpaths in the local application server and the remote application server independently.

 

Defect		Reference Number: 72873
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	A Web application cannot be configured to be rooted at "/" and have a servlet, JSP, or static HTML with a Web path of "/". Attempting to do this results in a "URL already exists error"
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You can now have a "/" in both a Web application and another single instance of a configured resource.

 

Defect		Reference Number: 73345
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	The values being specified in the GUI for the in memory size for sessions is getting lost.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now the memory size you specify using the WebSphere Administrative Console display does not get lost and remains visible.

 

Defect		Reference Number: 73422
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	It is not possible to add a bean model to a container model when the clone is in running state.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now you can add bean models to container models using the EJS console.

 

Defect		Reference Number: 73758
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	It is not possible to add more than 30 entries in the host alias table list on the default host(or any other virtual host).
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
This problem is resolved.

 

Defect		Reference Number: 77181
Category:	Administration	PTF No.: WAS 3.0.2.1
Brief Description:	Running a database servlet using an id that is different from the one that was used to create the SAMPLE database in DB2,  gives a database error.
Platforms:	NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The database servlet has been modified so that it does not depend on any tables being present in the SAMPLES database. Now you can run the servlet from any userid.

 
 

Security

[Home]

Defect		Reference Number: PQ36188
Category:	Security Support	PTF No.: WAS 3.0.2.1
Brief Description:	The cipher suite value which indicates the strength of SSL encryption being used is not extracted properly by a Netscape plugin.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You can now get the correct strength of SSL encryption through the Netscape plugin

 

Defect		Reference Number: 74134
Category:	Security Support	PTF No.: WAS 3.0.2.1
Brief Description:	When WebSphere Application Server security is enabled with LTPA authentication mechanism, there might be authentication and authorization failures experienced when concurrent users access a secured resource (or multiple secure pages in a frameset).
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Implementation is changed to handle concurrency issues.

 
 

Web Server Interface

[Home]

Defect		Reference Number: 73878
Category:	Web Server Interface	PTF No.: WAS 3.0.2.1
Brief Description:	HTTP 1.0 requests fail with the IBM HTTP Server plugin when no "host" header is supplied.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You can now issue a request with no "host" header. The localhost is used in that case.

 

Defect		Reference Number: 73964
Category:	Web Server Interface	PTF No.: WAS 3.0.2.1
Brief Description:	Set-Cookie header was not working when two or more cookies were set on Netscape.
Platforms:	Solaris
Resolution		Status:[Resolved]
Now this works properly.

 
 

Servlet Support

[Home]

Defect		Reference Number: 71061
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	If the servlet redirector has to route the service to a different node other then the node where the Web server is, and if the Web server is running on non-default port, one extra entry in the host alias table has to be made without the port specified (in addition to the entry that contains the host and non-default port). Otherwise, service request from browser fails.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now you can successfully execute this scenario without adding the extra entry in the host-alias table.

 

Defect		Reference Number: 72123
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	HttpServletRequest.isRequestSessionIdValid() returns false, if HttpServletRequest.getSession(false) call is not made.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You can invoke the HttpServletRequest.isRequestSessionIdValid() method to investigate the validity of the session object before calling the getSession().  It returns "true" if the request object has a valid session.

 

Defect		Reference Number: 72284
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	Servlet redirector does not work when it is configured on an administrative agent node.
Platforms:	AIX / Solaris / HP-UX
Resolution		Status:[Resolved]
An administrative agent is an administrative server that does not have its own administrative respository. The administrative server is acting as an agent. It is configured to connect to another adminiatrative server that does have its own administrative repository. An administrative agent differs from a regular administrator server in the following ways: 1) An administrative agent has no direct connection to the repository database. It relies on the "full-service" administrative server to which it is connected to perform all tasks. The administrative agent resources appear in the WebSphere Administrative Console under a different node than the "full-service" resources.  2) A WebSphere Administrative Console cannot connect to an administrative agent. It must connect to a regular, "full-service" administrative server.  3) An administrative agent does not contain a name service, but delegates this task to the "full-service" administrative server that it is connected to for this function. An administrative agent is configured so that the values that are specified for the administrative.bootstrapHost and administrative.bootstrapPort properties are as follows:      a)   com.ibm.ejs.sm.adminServer.bootstrapHost is the host name of the Windows NT or other system on which the "full-service" administrative server is running.       b)   com.ibm.ejs.sm.adminServer.bootstrapPort is the bootstrapPort value that is specified in the admin.config file for the "full-service" administrative server.

 

Defect		Reference Number: 72834
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	destroy() method is not called on the servlets loaded using the invoker when the servlet engine is shutdown.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now the destroy() method is properly called when the servlet engine shuts down.

 

Defect		Reference Number: 73347
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	Different maximum inactive intervals for sessions do not function consistently - If Servlet API is used to set a different maximum inactive interval (other than the default value) for the different sessions, the invalidation does not function consistently.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The Servlet API setMaxInactiveInterval() can be used to set the maximum inactive interval time for each session. The session will be invalidated consistently for each session when the session not active and its past inactive period or the session is active and is 3 times past inactive period (probably a servlet  never returns, or servlet engine dies before releasing).

 

Defect		Reference Number: 73847
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	It was not possible to add servlets to existing servlet models.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You can add servlets to existing models using the EJS console.

 

Defect		Reference Number: 74013
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	Not dumping sessions associated with the Web application when the Web application is restarted using the WebSphere Administrative Console. The WebSphere Administrative Console can be used to restart a web application.  The associated servlets will be reloaded.  All the sessions associated with the Web application are not getting dumped.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Using this fix, you can reload a modified (or the same)  Web application using the WebSphere Administrative Console safely and consistently.  All the previous sessions associated with the Web application are dumped.

 

Defect		Reference Number: 74154
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	Reloading a Web application affects the session state of other Web applications. When an Web application is reloaded, all the sessions maintained in the Web application were dumped.  In addition, sessions associated with other Web applications also were dumped.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Web applications can be reloaded safely.  Only the sessions (and all its sessions) maintained by the Web application are dumped.  The sessions maintained by the other Web applications in the server are left intact and will not be affected.

 

Defect		Reference Number: 74435
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	Servlets fail if the CLASSPATH has a directory entry, which are recursive. For example, if the CLASSPATH have the following entries: C:/WAS302/hosts/default_host/examples/servlets/deadend; C:/WAS302/hosts/default_host/examples/servlets  the servlets placed in the C:/WAS302/hosts/default_host/examples/servlets were never picked.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Your servlets can be placed in any directory and CLASSPATH updated appropriately. The CLASSPATH can also have recursive entries. For example, all servlets from the ../examples/servlets/deadend and the ../examples/servlets would be selected and picked up.

 

Defect		Reference Number: 74656
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	RequestDispatcher.forward() method does not throw an IllegalStatementException exception when output exists in the response buffer that is not committed.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
According to the Servlet API specification, you cannot call the RequestDispatcher.forward() method if you have requested for a response buffer using the getWriter() or the getOutputStream() method. The forward() method will throw an IllegalStatementException.

 

Defect		Reference Number: 74797
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	WebSphere Application Server does not support storing the session state data as a blob, since the size in DB2 for individual pieces of session data is restricted to 32700.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The maximum size of 32700 has been changed to a 2MB blob. You must drop the existing session table before restarting the application server with this fix, so that the table is recreated with the blob column.

 

Defect		Reference Number: 75396
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	For normal operation with servlet redirector, there is a special bean in the appserver that holds the servlet engine, called RemoteSRP. If this bean is renamed to any name other than "RemoteSRP", the servlet redirector cannot find it, and it stops functioning. Note that this is the actual name of the bean in the container, NOT its JNDI name.
Platforms:	Windows NT/AIX /Solaris/HP-UX
Resolution		Status:[Resolved]
The name checking should include any EJB that contains the string RemoteSRP. This should help with the cloning problem caused by the name change to RemoteSRPClone.  This will not work if changes are made to the bean without including RemoteSRP.

 

Defect		Reference Number: 75756
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	With persistent sessions, if only HttpSession.remove is called without any updates to the session, the object still shows up in the next request.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now this works correctly.

 

Defect		Reference Number: 75758
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	With multirow persistent sessions, getValueNames() frequenlty lists each attribute twice.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now this works correctly.

 

Defect		Reference Number: 76521
Category:	Servlet Support	PTF No.: WAS 3.0.2.1
Brief Description:	During some usage, the session manager would obtain a database connection of a particular session even it still had an active connection for the session (never returning the original connection).  Eventually the connection pool for the datasource depletes.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now a database connection is made only when it is needed.

 
 

JSP Support

[Home]

Defect		Reference Number: PQ33315
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	JSP include fails on Solaris with servlet redirector.
Platforms:	Solaris
Resolution		Status:[Resolved]
Now this works as expected.

 

Defect		Reference Number: PQ36698
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	If an error page is not defined in a JSP, but the error page on the webapp panel is relied on, the default error reporter is received instead of the error page.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The Web Application's error page is used if there is no JSP error page defined. If you would prefer the default JSP error page as in Version 3.02, set an initial parameter for the JSP 1.0 enabler to be "useJspDefaultErrorPage" equals "true".

 

Defect		Reference Number: 70492
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	Name collision occurs when 2 JSPs with the same name are present in different directories.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
This now works as expected. Each JSP gets compiled into a unique class regardless of its name or directory.

 

Defect		Reference Number: 72281
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	JSP fails when the “/” character appears as a part of the include filename as in <%@ include file="/index.html" %>
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
This now works as expected. Included files starting with a '/' are found relative to the document root of the Web application.

 

Defect		Reference Number: 74786
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	For both in memory and database mode, the documented transaction for HTTP session had scenarios (especially in a multipaned JSP environment) where concurrent access was allowed and data was corrupted, resulting in a series a errors and exceptions.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The concurrency issues (especially multipaned JSP environment) are resolved. Now you will get neither errors nor exceptions.

 

Defect		Reference Number: 75318
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	getProperty JSP tag inserts an extra end of line when it is inserted into the response.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
This now works as expected. The extra CR/LF was removed.

 

Defect		Reference Number: 75590
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	The JNDI attribute on the dbconnect tag follows JSP 0.91 instead of JSP 1.0
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The dbconnect tag in JSP 1.0 now supports the JNDI attribute, which allows it to use connections from a DataSource.

 

Defect		Reference Number: 75984
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	The JNDI lookup of the DataSource object is done each time a connection is made. This makes the process less efficient.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The JNDI lookup to locate the DataSource object is done only once. Using the DataSource object for connections is now more efficient (JSP0.91 and JSP1.0).

 

Defect		Reference Number: 76117
Category:	JSP Support	PTF No.: WAS 3.0.2.1
Brief Description:	The XML tags for scriptlet and expression do not  conform with JSP 1.0 spec values. <jsp:expr is used instead of <jsp:expression and <jsp:decl instead of <jsp:declaration
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Application server  now works with the JSP 1.0 spec XML tags. The previous ones (<jsp:expr and <jsp:decl) are no longer supported.

 
 

EJB Support

[Home]

Defect		Reference Number: 71557
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	ejscp would not accept attribute values which have a space in them. For example "commandline -Dfoo -Dbar" would not be accepted since there is a space between -Dfoo and -Dbar.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You now can have attribute values with spaces in them.

 

Defect		Reference Number: 72239
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	A NullPoint exception is raised on a Callable Statement method call.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now the Callable Statement method can be invoked without getting an exception.

 

Defect		Reference Number: 72573
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	Calling unbind or destroy on the JNDI Context interface causes the caller to hang and ultimately time out.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
You now can call the unbind and destroy methods without hangs.

 

Defect		Reference Number: 72742
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	When beans are deployed into a container and WebSphere security is enabled, users might see Authorization failed exception when accessing "getEJBMetaData" method.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Based on the EJB specification, methods belong to either a home or a bean. Home methods (e.g., create) have corresponding bean methods prefixed with the keyword "ejb" (e.g., ejbCreate). In earlier versions of WebSphere Application Server, the "getEJBMetaData" was not correctly a home method.

 

Defect		Reference Number: 72827
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	Environment for Remote Servlet Redirector Runs in the following:  - Web Server (IBM HTTP 1.3.6.1) with thin Redirector - Sun (Burlap)  - WAS Server  - Sun 250 2X248MHz (Canvas)  - Solaris 2.6 plus latest patches  - Sun JDK 1.1.7_08  - DB2 6.1plus fixpak 2  - WAS 3.0.2 GA (driver 49_01)  - remote DB2 6.1 plus fixpak 2 Server - Sun 450 4X (Kevlar) ConnectionPreemptedExceptions (i.e., SessionContex X BackedHashtable:pollForInvalids - database error; SessionContex X BackedHashtable:doInvalidations - database error) are being thrown in the Thin Redirector Solaris environment listed above.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Currently when the RemoteSRPBean is invoked to perform the "servlet" operation, there is an implicit transaction (local) associated with the request.  Any DB connection created is associated with that transaction and causes problems, e.g., session persistence breaks. Prior to invoking dispatchByURI, the transaction should be suspended. After the dispatch is completed, the transaction should be resumed.  Example code to do this can be found in com.ibm.ejs.sm.util.Utils.activeObjectExecutionPrologue()/Epilogue().

 

Defect		Reference Number: 72875
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	When the JTA is enabled, the default value of the URL prefix is not updated on the WebSphere Administrative Console. As a result, the wrong value is passed back to server, causing the connection pool iniitalization to later fail.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The default value for the URL prefix for DB2 is fixed when the JTA is enabled on the datasource configuration.

 

Defect		Reference Number: 73335
Category:	EJB Support	PTF No.: WAS 3.0.2.1
Brief Description:	XMLConfig.sh must always be invoked script from [WASRoot]/bin directory.  If I run the XMLConfig.sh from a directory other than the [WASRoot]/bin, the script will not be able to find the <current working directory>/setupCmdLine.sh file.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
Now you could run XMLConfig.sh file from any directory. The supporting scripts / executable would be picked from the system PATH environment variable.

 
 

Documentation

[Home]

Defect		Reference Number: 74624
Category:	Documentation	PTF No.: WAS 3.0.2.1
Brief Description:	The samples documentation on creating a DataSource object incorrectly implied that "JTA Enabled - true" could be specified  for DB2 5.2.
Platforms:	Windows NT/AIX/Solaris/HP-UX
Resolution		Status:[Resolved]
The revised documentation indicates that DB2 5.2 supports only "JTA Enabled - false"; and DB2 6.1 can be set for either "true" or "false."

 

[Home]		[Installation]	[Administration]	[Security]
[Web server Interface]	[Servlet Support]	[JSP Support]	[EJB Support]	[Documentation]