BEA WebLogic Server 4.5.1 and 4.5.2

 

The following document lists the differences between Weblogic Server Version 4.5.1 and WebLogic Server Version 4.5.2. The WebLogic Server 4.5.2 was based on the 4.5.1 release, yet there are some differences. The 4.5.2 release was made public in June of 2000 and it's first service pack was made available in September. The 4.5.2 Weblogic Server with Service Pack 1 was, except for the discrepancies listed below, modeled on the 4.5.1 version with WebLogic Service Pack 11 installed. The following lists the disparate issues between Weblogic Server 4.5.1 with Service Pack 11 and WebLogic Server with Service Pack 1.

The following changes are in WebLogic Server 4.5.1 (with Service Pack 11 installed) but not in in WebLogic Server 4.5.2 (with Service Pack 1 installed):

• Issue 31738: Fixed a problem with Classloader where is was throwing an NPE when the service pack jar was put in the clients classpath.
• Issue 32100: Fixed a problem in Server where an ArrayIndexOutOfBounds was being thrown due to incorrectly computing message size when the size field falls on a Chunk boundary.

The following changes are in in WebLogic Server 4.5.2 (with Service Pack 1 installed), but not in WebLogic Server 4.5.1 (with Service Pack 11 installed):

• CR024253(Issue 3796): Upon customer request, WebLogic Sever now supports HTTP access log rotation.
• CR028155(Issue 7734): In the file TimeServicesImpl.java, the currentTime Millis() method was performing incorrect calculations to compute the Offset. The calculations have been corrected.
• CR029085(Issue 8734): JDBC drivers need to work around the new synchronization in DriverManager.println. JDBC 2.0 has made println a synchronized method, which may lead to deadlocks between getConnection and other methods that call println. This problem was solved by reorganizing when and where the println method is called.
• CR030406(Issue 10073): The JSP Java File naming convention was altered. The naming standard has been reverted to prepending an underscore to generated file names.
• CR030441(Issue 10108): Fixed a problem with the readability of Japanese messages output by JSPs. ByteArrayOutputStream does not properly handle double-byte chars. CharArrayWriter is now used instead.
• CR030944(Issue 10617): The setObject method was passing an object reference instead of object copy.
• CR031006(Issue 10679): Fixed a problem with a cookie never being set if setCookie is issued, and a res.sendRedirect is issued after. With the apache plugin, the redirect is sent before the cookie is set in the header.
• CR031211(Issue 10885): Fixed a problem with the Apache plugin. The 401 Error code was not being propegated back to the client. If the client calls a servlet, on which an ACL is set, through apache, there will not be a prompt for username and password, but rather "No credentials supplied".
• CR031274(Issue 10948): Per customer request, WLS now has the ability to proxy HttpClusterServlet in order to proxy requests to multiple servers.
• CR031287(Issue 10961): Modified server's timing as heart beats are not being processed in time. This is because the server was not processing heart beats in the same thread.
• CR031304(Issue 10978): In adding the functionality of HTTP log access rotation, a flag needed to be set marking the log rotated at the correct time.
• CR031312(Issue 10986): Certified the Apache plugin with Raven 1.4.3/Apache 1.3.12. The previous version of Covalent Raven SSL used Apache 1.3.9, but is no longer available.
• CR031343(Issue 11017): Fixed problem with plugins returning double Content-Type headers for JSP pages. This problem appears differently on different browsers. Something in the plugin is inserting Content-type=text/jsp into the header, when it should be text/html. This bug is in the proxy.
• CR031361(Issue 11035): Fixed a problem where JSPs were getting compiler errors. These errors were logged because the compiler was seeing java reserved words in file names. The file naming standard was reverted to an unproblematic naming system.
• CR031889: Fixed a problem in JSPs, where setProperty values were not replicated across a in-memory-state-replicated session. The problem was fixed by ensuring that the session.putValue() method was called whenever useBean is updated and the bean's scope is session.
• CR031943: Fixed expression constructor so the longProperty will work. One particular piece of data was being cast as an int rather than as a long.
• CR032090: Fixed a problem where "java.security.AccessControlException: access denied" was being logged. With Java 2.0, reading system properties is allowed only by special permission. Applets needed to have this permission to gain access to the system property ignoreIncomingProtocol.
• CR032174: Location tags embedded in VirtualHost tags have been fixed to correctly work with the apache plug-in. This was done by adding locationKeys, pathTrimTable, and pathPrependTable in ConfigInfo structure to handle more than one location tag used in virtual hosting.
• CR032309: Fixed a rare problem with the dispatch in-thread pattern resulting in a deadlock.
• CR032634: Enhanced performance in the JDBC. The messageIdBlockSize was set too low. The number to which this property is set determines how often there is an extra database hit(per productive data base hits).
• CR032576: Fixed a problem with inconsistent character sets. While characters were being buffered, they were represented by the 8859-1 codeset. However, once the buffer overflowed, the remainder of the characters were represented by UTF8. This was resolved by representing all characters with the 8859-1 codeset.
• CR032806: In HTTP logging, if a log rotation's begin date has past, DAY_OF_WEEK should only be used in setting a new date if the rotation time period is greater than a week.
• CR032952: Fixed another rare case where dispatch in-thread pattern resulted in a deadlock. Avoid sending out the transaction context as part of the remote call to create, update or remove secondaries used by the in-memory replication machinery. Part of the reason is that not sending the context is more efficient especially under heavy loads and also due to rare cases where there is a potential deadlock while deserializing the transaction context.
• CR033252: Fixed a problem in exception handling. Now a message is logged when a remote exception is caught while trying to create a secondary.
• CR033255: Fixed a problem with the over-synchronization of theDriverManager.getConnection() method. This problem was resolved by synchronizing this method with the less synchronized method, Driver.connect().
• CR033256: Per customer request, a property, setEmptyStrings, was added in JSPs that gives users the option of allowing a bean to take String attributes even when the request attribute is the empty string.
• CR033603: This fix only applies to stateful session beans running in a cluster accessed by java clients either in standalone applications or applets. Upon handle reactivation of the stateful session bean, there was no guarantee that the client would get back the reference to the bean on the server to which the bean was pinned. The fix is to make the client aware of the stateful session bean server and go back to the same server that the stateful session bean is actually on. Accessing this fix requires the redeployment of /weblogic/ejb/internal/HandleImpl.class on the client.
  
  

  ---

  Back to top

   

  

  Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.