Resolved Issues


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	e-docs \| Site Map \| Search \| Contact \| Glossary \| WebLogic Server Documentation

BEA WebLogic Server 6.0 Release Notes : Previous Topic \| Next Topic \| Contents

Resolved Issues

The following sections contain information on issues that were resolved for the release of WebLogic Server 6.0 with Service Pack 2 (Service Packs are cumulative, so all the changes in earlier Service Packs are included in the latest Service Pack):

Service Pack 2 Fixes

EJB Issues

Change Request Number

Description

042956

Fixed a problem with jar files that contained many beans (100+). In these circumstances ejbc was failing when running under Windows.

043398

Fixed some problems with a message-driven bean calling a stateless session bean when the two beans are packaged in different jar files. A classcast exception occurred when narrowing on the home of the called bean.

043640

Fixed some problems in EJB in which certain log messages occurring with rolled back transactions were exceedingly verbose.

044179

An unintentional debug statement in the server's internal EJB container has been removed.

044605

Serializing a JMS message that has never been sent resulted in a NullPointerException. This happened during the writing of unsent messages to a stream or passing an unsent message as a parameter via an RMI call, including EJB invocations. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be installed on the JMS client.

044755

Fixed some problems with primary key classes when migrating 1.1 CMP beans. In WebLogic Server 5.1 the primary key class fields were not included within the updated fields, whereas in WebLogic Server 6.0 they were updated. Now we have returned to the earlier, correct, behavior--where the primary key class fields are not included as an updated field.

Examples Issues

Change Request Number

Description

042366

Running the Security Audit Example was causing a run-time exception in WebLogic Server. This has been fixed.

JDBC Issues

Change Request Number

Description

038235

Fixed some problems with the jDriver concerning double data types in Oracle.

041793

If a database went down during attempts to access the database, the initial reset of the JDBC connection pool was failing. This has been fixed.

041866

Using CLOB.getCharacterStream() is no longer a problem with the Weblogic jdriver.

042134

Fixed some problems with dynamic connection pools.

042279

Multipools now work with a TxDataSource with the restriction that all connection pools in the TxDataSource must either use the same driver, or they must all use drivers that have the same XA capabilities. (either all the drivers must be XA compliant, or all drivers must not be XA compliant).

043745

When Oracle returned OCI_SUCCESS_WITH_INFO, the WebLogic jDriver returned a warning message without providing the data. Now, both the warning and data are given.

043956

Fixed some problems on HP-UX 11.0 when using the WebLogic jDriver and executing certain SQL commands.

044223

Fixed a problem with connection pools not failing over.

045965

Included some fixes in order to get around XA-Resource issues with the Oracle 8.1.7 thin driver.

JMS

Change Request Number

Description

041031

Fixed problems with asynchronous JMS messages, whereby the last message was not being acknowledged. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be installed on the JMS client.

043118

Fixed a problem with using a MQSeries JMS Topic driving a message-driven bean. The following exception was being raised: javax.jms.JMSException: MQJMS1057: Message has no session associated with it.

043155

Topic message expiration times are no longer ignored for asynchronous subscribers.

043225

During transmission of ObjectMessages, the object stored in the message was serialized at least twice (possibly more for topics). For most situations this has been reduced to once. In addition, calling toString on an ObjectMessage would previously return null if the object was not first unserialized by calling getObject(). This is no longer the case. getObject() is now called from within the toString method of an ObjectMessage.

043519

Fixed a problem in JMS that occurred during session rollback or recover. Asynchronous consumers were refusing to receive messages. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be applied to both the JMS client and server.

043752

In JMS, recovered expired messages no longer cause incorrect NullPointerExceptions.

044285

Fixed a problem in JMS. Multiple simultaneous transacted asynchronous durable subscriptions were possibly causing a server lock-up if not enough threads were configured. Now, no extra threads are needed to service such simultaneous requests.

045963, 045939, 045956

Connection consumers for session pools are behaving properly now.

JSP Issues

Change Request Number

Description

042360

In JSPs, getCharacterEncoding() was returning ISO-8859-1 even if charset was set to Shift_JIS or some other character set. Now the proper character set is returned.

043167

JSP pages that use includes with relative paths (i.e. <jsp:include page="../bar.html") no longer cause parsing errors.

044023

WebLogic's JSP compiler was not case sensitive. If you were using Windows NT and had compiled HelloWorld.jsp, the generated file would have been _helloworld.class, not _HelloWorld.class. The default behavior of the JSP compiler is now case sensitive.

045895

A JSP page that was using a jsp:useBean tag and had 'type' set to 'BeanInterface' was not working. The following exception was occuring:

weblogic.servlet.jsp.JspException: Could not set property: someValue:
java.beans.IntrospectionException: java.lang.Object not superclass of BeanInterface.

This problem has been fixed.

046534

When JSPs are registered in web.xml, the 'compileCommand' entry is no longer ignored.

Miscellaneous Issues

035169

Fixed problems with form authorization in a Web Application. There was a misleading message when users who were already logged in went directly to the <form-login-page> specified in the web.xml deployment descriptor. The message returned to the browser was:

Form based authentication failed. Could not find session.

The following error was printed to the log:

<E> <WebAppServletContext-test> Form based authentication failed. One of the following reasons could cause it: HTTP sessions are disabled. An old session ID was stored in the browser.

This error is incorrect--at that point the user is still logged in, has a valid session, and you can still access the protected resource. Now the server no longer generates these errors and instead, in this case, redirects the user to the parent directory of the login page, which causes the server to look for and serve the Web Application's welcome page. For more information see Configuring Welcome Pages.

042661

Fixed a problem in clustering. When a replica-aware stub is called within a transaction, it attempts to route the call to the server hosting the transaction coordinator. The problem was that the stub was sticking to this server for the life of the stub, even if it was called a second time outside of the transaction.

043010

Instances of WebLogic Server 6.0 running as a Windows service no longer shut down automatically and become inaccessible after you log out of the NT session in which the server was running in.

043493

JNDI is no longer accessed prior to it being properly initialized during server startup.

043695

The value returned by session.getId() no longer returns the same value as request.getRequestedSessionId(). Also note: to determine whether an incoming cookie has a valid session, use request.getSession(false).

043865

Fixed a problem that caused an EXCEPTION_ACCESS_VIOLATION when shutting down a WebLogic Server that uses a RDBMS realm with the Weblogic type 2 Oracle JDBC driver for Oracle 8.1.6 on win32.

044105

Fixed problems that occurred when starting the server as an NT service while using the -hotspot option.

044282

An unnecessary reverse DNS lookup has been removed.

044450

Removed unnecessary code in JDBC Store that was causing problems with TimesTen.

044556

Fixed a problem with the serialization of HTTP query parameters.

045960

IDL files generated by weblogic.ejbc can now be compiled by an IDL compiler.

044987

Fixed problems in the java socket multiplexor with applets reloading/refreshing the browser.

045091

In EJB 2.0 the transaction context is no longer lost if remove() is called on a stateful session bean with a transaction attribute of NotSupported.

046058

The WebLogic Plug-ins no longer cause a long delay when they route URL requests with SecureProxy=ON.

Servlet Issues

Change Request Number

Description

042281

A servlet no longer continues executing after the browser is closed.

044579

An incorrect IllegalStateException is no longer thrown in certain situations when a servlet in a Web Application handles file upload and then has to process the input.

045580

There are no longer problems when mapping a ServletException to an error page in web.xml.

043541

The servlet engine now properly parses all URLs not ending in '/' or an extension.

Service Pack 1 Fixes

C onsole Issues

Change Request Number

Description

035788

Fixed some hyperlinks to our documentation that were broken in the Console.

038336

Fixed HTML problems in the Console where some anchors were going to the right help page but not to the right place within that page.

038359

A Multibyte machine name is now displayed correctly when creating a Kanji Machine name.

039629

On the Web App General panel of the Administration Console, there is now a check box indicating that the Web Application is deployed.

040029

A help icon in the Console is no longer displaying an Error 404--Not Found.

040101

Fixed a problem with graphs in Netscape when using monitoring in the console.

040127

On Japanese NT, fixed a problem with the Console and using localized log messages.

040181

When creating a 'Machine' on the Japanese NT, the 'CREATE' button was not making any change in the console. The create page was still virtually the same after clicking the 'CREATE' button. This is now fixed.

040820

Fixed a problem when the `Create' button was selected prematurely while trying to configure a new web application.

040846

Fixed a problem with Netscape and the WebLogic Console. When creating a new conection Factory, at the JNDIName text box, a dialog box said, "This field cannot be blank". This dialog would not disappear until killing the browser.

040865

Fixed a problem with the cluster monitoring tab in the console. It was not showing the correct number of participating servers.

040902

Fixed an unnecessary field in the console when clicking on the garbage can in the security-->group node.

041080

Fixed a problem with the console and security when creating a multi-byte group name and registering a user to the group.

041096

Fixed a problem with Japanese characters in the console.

041112

Fixed a problem with certain domain settings not being persisted and returning to the defaults on restart.

041117

The Console was having problems when `refresh' was being used regularly in the browser. These problems have been fixed.

041141

The Console no longer displays corrupt strings when the navigational tree is disabled.

041268

Fixed a problem in the Console when switching languages from Japanese to another language.

041301

In the Console, the Max Size value under the HTTP tab had a unit of kilobytes. It has been changed to bytes.

041532

Fixed problems with the Console, involving undeploying and redeploying Web Applications.

041606

When entering 'Search text' in the log customize window in multi-byte string, it was displaying the search result. But when displaying the log customize window a second time, the initial value of the string which was entered in the previous search was corrupted. This has been fixed.

041733

The Console was setting the XMLRegistry MBean attributes to "" if they are unset. This confuses the XMLRegistry which thinks the are settings to the value empty string. The XML Registry now considers "" to be the equivalent of an unset field.

041837

There was a problem starting the Console and changing the rotation type to date based in http logging and then restarting the Server.

041875

Added some information to the console for users who delete an ACL.

041943

Fixed a problem in the console when using a Kanji group name.

041944

Fixed a bug in the console when using a Kanji character as an ACL name.

041994

Fixed errors when creating a new domain using the Console.

042058

In the JNDI tree of an active server, nodes of bound objects no longer have incorrect '(access denied)' labels.

042068

Removed the ability to clone applications from the Console.

042181

The unit in which the configuration parameter "Logging -> Size Threshold" is identified now as 'kilobytes' on both the domain and server logging tabs.

042278

You can now deploy a MultiPool and specify the targets using the Console.

042434

Fixed a problem deleting a multibyte group name.

E JB Issues

Change Request Number

Description

031228

Improved error messaging with ejbc. The full stack trace is now printed out when a NoClassDefFoundError occurs.

031852

It was possible to set transaction attributes for non-existent methods. A misspelled method name in the deployment descriptor could cause a transaction attribute to not be set. We now validate that all method names specified in the deployment descriptors actually exist in both the remote interface and the bean implementation class.

033538

Fixed a problem in EJB with queries and escape clasuses. Also fixed problems with the Java compiler and the '\' character.

034691

It is incorrect to use EJB 2.0 with WebLogic 6.0 and a WebLogic 5.1 RDBMS XML deployment descriptor. When doing so, a confusing ClassCastException was being thrown. Now we inform users that this configuration is incorrect.

035395

Finders were only working if all of the finder method parameters were referenced exactly once by the query. This has been fixed.

036007

Now we throw the appropriate error message when using ejbc for a cmp11 type bean with one of the attributes as private.

037622

Removed redundant messages (setMessageDrivenContext called, ejbCreate called, setMessageDrivenContext called) when running the sample server on UNIX.

037957

Now EJB-QL: WHERE clauses are commutative.

039179

There was a confusing and misleading error message in the EJB examples. The message was:

log("UNABLE to get a connection from demoPool!");
log("Please make sure that you have setup the connection pool properly").

Now this message reads:

log("Failed to lookup JDBC Datasource. Please double check that"); log("the JNDI name defined in the resource-description of the ");
log("EJB's weblogic-ejb-jar.xml file is the same as the JNDI name ");
log("for the Datasource defined in your config.xml.")

039477

Fixed the error message that is displayed if the ejb20.jar is not in the server classpath. There are now two distinct errors if EJB 2.0 cannot be started - either it's a LicenseException, and the user should contact a sales representative to get a license,or EJB 2.0 has not been enabled and the error message indicates where users can download the EJB 2.0 upgrade to enable it.

039518

Our CMP 2.0 code was not retrieving cmp-fields that were an EJBObject. This has been fixed.

039562

Message-Driven EJBs with the NotSupported transaction attribute are now destroyed when a System Exception is thrown.

039635

The latest revision of the EJB 2.0 spec requires that CMP and CMR fields start with a lower-case letter. We have added this check to our compliance checker, and made sure our examples do not violate this rule.

039736

If you deployed an EJB using weblogic.deploy, it copies the .jar file to the applications directory. The .jar file cannot be removed from the applications directory. Attempts to remove the .jar file result in the following message:

C:\weblogic\dev\src\tools\weblogic\qa\tests\config\mydomain\applications>rm matt.jar
rm: cannot unlink entry "matt.jar": The process cannot access the file because it is being used by another process.

This has been fixed.

039818

Fixed AssertionError when Primary Key fields were Serializable objects.

040052

Removing a bean from a M-N relationship wasn't removing join table entries. This has been fixed.

040066

The setting max-beans-in-free-pool now determines the maximum number of concurrent instances that can be created to service messages. It is bound by the number of ExecuteThreads.

040108

EJB Compliance Checker now allows java.lang.Object as the primary key type.

040303

Having two EJBs with the same <abstract-schema-name> creates an inaccurate and misleading error message: org.xml.sax.SAXParseException: The content of element type "ejb-jar" must match "(description?,display-name?,small-icon?,large-icon?,enterprise-beans,dependents?,relationships?,assembly-descriptor?,ejb-client-jar?)".

We have added a compliance check for this problem.

040461

Set transaction state to committed as soon as the last ackCommit message is received.

040469

Previously when you added a message-driven entry to your ejb-jar.xml file but neglected to add its counterpart to the weblogic-ejb-jar.xml file, ejbc did not give you an error message. This has been fixed.

040470

If a EJB fails to deploy all of the ejbs within the ejb, now the jar file will be undeployed.

040564

Added support to EJB for instances when a Primary-key includes a foreign key column for 1-n and 1-1 relationships.

040586

The EJB compliance checker now ensures that finder return types are the remote interface, java.util.Collection, or java.util.Enumeration.

040593

The EJB comliance checker now detects when the EJB-QL for a finder method contains a SELECT clause.

040594

Using an abstract base class to declare the public abstract getter and setter methods for the CMP fields of an EntityBean, ejbc wasn't able to find the methods on the EntityBean and refusesd to code-generate the container classes. This has been fixed.

040697

Fixed a ClassCastException when undeploying Message-Driven EJBs.

040740

Enabled monitoring of managed servers in deadlock and overload situations.

040788

We now allow message driven bean users to specify NO_ACKNOWLEDGE or MULTICAST_NO_ACKNOWLEDGE for their acknowledgement mode.

040907

Fixed a problem with message driven beans when calling other EJBs in the same ejb-jar.

040924

Now we conform to the latest EJB spec revisions, which don't allow protected CMR get/set methods. These methods must now be public.

041041

Improved performance using EJBs and big CMP 2.0 creations.

041055

Before SQL was generated, an error was not being caught when a CMP field and a CMR field were mapped to the same database column.

041133

The current version of the EJB QL spec states that the 'FROM' clause is required in every query (see EJB2.0 spec sec 10.2). The examples have been updated to reflect this.

041284

Message-Driven EJBs now support external JMS Providers.

041306

During JSP compilation, the EJB interfaces within the same application were not available. This has been fixed.

041369

Fixed AssertionError when EJBMetaData was used from within the server and the EJB's classes were not in the classpath.

041430

When there was a NoClassDefFoundError within ejbc, the stack trace was being omitted. This has been fixed.

041728

When deploying CMP Beans, if the DataSource/Connection was unavailable, users were seeing a misleading message which suggested that the Bean's table didn't exist. This has been fixed.

041801

A ClassCastException was occurring when replicated stateful session beans were compiled without an In-Memory replication license and then deployed in a server with the proper license.

041918

Calling a replicated stateful session bean in a non-clustered server no longer causes an Assertion Failure.

041937

If <primkey-field> isn't a CMP-field, users were getting a java.lang.NullPointerException. This has been fixed.

041986

The EJB compiler was generating invalid SQL queries for the finder methods of 1.1 CMP Beans.

042041

1-N relationships were failing when the beans in the relationship had a compound key, and when the foreign-key used in the relationship was also part of the primary key of one of the beans. The failures manifested when a bean participating in the relationship was removed, and also when ejbc is run in some cases (ejbc fails). This has been fixed.

042132

Any EJB method whose name starts with `remove' was being deployed as NotSupported. This has been fixed.

042217

EJB QL queries that contained a 1-1 or 1-n join weren't working with compound keys. This has been fixed.

042430

The RemoteException detail field is now set correctly in EJB.

042483

Fixed a problem when an EJB marks a transaction for rollback and then calls the RequiredNew method.

042637

When removing a bean, the server wasn't initializing the bean's CMP variables before putting it into the pool. This caused errors later if the bean was reused. This has been fixed.

E xamples Issues

Change Request Number

Description

037669

The WLEC university sample was failing to make a connection when the connection pool initializes. The server couldn't connect because the password specified by the example is greater than 8 characters long. This has been fixed.

039403

In the left hand pane of the console, the audit provider example (found at /security/audit/package-summary.html) was referencing an Audit Provider node that didn't exist. This has been fixed.

040411

When using the Administration Console with the Examples server and the default Cloudscape RDBMS realm, you can now shut down the server. Attempts to shut down the server were failing because the user guest did not have shutdown permission for weblogic.admin. The example Cloudscape database did not contain the appropriate ACL to allow the user guest to shut down the server.

040429

Fixed a problem in our examples. In the security acl example the documentation has a typo; java examples.security.acl.Client t3://localhost:7002 joeuser joepass should have been: java examples.security.acl.Client t3s://localhost:7002 joeuser joepass.

040508

Modified all examples to use java.rmi and JNDI instead of weblogic.rmi.

040633

After undeploying the Pet Store Web Application and then deploying it again to a managed server a javax.management.MBeanException was being thrown. This has been fixed.

040682

The JAAS security example was missing an implementation of AltClient. AltClient is the client side implementation showing how to use mutual authorization with WebLogic.

040954

Added seven new XML examples.

041643

Fixed the cluster connection string example. WebLogic requires that all members of a cluster share the same port.

042136

The examples.utils.ddl.demo.ddl file has a mistyped statement; an extra T in DROP: (DROPT table).

042140

A DataSetException was occurring when trying to execute the samples\examples\dbkona\rowid example. This has been fixed.

042213

In the date and phoneBook examples, there was an error in the documentation. Under Run this Example, "From the toolkit's General Menu," should have been: "From the Nokia Active Server manager general Menu."

042244

The setExamplesEnv script and the startExamplesServer script now include the xmlx.jar in the CLASSPATH.

042256

The web.xml in the examplesWebApp did not have a taglib-uri element for the xslt tag library.

042261

Improved the documentation in examples/i18n/logging/startup/package-summary.html

042583

When building the ejb/simpapp WLEC sample, the jspc compiler complains that it can't find the web.xml file. We added a -webApp flag to the jspc command to fix this. There was a similar problem, also fixed, with examples/jdbc/pool/build.cmd.

042585

The instructions for running the university samples say the following:

Start a web browser and enter the URL for UniversityForm.html.

For example:

http://localhost:7001/examplesWebApp/UniversityForm.html

But the name of the file is actually universityForm.html. (The 'U' in university should have been lowercase.)

042586

The WLEC Simpapp Servlet example now catches any PoolUnavailable exceptions.

I nternationalization Issues

Change Request Number

Description

035036

When WebLogic boots and prompts for the boot account's password, the prompt used is now internationalized.

041021

Fixed a problem failing to generate properties files for some message catalogs after executing l10ngen.

041078

Fixed some duplicated keys in the english.xml file.

041264

Fixed some internationalization problems with certain tags not being in english.xml.

041266

The time stamp is now internationalized.

J DBC Issues

Change Request Number

Description

033423

There were dbKona problems with QueryDataSet and the OCI805_8 driver. This has been fixed on Windows NT, but is still a problem on HPUX and Solaris.

033920

Change There was a problem in JDBC when running tests which access the connection pool.

035530

There were problems enabling OS authentication and using Oracle 8.1.6/oci8 with the jDriver. This has been fixed on NT and HP-UX, but still is an issue on Solaris. We have added an error message that reports this problem: OS level authentication is not currently supported due to a defect in OCI 8 libraries.

037589

Added Oracle thin driver support and fixed some outdated command line help.

037591

Added support for ORACLE_THIN database type. Removed obsolete database types and command line options.

037693

There are no longer problems with the Oracle driver and ROWID selects when running examples.dbkona.rowid.

037893

Fixed getBytes() to return null instead of a zero-length byte array with Oracle LONG RAW columns.

038143

JDBConnectionPoolRuntimeMBean's were not working. Added a RuntimeMBean implementation to ConnectionPools.

038229

The jDriver for Oracle 8.1.6 caused managed servers to run out of memory.

038275

We no longer refer to the weblogic.classpath in one of our JDBC error messages. The weblogic.classpath does not exist in WebLogic 6.0.

040379

The following error occurred when the server and serverName properties in a JDBC connection pool were specified with the same value:

<Cannot startup connection pool "jtaXAPool" server and serverName properties must have the same value>

This problem was seen when the XA driver requires the server or serverName property to be set. It was occurring with the WebLogic jDriver for Oracle, but not the Oracle thin driver, or the Cloudscape driver. It has been fixed.

040509

Fixed a small problem with Solaris 2.6 and the jdriver.

041286

Better error message for misconfigured connection pools

041302

The MS SQLServer driver has been updated.

041514

Added support for JDBC and connection pool monitoring in the Console.

J MS Issues

Change Request Number

Description

038109

The JMS connection is now cleaned up properly when the client terminates without closing.

039249

The managed server no longer has a memory leak when it monitors JMSServer using the Administration Console.

039802

Closing non-durable subscriber messages that were not being pushed to the subscriber at the time, such as messages for the synchronous subscriber, was sometimes causing message statistics to become out of sync. This has been fixed.

039921

A multicast subscriber was not able to receive multicast messages on Solaris machines. This has been fixed.

040088

Problems were occurring when attempting to send messages from a connection consumer's listener class OnMessage method using the same session that a session pool uses to send messages to the connection consumer.

040479

Fixed a bug in JMSHelper that was causing incorrect xml to be written to the config.xml file.

040793

Recovered unacknowledged messages were not being marked as Redelivered. This has been fixed.

041617

The JMSMessageID converted using the JMSHelper no longer adds an extra zero at the end.

041691

Fixed a bug in JMS that causes Message-Driven-Beans to hang when the trans-attribute flag in the ejb-jar.xml file is set as Required.

042461

When sending a message from WebLogic Server JMS classes through a IBM MQ JMS sender and the correlation ID for the message is null, the IBM code was calling WebLogic with setJMSCorrelationIDAsBytes(), which is not supported. We now convert the bytes to a UTF8 string and store it in the correlation id in order to handle setJMSCorrelationIDAsBytes.

042484

When trying to create an ObjectMessage with an object that was not in the classpath and within a bean, JMS was throwing ClassNotFoundException. This has been fixed.

P lug-in Issues

Change Request Number

Description

038831

The Apache plug-in was failing under heavy load. This has been fixed.

040817

When using IIS to browse and call a regular JSP page that calls a Java Bean and getting a ResultSet reference, there were problems when submitting through the FORM POST method. The HTML stream was getting truncated when it came back to IIS--in other words, the page was only partially painted. This has been fixed.

041332

Using plug-ins, MatchExpression can now contain multiple, comma-separtated expressions.

041534

Using the mod_wl.so, Apache was not proxying without Debug and DebugConfigInfo in the httpd.conf. This has been fixed.

041580

The Apache plug-in MatchExpression now works if an encoded URL is used.

041745

Added a log message when the trusted CA file isn't specified and SSL is used with the Isapi plug-in.

041754

Fixed an infinite loop when ISAPI was configured for SSL but using a non-secure port.

041939

The Apache plug-in wasn't filtering out the header "transfer-encoding"="chunked". So the browser was failing to handle these responses, causing Netscape to hang and IE to display an error page. This has been fixed.

042482

The NSAPI and Apache plugins were having a READ timeout on HPUX-11. These problems have been fixed.

S ervlets and JSP Issues

Change Request Number

Description

026488

Fixed a problem with servlets when the parameter to method println(String) was null.

029989

The wrong error message was sometimes being sent when an UnavailableException was raised within a servlet.

030880

Fixed problems compiling JSPs when debugging was turned on. Now you can specify compiler flags in weblogic.xml. For example:

 <weblogic-web-app>
<session-descriptor>
</session-descriptor>
<jsp-descriptor>
<jsp-param>
<param-name>compileCommand</param-name> <param-value>jikes</param-value>
</jsp-param>
<jsp-param>
<param-name>compileFlags</param-name>
<param-value>+E -nowarn</param-value>
</jsp-param>

041478

There was a change in session cookie format that also fixed some problems with URL rewriting.

037771

Optimized the checking of JSP's for reloading.

038739

Improved support for JSP debugging.

039083

The RequestDispatcher and forwarding a JSP page now works correctly.

039193

When users forgot to make their servlet class public, a vague and unhelpful error was being thrown. This no longer happens.

039530

Fixed our internal servlet tags to reset their state on release. If you used the same tag more than once on a page the additional tags kept the stale data from the previous tag.

040171

The attribute SingleThreadedServletPoolSize was not settable through the Administration Console. This has been fixed.

040338

Some servlets were functioning, but were not showing up in the mydomain>WebApplications>DefaultWebApp_myserver>ActiveServlets window of the console. This has been fixed.

040662

When JSP files had a page tag, the JSP compiler was not generating a class, or java file. This happened only with command line jspc. This has been fixed.

040766

Fixed a problem in servlets with using ../ for a relative URL when doing a response.sendRedirect.

040814

Added more informative error messages for instances when user errors cause exceptions using servlets.

040843

Fixed problems with deploying WebAppComponents using virtual hosts.

040981

Fixed problems associated with WAP and session cookies using the pipe characters.

041234

Fixed a problem in JSP/Servlets using POST and HTTPS.

041605

There was a problem with JSPs where the compiler error page displayed a corrupt error message from javac. This has been fixed.

041684

Fixed a problem in servlets. The XSLT tag threw a SAXParseException while proceesing XML content.

041729

The weblogic.servlet.jsp.Precompiler didn't honor weblogic.xml parameters, like workingdir, packagePrefix, etc, for the JSPs that it precompiles. This has been fixed.

041945

When the web.xml had the setting inputCharset./A*=Shift_JIS inputCharset./B*=EUC-JP, and two clients simultaneously accessed the JSP/Servlet, WebLogic failed to handle these string correctly. It was possible to get the correct result from one client, but not from the other. This has been fixed.

042031

In the webapp data table, when you click the monitoring icon for any webapp and then click on the monitor link in the Servlets column, the correct heading is now displayed.

042293

Servlet URL rewriting was working fine with IE 5.0 but wasn't working with Netscape 4.7. This has been fixed.

042509

Fixed some problems when forwarding from one web application to another web application and using some form of authentication in both. Some session data was incorrectly getting shared across the applications

X ML Issues

Change Request Number

Description

039096

You no longer have to restart WebLogic Server to make it aware of a newly added entry to the XML registry.

039247

Custom parsers are now correctly invoked when an XML document that has been configured to be parsed by the custom parser is parsed using the setAttribute() method of the Servlet API.

041734

WebLogic's JAXP implementation no longer requires that the input stream that contains an XML document that is about to be delegated to a particular parser for parsing be resettable.

041778

A NullPointerException error is no longer thrown when an XML document that contains an external entity that has been correctly registered in the XML registry is parsed.

041797

After creating a new server, the server was failing to reboot and the config.xml had some incorrectly parsed headers. These problems have been fixed.

M iscellaneous Issues

Change Request Number

Description

035039

When WebLogic needs to prompt for the boot password, first it should log (in security.xml) that it is prompting. This would allow an administrator on a remote machine to know why the machine is apparently "hung". This now happens.

036141

A managed server was not starting if guest had been disabled (in order to do a JNDI lookup in an ACL). This has been fixed.

036604

The method ClusterMBean.setDefaultLoadAlgorithm() no longer accepts illegal values and throws the proper IllegalArgumentException.

036986

Using Weblogic's XA driver with CMP was failing at deployment time. This has been fixed.

038883

Specifying the root directory when starting the server was not working when the root directory was not under a /config directory.

039066

If you entered an incorrect password when prompted at system startup, the server just tried to start anyway. The startup eventually fails. Now we reprompt for the password when the password is wrong.

039182

When binding two clusterable objects implementing the same interface to the same JNDI name on a single server, an exception was not being thrown and the first clusterable object was being bound. This has been fixed.

039249

A managed server had a memory leak when it monitored JMSServer using the Administration Console. This has been fixed.

039361

If you used the rdbms realm and created a group, you could not delete the group. This has been fixed.

039891

Fixed a problem with the server not setting the context attribute correctly during servlet initialization.

039960

Log Viewer is now working in Non-US Locales.

039995

A server startup error no longer occurs after a WLEC Connection pool was created using the Administration Console.

040168

The logging example for internationalization failed when a dot (.) occurred in the path. This has been fixed.

040177

Additional user information was required when converting weblogic.properties files for use with WebLogic Server 6.0. This has now been added to the product documentation.

040178

When you were using the conversion utility, if a weblogic.properties file included the property weblogic.httpd.register.Name=weblogic.servlet.FileServlet and the servlet did not have initial arguments associated with it (it does not have the property weblogic.httpd.initArgs.file=arg1=value defined in the same weblogic.properties file), then the conversion utility was throwing a Null pointer exception. This has been fixed.

040213

The listenport of the managed server cannot be the same as the administrative listenport. You cannot, for example, use localhost or 127.0.0.1, with the 7001 host number on both the managed and administrative servers. Added a more descriptive and informative error message when this occurs.

040297

Fixed a bug that was causing attributes set in application.xml not to propagate from administration servers to managed servers.

040405

The config.xml file is now serialized using the Apache XML serialize classes. This results in the correct XML, including escapes for built-in entities and an XML header with encoding specified. The encoding used is the platform default. This also fixes problems with the "&" character.

040659

When specifying getParameter() encoding as iso-8859-1, the POST method is now working properly.

040688

Targeting a mail session to a server that is part of a cluster, the following exception was being thrown since the mailsession was not serializable: java.io.NotSerializableException: javax.mail.Session. This has been fixed.

040899

Fixed a problem with a start-up class when the converter utility converted startup weblogic.properties into .xml.

040950

Fixed a problem in JTA. For XA connections, the Connection Pool test connection logic was attempting to start a distributed transaction before executing the testing SQL. This had the potential to create a javax.transaction.NotSupported exception.

041157

The dialog tabs in the Console were not working correctly when the Mbean name contained Kanji characters.

041290

If the username property is set from the weblogic.Admin or weblogic.Server command lines, the username must be the system password. Note however, that the username syntax is retained to prevent breaking a user's scripts. The weblogic.management.password property value must be the system password and the username may not be modified in the config.xml file.

041662

To improve JTA, we now advertise resources on JNDI. Resources were dynamically discovered as transactions go along, but now it is also possible to find out which resources are currently being supported at which servers.

041757

Fixed a problem with JTA. Resource advertisenment (JNDIAdvertiser) was incorrectly done under the caller's identity. We now use the system identity while doing this operation.

041845

Updated the NTRealm to generally improve usabilty and functionality.

041854

To help support Java WebStart with WebLogic Server 6.0, we now provide a default Web Application with the web.xml configured for this mime type. We have also provided other mime type mappings.

041995

Fixed an Unexpected Error being received in the console when resuming an active server. Also deleted some extraneous informational messages in the console when adding users.

042183

When the config.dtd was being generated in the console it was appearing with some errors. This has been fixed.

043388

Clusters of WebLogic Servers no longer require the use of a shared network drive. Both the WebLogic Server installations and your applications can now reside on local file systems.

Change Request Number	Description
042956	Fixed a problem with jar files that contained many beans (100+). In these circumstances ejbc was failing when running under Windows.
043398	Fixed some problems with a message-driven bean calling a stateless session bean when the two beans are packaged in different jar files. A classcast exception occurred when narrowing on the home of the called bean.
043640	Fixed some problems in EJB in which certain log messages occurring with rolled back transactions were exceedingly verbose.
044179	An unintentional debug statement in the server's internal EJB container has been removed.
044605	Serializing a JMS message that has never been sent resulted in a NullPointerException. This happened during the writing of unsent messages to a stream or passing an unsent message as a parameter via an RMI call, including EJB invocations. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be installed on the JMS client.
044755	Fixed some problems with primary key classes when migrating 1.1 CMP beans. In WebLogic Server 5.1 the primary key class fields were not included within the updated fields, whereas in WebLogic Server 6.0 they were updated. Now we have returned to the earlier, correct, behavior--where the primary key class fields are not included as an updated field.

Change Request Number	Description
042366	Running the Security Audit Example was causing a run-time exception in WebLogic Server. This has been fixed.

Change Request Number	Description
038235	Fixed some problems with the jDriver concerning double data types in Oracle.
041793	If a database went down during attempts to access the database, the initial reset of the JDBC connection pool was failing. This has been fixed.
041866	Using CLOB.getCharacterStream() is no longer a problem with the Weblogic jdriver.
042134	Fixed some problems with dynamic connection pools.
042279	Multipools now work with a TxDataSource with the restriction that all connection pools in the TxDataSource must either use the same driver, or they must all use drivers that have the same XA capabilities. (either all the drivers must be XA compliant, or all drivers must not be XA compliant).
043745	When Oracle returned OCI_SUCCESS_WITH_INFO, the WebLogic jDriver returned a warning message without providing the data. Now, both the warning and data are given.
043956	Fixed some problems on HP-UX 11.0 when using the WebLogic jDriver and executing certain SQL commands.
044223	Fixed a problem with connection pools not failing over.
045965	Included some fixes in order to get around XA-Resource issues with the Oracle 8.1.7 thin driver.

Change Request Number	Description
041031	Fixed problems with asynchronous JMS messages, whereby the last message was not being acknowledged. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be installed on the JMS client.
043118	Fixed a problem with using a MQSeries JMS Topic driving a message-driven bean. The following exception was being raised: javax.jms.JMSException: MQJMS1057: Message has no session associated with it.
043155	Topic message expiration times are no longer ignored for asynchronous subscribers.
043225	During transmission of ObjectMessages, the object stored in the message was serialized at least twice (possibly more for topics). For most situations this has been reduced to once. In addition, calling toString on an ObjectMessage would previously return null if the object was not first unserialized by calling getObject(). This is no longer the case. getObject() is now called from within the toString method of an ObjectMessage.
043519	Fixed a problem in JMS that occurred during session rollback or recover. Asynchronous consumers were refusing to receive messages. To fix this issue, WebLogic Server 6.0 with Service Pack 2 or higher must be applied to both the JMS client and server.
043752	In JMS, recovered expired messages no longer cause incorrect NullPointerExceptions.
044285	Fixed a problem in JMS. Multiple simultaneous transacted asynchronous durable subscriptions were possibly causing a server lock-up if not enough threads were configured. Now, no extra threads are needed to service such simultaneous requests.
045963, 045939, 045956	Connection consumers for session pools are behaving properly now.

Change Request Number	Description
042360	In JSPs, getCharacterEncoding() was returning ISO-8859-1 even if charset was set to Shift_JIS or some other character set. Now the proper character set is returned.
043167	JSP pages that use includes with relative paths (i.e. <jsp:include page="../bar.html") no longer cause parsing errors.
044023	WebLogic's JSP compiler was not case sensitive. If you were using Windows NT and had compiled HelloWorld.jsp, the generated file would have been _helloworld.class, not _HelloWorld.class. The default behavior of the JSP compiler is now case sensitive.
045895	A JSP page that was using a jsp:useBean tag and had 'type' set to 'BeanInterface' was not working. The following exception was occuring: weblogic.servlet.jsp.JspException: Could not set property: someValue: java.beans.IntrospectionException: java.lang.Object not superclass of BeanInterface. This problem has been fixed.
046534	When JSPs are registered in web.xml, the 'compileCommand' entry is no longer ignored.

035169	Fixed problems with form authorization in a Web Application. There was a misleading message when users who were already logged in went directly to the <form-login-page> specified in the web.xml deployment descriptor. The message returned to the browser was: Form based authentication failed. Could not find session. The following error was printed to the log: <E> <WebAppServletContext-test> Form based authentication failed. One of the following reasons could cause it: HTTP sessions are disabled. An old session ID was stored in the browser. This error is incorrect--at that point the user is still logged in, has a valid session, and you can still access the protected resource. Now the server no longer generates these errors and instead, in this case, redirects the user to the parent directory of the login page, which causes the server to look for and serve the Web Application's welcome page. For more information see Configuring Welcome Pages.
042661	Fixed a problem in clustering. When a replica-aware stub is called within a transaction, it attempts to route the call to the server hosting the transaction coordinator. The problem was that the stub was sticking to this server for the life of the stub, even if it was called a second time outside of the transaction.
043010	Instances of WebLogic Server 6.0 running as a Windows service no longer shut down automatically and become inaccessible after you log out of the NT session in which the server was running in.
043493	JNDI is no longer accessed prior to it being properly initialized during server startup.
043695	The value returned by session.getId() no longer returns the same value as request.getRequestedSessionId(). Also note: to determine whether an incoming cookie has a valid session, use request.getSession(false).
043865	Fixed a problem that caused an EXCEPTION_ACCESS_VIOLATION when shutting down a WebLogic Server that uses a RDBMS realm with the Weblogic type 2 Oracle JDBC driver for Oracle 8.1.6 on win32.
044105	Fixed problems that occurred when starting the server as an NT service while using the -hotspot option.
044282	An unnecessary reverse DNS lookup has been removed.
044450	Removed unnecessary code in JDBC Store that was causing problems with TimesTen.
044556	Fixed a problem with the serialization of HTTP query parameters.
045960	IDL files generated by weblogic.ejbc can now be compiled by an IDL compiler.
044987	Fixed problems in the java socket multiplexor with applets reloading/refreshing the browser.
045091	In EJB 2.0 the transaction context is no longer lost if remove() is called on a stateful session bean with a transaction attribute of NotSupported.
046058	The WebLogic Plug-ins no longer cause a long delay when they route URL requests with SecureProxy=ON.

Change Request Number	Description
042281	A servlet no longer continues executing after the browser is closed.
044579	An incorrect IllegalStateException is no longer thrown in certain situations when a servlet in a Web Application handles file upload and then has to process the input.
045580	There are no longer problems when mapping a ServletException to an error page in web.xml.
043541	The servlet engine now properly parses all URLs not ending in '/' or an extension.

Change Request Number	Description
035788	Fixed some hyperlinks to our documentation that were broken in the Console.
038336	Fixed HTML problems in the Console where some anchors were going to the right help page but not to the right place within that page.
038359	A Multibyte machine name is now displayed correctly when creating a Kanji Machine name.
039629	On the Web App General panel of the Administration Console, there is now a check box indicating that the Web Application is deployed.
040029	A help icon in the Console is no longer displaying an Error 404--Not Found.
040101	Fixed a problem with graphs in Netscape when using monitoring in the console.
040127	On Japanese NT, fixed a problem with the Console and using localized log messages.
040181	When creating a 'Machine' on the Japanese NT, the 'CREATE' button was not making any change in the console. The create page was still virtually the same after clicking the 'CREATE' button. This is now fixed.
040820	Fixed a problem when the `Create' button was selected prematurely while trying to configure a new web application.
040846	Fixed a problem with Netscape and the WebLogic Console. When creating a new conection Factory, at the JNDIName text box, a dialog box said, "This field cannot be blank". This dialog would not disappear until killing the browser.
040865	Fixed a problem with the cluster monitoring tab in the console. It was not showing the correct number of participating servers.
040902	Fixed an unnecessary field in the console when clicking on the garbage can in the security-->group node.
041080	Fixed a problem with the console and security when creating a multi-byte group name and registering a user to the group.
041096	Fixed a problem with Japanese characters in the console.
041112	Fixed a problem with certain domain settings not being persisted and returning to the defaults on restart.
041117	The Console was having problems when `refresh' was being used regularly in the browser. These problems have been fixed.
041141	The Console no longer displays corrupt strings when the navigational tree is disabled.
041268	Fixed a problem in the Console when switching languages from Japanese to another language.
041301	In the Console, the Max Size value under the HTTP tab had a unit of kilobytes. It has been changed to bytes.
041532	Fixed problems with the Console, involving undeploying and redeploying Web Applications.
041606	When entering 'Search text' in the log customize window in multi-byte string, it was displaying the search result. But when displaying the log customize window a second time, the initial value of the string which was entered in the previous search was corrupted. This has been fixed.
041733	The Console was setting the XMLRegistry MBean attributes to "" if they are unset. This confuses the XMLRegistry which thinks the are settings to the value empty string. The XML Registry now considers "" to be the equivalent of an unset field.
041837	There was a problem starting the Console and changing the rotation type to date based in http logging and then restarting the Server.
041875	Added some information to the console for users who delete an ACL.
041943	Fixed a problem in the console when using a Kanji group name.
041944	Fixed a bug in the console when using a Kanji character as an ACL name.
041994	Fixed errors when creating a new domain using the Console.
042058	In the JNDI tree of an active server, nodes of bound objects no longer have incorrect '(access denied)' labels.
042068	Removed the ability to clone applications from the Console.
042181	The unit in which the configuration parameter "Logging -> Size Threshold" is identified now as 'kilobytes' on both the domain and server logging tabs.
042278	You can now deploy a MultiPool and specify the targets using the Console.
042434	Fixed a problem deleting a multibyte group name.

Change Request Number	Description
031228	Improved error messaging with ejbc. The full stack trace is now printed out when a NoClassDefFoundError occurs.
031852	It was possible to set transaction attributes for non-existent methods. A misspelled method name in the deployment descriptor could cause a transaction attribute to not be set. We now validate that all method names specified in the deployment descriptors actually exist in both the remote interface and the bean implementation class.
033538	Fixed a problem in EJB with queries and escape clasuses. Also fixed problems with the Java compiler and the '\' character.
034691	It is incorrect to use EJB 2.0 with WebLogic 6.0 and a WebLogic 5.1 RDBMS XML deployment descriptor. When doing so, a confusing ClassCastException was being thrown. Now we inform users that this configuration is incorrect.
035395	Finders were only working if all of the finder method parameters were referenced exactly once by the query. This has been fixed.
036007	Now we throw the appropriate error message when using ejbc for a cmp11 type bean with one of the attributes as private.
037622	Removed redundant messages (setMessageDrivenContext called, ejbCreate called, setMessageDrivenContext called) when running the sample server on UNIX.
037957	Now EJB-QL: WHERE clauses are commutative.
039179	There was a confusing and misleading error message in the EJB examples. The message was: log("UNABLE to get a connection from demoPool!"); log("Please make sure that you have setup the connection pool properly"). Now this message reads: log("Failed to lookup JDBC Datasource. Please double check that"); log("the JNDI name defined in the resource-description of the "); log("EJB's weblogic-ejb-jar.xml file is the same as the JNDI name "); log("for the Datasource defined in your config.xml.")
039477	Fixed the error message that is displayed if the ejb20.jar is not in the server classpath. There are now two distinct errors if EJB 2.0 cannot be started - either it's a LicenseException, and the user should contact a sales representative to get a license,or EJB 2.0 has not been enabled and the error message indicates where users can download the EJB 2.0 upgrade to enable it.
039518	Our CMP 2.0 code was not retrieving cmp-fields that were an EJBObject. This has been fixed.
039562	Message-Driven EJBs with the NotSupported transaction attribute are now destroyed when a System Exception is thrown.
039635	The latest revision of the EJB 2.0 spec requires that CMP and CMR fields start with a lower-case letter. We have added this check to our compliance checker, and made sure our examples do not violate this rule.
039736	If you deployed an EJB using weblogic.deploy, it copies the .jar file to the applications directory. The .jar file cannot be removed from the applications directory. Attempts to remove the .jar file result in the following message: C:\weblogic\dev\src\tools\weblogic\qa\tests\config\mydomain\applications>rm matt.jar rm: cannot unlink entry "matt.jar": The process cannot access the file because it is being used by another process. This has been fixed.
039818	Fixed AssertionError when Primary Key fields were Serializable objects.
040052	Removing a bean from a M-N relationship wasn't removing join table entries. This has been fixed.
040066	The setting max-beans-in-free-pool now determines the maximum number of concurrent instances that can be created to service messages. It is bound by the number of ExecuteThreads.
040108	EJB Compliance Checker now allows java.lang.Object as the primary key type.
040303	Having two EJBs with the same <abstract-schema-name> creates an inaccurate and misleading error message: org.xml.sax.SAXParseException: The content of element type "ejb-jar" must match "(description?,display-name?,small-icon?,large-icon?,enterprise-beans,dependents?,relationships?,assembly-descriptor?,ejb-client-jar?)". We have added a compliance check for this problem.
040461	Set transaction state to committed as soon as the last ackCommit message is received.
040469	Previously when you added a message-driven entry to your ejb-jar.xml file but neglected to add its counterpart to the weblogic-ejb-jar.xml file, ejbc did not give you an error message. This has been fixed.
040470	If a EJB fails to deploy all of the ejbs within the ejb, now the jar file will be undeployed.
040564	Added support to EJB for instances when a Primary-key includes a foreign key column for 1-n and 1-1 relationships.
040586	The EJB compliance checker now ensures that finder return types are the remote interface, java.util.Collection, or java.util.Enumeration.
040593	The EJB comliance checker now detects when the EJB-QL for a finder method contains a SELECT clause.
040594	Using an abstract base class to declare the public abstract getter and setter methods for the CMP fields of an EntityBean, ejbc wasn't able to find the methods on the EntityBean and refusesd to code-generate the container classes. This has been fixed.
040697	Fixed a ClassCastException when undeploying Message-Driven EJBs.
040740	Enabled monitoring of managed servers in deadlock and overload situations.
040788	We now allow message driven bean users to specify NO_ACKNOWLEDGE or MULTICAST_NO_ACKNOWLEDGE for their acknowledgement mode.
040907	Fixed a problem with message driven beans when calling other EJBs in the same ejb-jar.
040924	Now we conform to the latest EJB spec revisions, which don't allow protected CMR get/set methods. These methods must now be public.
041041	Improved performance using EJBs and big CMP 2.0 creations.
041055	Before SQL was generated, an error was not being caught when a CMP field and a CMR field were mapped to the same database column.
041133	The current version of the EJB QL spec states that the 'FROM' clause is required in every query (see EJB2.0 spec sec 10.2). The examples have been updated to reflect this.
041284	Message-Driven EJBs now support external JMS Providers.
041306	During JSP compilation, the EJB interfaces within the same application were not available. This has been fixed.
041369	Fixed AssertionError when EJBMetaData was used from within the server and the EJB's classes were not in the classpath.
041430	When there was a NoClassDefFoundError within ejbc, the stack trace was being omitted. This has been fixed.
041728	When deploying CMP Beans, if the DataSource/Connection was unavailable, users were seeing a misleading message which suggested that the Bean's table didn't exist. This has been fixed.
041801	A ClassCastException was occurring when replicated stateful session beans were compiled without an In-Memory replication license and then deployed in a server with the proper license.
041918	Calling a replicated stateful session bean in a non-clustered server no longer causes an Assertion Failure.
041937	If <primkey-field> isn't a CMP-field, users were getting a java.lang.NullPointerException. This has been fixed.
041986	The EJB compiler was generating invalid SQL queries for the finder methods of 1.1 CMP Beans.
042041	1-N relationships were failing when the beans in the relationship had a compound key, and when the foreign-key used in the relationship was also part of the primary key of one of the beans. The failures manifested when a bean participating in the relationship was removed, and also when ejbc is run in some cases (ejbc fails). This has been fixed.
042132	Any EJB method whose name starts with `remove' was being deployed as NotSupported. This has been fixed.
042217	EJB QL queries that contained a 1-1 or 1-n join weren't working with compound keys. This has been fixed.
042430	The RemoteException detail field is now set correctly in EJB.
042483	Fixed a problem when an EJB marks a transaction for rollback and then calls the RequiredNew method.
042637	When removing a bean, the server wasn't initializing the bean's CMP variables before putting it into the pool. This caused errors later if the bean was reused. This has been fixed.

Change Request Number	Description
037669	The WLEC university sample was failing to make a connection when the connection pool initializes. The server couldn't connect because the password specified by the example is greater than 8 characters long. This has been fixed.
039403	In the left hand pane of the console, the audit provider example (found at /security/audit/package-summary.html) was referencing an Audit Provider node that didn't exist. This has been fixed.
040411	When using the Administration Console with the Examples server and the default Cloudscape RDBMS realm, you can now shut down the server. Attempts to shut down the server were failing because the user guest did not have shutdown permission for weblogic.admin. The example Cloudscape database did not contain the appropriate ACL to allow the user guest to shut down the server.
040429	Fixed a problem in our examples. In the security acl example the documentation has a typo; java examples.security.acl.Client t3://localhost:7002 joeuser joepass should have been: java examples.security.acl.Client t3s://localhost:7002 joeuser joepass.
040508	Modified all examples to use java.rmi and JNDI instead of weblogic.rmi.
040633	After undeploying the Pet Store Web Application and then deploying it again to a managed server a javax.management.MBeanException was being thrown. This has been fixed.
040682	The JAAS security example was missing an implementation of AltClient. AltClient is the client side implementation showing how to use mutual authorization with WebLogic.
040954	Added seven new XML examples.
041643	Fixed the cluster connection string example. WebLogic requires that all members of a cluster share the same port.
042136	The examples.utils.ddl.demo.ddl file has a mistyped statement; an extra T in DROP: (DROPT table).
042140	A DataSetException was occurring when trying to execute the samples\examples\dbkona\rowid example. This has been fixed.
042213	In the date and phoneBook examples, there was an error in the documentation. Under Run this Example, "From the toolkit's General Menu," should have been: "From the Nokia Active Server manager general Menu."
042244	The setExamplesEnv script and the startExamplesServer script now include the xmlx.jar in the CLASSPATH.
042256	The web.xml in the examplesWebApp did not have a taglib-uri element for the xslt tag library.
042261	Improved the documentation in examples/i18n/logging/startup/package-summary.html
042583	When building the ejb/simpapp WLEC sample, the jspc compiler complains that it can't find the web.xml file. We added a -webApp flag to the jspc command to fix this. There was a similar problem, also fixed, with examples/jdbc/pool/build.cmd.
042585	The instructions for running the university samples say the following: Start a web browser and enter the URL for UniversityForm.html. For example: http://localhost:7001/examplesWebApp/UniversityForm.html But the name of the file is actually universityForm.html. (The 'U' in university should have been lowercase.)
042586	The WLEC Simpapp Servlet example now catches any PoolUnavailable exceptions.

Change Request Number	Description
035036	When WebLogic boots and prompts for the boot account's password, the prompt used is now internationalized.
041021	Fixed a problem failing to generate properties files for some message catalogs after executing l10ngen.
041078	Fixed some duplicated keys in the english.xml file.
041264	Fixed some internationalization problems with certain tags not being in english.xml.
041266	The time stamp is now internationalized.

Change Request Number	Description
033423	There were dbKona problems with QueryDataSet and the OCI805_8 driver. This has been fixed on Windows NT, but is still a problem on HPUX and Solaris.
033920	Change There was a problem in JDBC when running tests which access the connection pool.
035530	There were problems enabling OS authentication and using Oracle 8.1.6/oci8 with the jDriver. This has been fixed on NT and HP-UX, but still is an issue on Solaris. We have added an error message that reports this problem: OS level authentication is not currently supported due to a defect in OCI 8 libraries.
037589	Added Oracle thin driver support and fixed some outdated command line help.
037591	Added support for ORACLE_THIN database type. Removed obsolete database types and command line options.
037693	There are no longer problems with the Oracle driver and ROWID selects when running examples.dbkona.rowid.
037893	Fixed getBytes() to return null instead of a zero-length byte array with Oracle LONG RAW columns.
038143	JDBConnectionPoolRuntimeMBean's were not working. Added a RuntimeMBean implementation to ConnectionPools.
038229	The jDriver for Oracle 8.1.6 caused managed servers to run out of memory.
038275	We no longer refer to the weblogic.classpath in one of our JDBC error messages. The weblogic.classpath does not exist in WebLogic 6.0.
040379	The following error occurred when the server and serverName properties in a JDBC connection pool were specified with the same value: <Cannot startup connection pool "jtaXAPool" server and serverName properties must have the same value> This problem was seen when the XA driver requires the server or serverName property to be set. It was occurring with the WebLogic jDriver for Oracle, but not the Oracle thin driver, or the Cloudscape driver. It has been fixed.
040509	Fixed a small problem with Solaris 2.6 and the jdriver.
041286	Better error message for misconfigured connection pools
041302	The MS SQLServer driver has been updated.
041514	Added support for JDBC and connection pool monitoring in the Console.

Change Request Number	Description
038109	The JMS connection is now cleaned up properly when the client terminates without closing.
039249	The managed server no longer has a memory leak when it monitors JMSServer using the Administration Console.
039802	Closing non-durable subscriber messages that were not being pushed to the subscriber at the time, such as messages for the synchronous subscriber, was sometimes causing message statistics to become out of sync. This has been fixed.
039921	A multicast subscriber was not able to receive multicast messages on Solaris machines. This has been fixed.
040088	Problems were occurring when attempting to send messages from a connection consumer's listener class OnMessage method using the same session that a session pool uses to send messages to the connection consumer.
040479	Fixed a bug in JMSHelper that was causing incorrect xml to be written to the config.xml file.
040793	Recovered unacknowledged messages were not being marked as Redelivered. This has been fixed.
041617	The JMSMessageID converted using the JMSHelper no longer adds an extra zero at the end.
041691	Fixed a bug in JMS that causes Message-Driven-Beans to hang when the trans-attribute flag in the ejb-jar.xml file is set as Required.
042461	When sending a message from WebLogic Server JMS classes through a IBM MQ JMS sender and the correlation ID for the message is null, the IBM code was calling WebLogic with setJMSCorrelationIDAsBytes(), which is not supported. We now convert the bytes to a UTF8 string and store it in the correlation id in order to handle setJMSCorrelationIDAsBytes.
042484	When trying to create an ObjectMessage with an object that was not in the classpath and within a bean, JMS was throwing ClassNotFoundException. This has been fixed.

Change Request Number	Description
038831	The Apache plug-in was failing under heavy load. This has been fixed.
040817	When using IIS to browse and call a regular JSP page that calls a Java Bean and getting a ResultSet reference, there were problems when submitting through the FORM POST method. The HTML stream was getting truncated when it came back to IIS--in other words, the page was only partially painted. This has been fixed.
041332	Using plug-ins, MatchExpression can now contain multiple, comma-separtated expressions.
041534	Using the mod_wl.so, Apache was not proxying without Debug and DebugConfigInfo in the httpd.conf. This has been fixed.
041580	The Apache plug-in MatchExpression now works if an encoded URL is used.
041745	Added a log message when the trusted CA file isn't specified and SSL is used with the Isapi plug-in.
041754	Fixed an infinite loop when ISAPI was configured for SSL but using a non-secure port.
041939	The Apache plug-in wasn't filtering out the header "transfer-encoding"="chunked". So the browser was failing to handle these responses, causing Netscape to hang and IE to display an error page. This has been fixed.
042482	The NSAPI and Apache plugins were having a READ timeout on HPUX-11. These problems have been fixed.

Change Request Number	Description
026488	Fixed a problem with servlets when the parameter to method println(String) was null.
029989	The wrong error message was sometimes being sent when an UnavailableException was raised within a servlet.
030880	Fixed problems compiling JSPs when debugging was turned on. Now you can specify compiler flags in weblogic.xml. For example: <!-- weblogic.xml: weblogic-specific web app descriptor --> <weblogic-web-app> <session-descriptor> </session-descriptor> <jsp-descriptor> <jsp-param> <param-name>compileCommand</param-name> <param-value>jikes</param-value> </jsp-param> <jsp-param> <param-name>compileFlags</param-name> <param-value>+E -nowarn</param-value> </jsp-param>
041478	There was a change in session cookie format that also fixed some problems with URL rewriting.
037771	Optimized the checking of JSP's for reloading.
038739	Improved support for JSP debugging.
039083	The RequestDispatcher and forwarding a JSP page now works correctly.
039193	When users forgot to make their servlet class public, a vague and unhelpful error was being thrown. This no longer happens.
039530	Fixed our internal servlet tags to reset their state on release. If you used the same tag more than once on a page the additional tags kept the stale data from the previous tag.
040171	The attribute SingleThreadedServletPoolSize was not settable through the Administration Console. This has been fixed.
040338	Some servlets were functioning, but were not showing up in the mydomain>WebApplications>DefaultWebApp_myserver>ActiveServlets window of the console. This has been fixed.
040662	When JSP files had a page tag, the JSP compiler was not generating a class, or java file. This happened only with command line jspc. This has been fixed.
040766	Fixed a problem in servlets with using ../ for a relative URL when doing a response.sendRedirect.
040814	Added more informative error messages for instances when user errors cause exceptions using servlets.
040843	Fixed problems with deploying WebAppComponents using virtual hosts.
040981	Fixed problems associated with WAP and session cookies using the pipe characters.
041234	Fixed a problem in JSP/Servlets using POST and HTTPS.
041605	There was a problem with JSPs where the compiler error page displayed a corrupt error message from javac. This has been fixed.
041684	Fixed a problem in servlets. The XSLT tag threw a SAXParseException while proceesing XML content.
041729	The weblogic.servlet.jsp.Precompiler didn't honor weblogic.xml parameters, like workingdir, packagePrefix, etc, for the JSPs that it precompiles. This has been fixed.
041945	When the web.xml had the setting inputCharset./A=Shift_JIS inputCharset./B=EUC-JP, and two clients simultaneously accessed the JSP/Servlet, WebLogic failed to handle these string correctly. It was possible to get the correct result from one client, but not from the other. This has been fixed.
042031	In the webapp data table, when you click the monitoring icon for any webapp and then click on the monitor link in the Servlets column, the correct heading is now displayed.
042293	Servlet URL rewriting was working fine with IE 5.0 but wasn't working with Netscape 4.7. This has been fixed.
042509	Fixed some problems when forwarding from one web application to another web application and using some form of authentication in both. Some session data was incorrectly getting shared across the applications

Change Request Number	Description
039096	You no longer have to restart WebLogic Server to make it aware of a newly added entry to the XML registry.
039247	Custom parsers are now correctly invoked when an XML document that has been configured to be parsed by the custom parser is parsed using the setAttribute() method of the Servlet API.
041734	WebLogic's JAXP implementation no longer requires that the input stream that contains an XML document that is about to be delegated to a particular parser for parsing be resettable.
041778	A NullPointerException error is no longer thrown when an XML document that contains an external entity that has been correctly registered in the XML registry is parsed.
041797	After creating a new server, the server was failing to reboot and the config.xml had some incorrectly parsed headers. These problems have been fixed.

Change Request Number	Description
035039	When WebLogic needs to prompt for the boot password, first it should log (in security.xml) that it is prompting. This would allow an administrator on a remote machine to know why the machine is apparently "hung". This now happens.
036141	A managed server was not starting if guest had been disabled (in order to do a JNDI lookup in an ACL). This has been fixed.
036604	The method ClusterMBean.setDefaultLoadAlgorithm() no longer accepts illegal values and throws the proper IllegalArgumentException.
036986	Using Weblogic's XA driver with CMP was failing at deployment time. This has been fixed.
038883	Specifying the root directory when starting the server was not working when the root directory was not under a /config directory.
039066	If you entered an incorrect password when prompted at system startup, the server just tried to start anyway. The startup eventually fails. Now we reprompt for the password when the password is wrong.
039182	When binding two clusterable objects implementing the same interface to the same JNDI name on a single server, an exception was not being thrown and the first clusterable object was being bound. This has been fixed.
039249	A managed server had a memory leak when it monitored JMSServer using the Administration Console. This has been fixed.
039361	If you used the rdbms realm and created a group, you could not delete the group. This has been fixed.
039891	Fixed a problem with the server not setting the context attribute correctly during servlet initialization.
039960	Log Viewer is now working in Non-US Locales.
039995	A server startup error no longer occurs after a WLEC Connection pool was created using the Administration Console.
040168	The logging example for internationalization failed when a dot (.) occurred in the path. This has been fixed.
040177	Additional user information was required when converting weblogic.properties files for use with WebLogic Server 6.0. This has now been added to the product documentation.
040178	When you were using the conversion utility, if a weblogic.properties file included the property weblogic.httpd.register.Name=weblogic.servlet.FileServlet and the servlet did not have initial arguments associated with it (it does not have the property weblogic.httpd.initArgs.file=arg1=value defined in the same weblogic.properties file), then the conversion utility was throwing a Null pointer exception. This has been fixed.
040213	The listenport of the managed server cannot be the same as the administrative listenport. You cannot, for example, use localhost or 127.0.0.1, with the 7001 host number on both the managed and administrative servers. Added a more descriptive and informative error message when this occurs.
040297	Fixed a bug that was causing attributes set in application.xml not to propagate from administration servers to managed servers.
040405	The config.xml file is now serialized using the Apache XML serialize classes. This results in the correct XML, including escapes for built-in entities and an XML header with encoding specified. The encoding used is the platform default. This also fixes problems with the "&" character.
040659	When specifying getParameter() encoding as iso-8859-1, the POST method is now working properly.
040688	Targeting a mail session to a server that is part of a cluster, the following exception was being thrown since the mailsession was not serializable: java.io.NotSerializableException: javax.mail.Session. This has been fixed.
040899	Fixed a problem with a start-up class when the converter utility converted startup weblogic.properties into .xml.
040950	Fixed a problem in JTA. For XA connections, the Connection Pool test connection logic was attempting to start a distributed transaction before executing the testing SQL. This had the potential to create a javax.transaction.NotSupported exception.
041157	The dialog tabs in the Console were not working correctly when the Mbean name contained Kanji characters.
041290	If the username property is set from the weblogic.Admin or weblogic.Server command lines, the username must be the system password. Note however, that the username syntax is retained to prevent breaking a user's scripts. The weblogic.management.password property value must be the system password and the username may not be modified in the config.xml file.
041662	To improve JTA, we now advertise resources on JNDI. Resources were dynamically discovered as transactions go along, but now it is also possible to find out which resources are currently being supported at which servers.
041757	Fixed a problem with JTA. Resource advertisenment (JNDIAdvertiser) was incorrectly done under the caller's identity. We now use the system identity while doing this operation.
041845	Updated the NTRealm to generally improve usabilty and functionality.
041854	To help support Java WebStart with WebLogic Server 6.0, we now provide a default Web Application with the web.xml configured for this mime type. We have also provided other mime type mappings.
041995	Fixed an Unexpected Error being received in the console when resuming an active server. Also deleted some extraneous informational messages in the console when adding users.
042183	When the config.dtd was being generated in the console it was appearing with some errors. This has been fixed.
043388	Clusters of WebLogic Servers no longer require the use of a shared network drive. Both the WebLogic Server installations and your applications can now reside on local file systems.