bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Release Notes

Resolved Problems for Service Pack 7

Service Packs are cumulative. Service Pack 7 contains all the fixes made in earlier Service Packs released for WebLogic Server 7.0. For a description of fixes made in earlier Service Packs, see Resolved Problems for Service Packs 1 - 6.

The following sections describe problems that were resolved in WebLogic Server 7.0 Service Pack 7:

- Administration Console

- Clusters

- Core Server

- Deployment

- EJB

- JDBC

- JMS

- JSP

- JTA

- JVM

- Node Manager

- Operations, Administration, and Management

- Plug-ins

- RMI

- Security

- Servlets

- Simple Network Management Protocol (SNMP)

- Web Services

- XML

Administration Console

Change Request Number | Description
--- | ---
CR082722 | The Deployment Descriptor Editor did not properly handle the <unchecked/> method permissions in the ejb-jar.xml file. This problem has been resolved.
CR108255 | If you tried to create a Japanese user name in the English version of WebLogic Server Administration Console (Group Tab), a weblogic.management.utils.NotFoundException was thrown. This has now been resolved.
CR109110 | Prior to this release, if the WebLogic Server Administration Console was used to delete a WTC object that had already been deleted, it threw a InstanceNotFoundException and displayed the stack trace in the Console. A meaningful error message is now displayed in place of the stack trace.
CR122389 | WebLogic Server ignored case sensitivity when it came to names of a node. As a result, it listed a node only once in the JNDI tree even if there were multiple nodes that had the same name, but different case. This problem has been resolved.
CR209949 | When comma separated multiple directories were specified as values for the alternateTypesDirectory property, WebLogic Server did not load valid archives present in these directories. Archives were loaded only when a single directory was specified for the property. This problem has been resolved.
CR216670 | When you exceeded the number of authentication attempts, a message was logged on the domain displaying that you were locked out. Now, the Administration Console also displays the lockout message.
CR216851 | The Define Security Policy and the Define Scoped Role pop-up menu options are no longer available for JMS bridge destinations.
CR238054 | Monitoring statistics related to EJBs were not displayed in the WebLogic Server Administration Console. This problem has been resolved.
CR239018 | CreateException occurred when you configured a security policy for a JMS destination. This problem has been resolved.
CR241554 | When the MSI File Replication Enabled check box was selected for starting the Managed Server in the Independence (MSI) mode, the configuration file (config.xml) was incorrectly copied as msi-config.xml instead of config.xml in the Managed Server's root directory. Since the config.xml file could not be located during server bootup, the Managed Server failed to start in the MSI mode. This problem has been resolved.
CR241861 | Monitoring statistics related to web application were not displayed in the WebLogic Server Administration Console. This problem has been resolved.
CR253611 | A NullPointerException was thrown in the WebLogic Server Administration Console when you tried to configure a new user after changing the user password. This problem has been resolved.
CR255254 | The AuthCookieEnabled attribute associated with a Web Server MBean could not be set through the WebLogic Server Administration Console. This problem has been resolved.

Clusters

Change Request Number | Description
--- | ---
CR241267 | If a server was no longer available in the cluster, there was a possibility of an invalid server lookup occuring. This was because an internal hash table was not being properly updated. This problem has been resolved.

Core Server

Change Request Number | Description
--- | ---
CR132806, CR126374 | The Thread.currentThread().getPriorty() method, used to determine the priority of the current thread, returned the default value instead of the actual priority that was set during configuration. This problem has been resolved.
CR196369 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/138
CR200568, CR128417, CR134918, CR172274 | Sometimes server-side sockets remained in an IDLE state when a client issued a reset on the socket before the server could set the TCP_NODELAY option. Therefore, these IDLE sockets were not getting cleaned up properly. Now, when an exception occurs when setting the TCP_NODELAY option on the socket, server-side sockets are cleaned.
CR210488 | Exceptions occurred during compilation of an EJB with IIOP on AIX platforms. This problem has been resolved.
CR211299 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/156
CR218491, CR201647 | WebLogic Server threw UnmarshalException with nested OptionalDataException after EJB tier was restarted, due to synchronization issues with the BasicReplicaList class. This problem has been resolved.
CR236296 | A memory leak occurred when the call-by-reference-enabled property was set to False and a JSP was calling an EJB. This problem has been resolved.
CR239324, CR239819 | If a socket is unregistered and then registered, and if between the two calls the timeout timer never ran, the data structures would get unsynchronized, preventing the newly-registered socket from timing out. This problem has been resolved.
CR243895 | While invoking a remote EJB, the ConcurrentModificationException occurred because a HashMap was simultaneously modified by two threads. Now, access to the HashMap has been synchronized.
CR248250 | When a remote object was accessed remotely and locally (within the server), the local access caused data corruption, causing load balancing to fail in both cases. This problem has been resolved.

Deployment

Change Request Number | Description
--- | ---
CR215116 | By default, if auto deployment is enabled, applications are automatically undeployed when they are deleted from the applications directory of the server. However, if an attempt was made to copy an application to this directory (after the delete operation), WebLogic Server would throw an UndeclaredThrowableException. This problem has been resolved.

EJB

Change Request Number | Description
--- | ---
CR122378, CR200204 | When an EJB that had both local and remote interfaces was deployed and accessed from a Web client deployed in the same application (EAR), a ClassCastException was thrown when create was called on LocalHome. This problem has been resolved.
CR187691 | You might encounter a CacheFullException if the findByPrimaryKey method is called, when the concurrency-strategy property is set to Exclusive, and the cache-between-transactions property is set to True for an entity bean. This problem has been resolved.
CR221686 | When a JSP with 100 or more EJBs in an EAR file was accessed, compilation by the container failed because of the command length limitation (for the forked process). Now, by default, JSPs and EJBs are compiled inline because inline compilation does not have this limitation.
CR229290 | During EJB compilation, Weblogic Server did not honor the options specified in the extra-rmic-options element of the config.xml file. This problem has been resolved.
CR240649, CR174593 | WebLogic Server threw a ConcurrentModificationException when a finder of an entity bean was invoked in the ejbStore method, and new entity beans were enrolled in a transaction of this method, or when entity beans of the same type were modified in this method. This problem has been resolved.
CR258768 | AssertionError was encountered when a user with insufficient privileges called the remove() method on a stateful session bean. The right message, AccessException is now thrown.
CR261092 | WebLogic Server no longer throws an XAER_PROTO error with MQSeries as the JMS provider.

JDBC

Change Request Number | Description
--- | ---
CR108103 | Statistics related to the JDBC connection pool waiters sometimes showed an improper value, under load. This problem has been resolved.
CR214723 | SQLException occurred when a Portal application was deployed using a 10g driver with Oracle database whose character set was set to JIS16EUC. This problem has been resolved.
CR241211 | NullPointerException occurred at startup because XAConnection created before TxDataSource did not have any non-null data source assigned to it when called by Connection.reserve. This problem has been resolved.
CR242502 | Now, XAER_NOTA exceptions that are thrown because of recovery are printed in the server logs only when the JDBC debug flag is turned on.
CR249009, CR243824 | When enlist failed, XA.end was not called, to disassociate the transaction from the connection, before releasing the connection to the pool. This problem has been resolved.
CR256316 | InvalidTransactionException occurred when a suspended transaction that had timed out was resumed. This problem has been resolved.
CR263367 | JConnect Driver for Sybase has now been updated to JConnect 6.05 in the product package.

JMS

Change Request Number | Description
--- | ---
CR172511, CR174691 | Closing a JMSConnection session before closing all JMSConsumer clients first could cause a memory leak. This problem has been resolved.
CR176366 | When the getObject() method is set on the Boolean.TYPE in the onMessage() API, it throws the following JMSException: javax.ejb.EJBException: nested exception is:weblogic.jms.common.JMSException: Error deserializing object weblogic.jms.common.JMSException: Error deserializing object This problem has been resolved.
CR177558 | A server-side memory leak no longer occurs with NO_ACKNOWLEDGE delivery mode.
CR178775 | When a JMS client repeatedly opened and closed JMS connections against WebLogic Server, JMSConnection and related objects such as DispatcherWrapper were not being released in both the client and the server side. This caused an OutOfMemoryError, which occurred when the client retained one open JMS connection while opening and closing other JMS connections. This problem has been resolved.
CR187610 | JMS Bridge was not using the Messaging Bridge Thread Pool for bridge dispatch requests. Now, JMS Bridge uses the Messaging Bridge Thread Pool if one has been configured. If there are not enough available threads configured in the Messaging Bridge Thread Pool, the bridge uses the default execute thread pool. Bridge also logs a warning message if the configured Messaging Bridge Thread Pool size is insufficient and then attempts to obtain a thread from the default execute pool instead.
CR216063, CR256579, CR234758 | MessagingBridgeRuntime mbean getState() is now properly refreshing state information.
CR226919 | A JMS memory leak that was caused by a temporary destination delete() failure no longer occurs.
CR229495 | Client no longer hangs while waiting for acknowledge completion when the backend JMS server goes down.
CR235404 | Memory leaks were encountered if the producer was not explicitly closed before closing the client connection. This problem has been fixed.
CR239642 | NullPointerException no longer occurs in BESession.acknowledge().

JSP

Change Request Number | Description
--- | ---
CR217352 | When a JSP was accessed using an invalid URL, the 404 error was not thrown due to improper JSP mapping. This JSP mapping issue has now been resolved by changing the default value of exactMapping to true in the code. If required, this value can be set to false in the weblogic.xml file.
CR219805 | Compilation of JSP no longer fails when Java comments span multiple scriptlets as shown below. <%/*%> [HTML code] <%*/ { /*comment*/ } %>
CR242858 | When the wl:summary tag available in Weblogic-vtags.jar was used by JSPs, the query string was not passed to the next page. This problem has been resolved by adding the AddQueryParams optional boolean field to the wl:summary tag. When the AddQueryParams field is set to True, the query string is appended to the URI.
CR254360 | ClassNotFoundException was thrown for classes in the WEB-INF\lib directory when weblogic.jspc was used, and the application code used the context classloader. WebLogic Server no longer throws a ClassNotFoundException under these circumstances.

JTA

Change Request Number | Description
--- | ---
CR048979 | A race condition no longer occurs when multiple enlistments of JTS connections attempt to initialize the resource at the same time. As a result, WebLogic Server no longer throws a javax.management.InstanceAlreadyExistsException while trying to get a JTS connection.
CR213034 | Redelivery of JMS message did not occur after migration on transacted messages. This problem has been resolved.
CR215559 | When a resource involving a global transaction threw a Heuristic Hazard Exception, the transaction was declared completed regardless of the fact that all the subcoordinators and resources had not responded to the commit. Ideally, during a commit process, if one of the subcoordinating servers is down, the coordinator should not have committed till such time that it heard from all resources and subcoordinators. Because WebLogic Server did not allow all subcoordinators to complete the commit call, transactions remained pending even though the transaction had been declared committed. The problem has been resolved.
CR249090 | When a transaction reaches the prepare phase, as it approaches its timeout, there is a possibility that a negative value could be passed to the Object.wait() method. This results in an IlegalArgumentException being thrown by the wait method which is then wrapped by a SystemException exception and thrown to the commit caller. This problem has been resolved.

JVM

Change Request Number | Description
--- | ---
CR218538, CR241553 | A JAVA LEVEL DEADLOCK no longer occurs when the RJVM is being shut down.
CR252304 | When the RMI service of a remote server was called from a servlet after a MaxMessageSizeExceededException occurred, some threads stopped indefinitely at the status of waiting for an RMI response. This problem has been resolved.

Node Manager

Change Request Number | Description
--- | ---
> CR111339, CR237367 | Attempts to start multiple WebLogic Server instances using Node Manager on slower hardware produced the following error:
>     <Jun 25, 2003 5:16:15 PM CDT> <Error> <NodeManager@192.168.190.4:5555> <__COMMAND_EXCEPTION__Request: failed to execute command 'online' on server 'ifgw1catapp4 - reason: '[JavaProcessControlOnline: Could not get valid pid for WebLogic process.]'>
This problem occurred because Node Manager looked for the PID file before there had been a chance to write to that file. A new property allows users to specify how many times Node Manager will retry reading the PID from the file. Every retry will have a 2 second wait. The property introduced is PIDFileReadRetryCount, which can be specified as a system property or in the nodemanager.properties file. When the value of PIDFileReadRetryCount is greater than zero, Node Manager attempts PIDFileReadRetryCount number of times before giving up on reading the PID from the file. The default value of PIDFileReadRetryCount is zero, so there is no change in default behavior.

Operations, Administration, and Management

Change Request Number | Description
--- | ---
CR179126 | An InvalidAttributeValueException was thrown by the weblogic.Admin utility when the addTarget method was invoked using the utility on an Administration server hosting a JMS server, and the JMS server was not yet targeted. This problem has been resolved.
CR189763 | When a staged application was deployed to a server running in MSI mode, the server incorrectly created a staging directory. Now, when a staged application is deployed on a server running in MSI mode, WebLogic Server determines whether to use an existing staging directory or create a new one. As a result, there is no InvalidAttributeValueException when deploying to a server running in MSI mode where the server process does not have write access to the directory structure.
CR196774, CR135780 | When a WebLogic configuration property was used while booting WebLogic Server and that property was unknown to the WebLogic Server management subsystem, a message of severity WARNING was being logged. The Message severity was lowered to INFO and the message text was changed to accurately reflect the nature of the message.
CR224350 | When there was an unhandled exception in the handleNotification() method of weblogic.management.timer.Timer, delivery of timer notifications did not take place.
CR235443 | The comm Mbean Proxy stub that is initialized with the Admin MBean Server stub is now refreshed when the Administration server is rebooted.
CR259326 | Passwords in the Properties attribute of the JDBCDataSourceFactory were not encrypted. Now, a Password attribute has been added to JDBCDataSourceFactoryMBean. The value specified in this attribute is encrypted and access to the password is restricted to only Administrators. In addition, the JDBCDataSourceFactoryMBean.Properties attribute no longer contains the password.
CR262604 | weblogic.Admin PING can no longer be used by anonymous users. This is acceptable behavior. However, an incorrect error message was displayed. The error message has now been modified to state that anonymous JNDI lookup is not allowed.

Plug-ins

Change Request Number | Description
--- | ---
CR201397 | With Idempotent=OFF, the IIS proxy plug-in does not retry if it gets a READ_TIMEOUT exception after WLIOTimeoutSecs has elapsed.
CR205132 | Now, Apache 2.0.49 (with mod_wl_20.so) child processes are always terminated on HP-UX.
CR206043 | When performing HTTP GET requests that were larger than 4096 bytes, the following error was seen in the wlproxy log files: request too long: XXXX, max is 4096 This problem is resolved and the error is no longer thrown.
CR206340 | The failover logic used during WebLogic Server shutdown has been fixed. WebLogic Server no longer returns HTTP 404 after SHUTDOWN sequence is initiated.
CR210417 | In a WebLogic Server clustered environment with a plug-in setup, HTTP requests were always routed to SECONDARY during failover. This caused SECONDARY to host all the sessions and utilize more than 50% of the server capacity. Now the plugin does not failover to SECONDARY by default. Instead, it routes the request randomly to the next available server.
CR210497 | The iisproxy128.dll bits were not available in the installer because the path for the binary in the build-native.xml file for the installer was wrong. The path has been rectified and the iisproxy128.dll bits are now available in the installer.
CR210899 | When the DefaultFileName property is set along with the PathTrim and PathPrepend properties, the final URI is no longer malformed.
CR213809 | The older Apache plug-in used an undefined symbol AP_NEED_SET_MUTEX_PERMS on an HP-UX platform. This problem has been resolved. Contact BEA Customer Support for the latest patch.
CR216445 | The size limitation for the response header has been removed. The NSAPI plug-in now allows response headers that are greater than 16k.
CR216621 | Changes made by mod_rewrite to the URI are reflected only to request_rec->uri. Hence, the Apache plug-in now uses request_rec->uri by default. Also, a new property, WLForwardUriUnparsed, has been added. When it is set to ON, the Apache plug-in uses request_rec->unparsed_uri instead of request_rec->uri. Note: The Apache plug-in with WLForwardUriUnparsed set to ON does not work correctly with mod_rewrite.
CR216841 | Absolute URL was not converted to relative URL before processing it for pathPrepend and pathTrim when using an unparsed URI. Now, if the Apache plug-in detects an absolute URL, it first converts it to a relative URI before applying the pathTrim and/or the pathPrepend properties.
CR218494 | WebLogic Server no longer throws an error during graceful shutdown using a memory-based locking mechanism on Linux and HP_UX.
CR220685 | WebLogic Server no longer retries using a new connection when the following are all true: Idempotent is set to OFF. A recycled connection is being used. The backend server is not responsive.
CR222702 | Apache Web server no longer generates huge log files under load if APLOG_NOTICE log level is used within the plug-in.
CR222855 | Now, the latest proxy plug-in for SunOne 6.1 serves the ErrorPage before WLIOTimeoutSecs.
CR223636 | In a multiple cluster environment, it was difficult to track all the log messages for a particular request in the plug-in log file. Now, a unique request ID has been associated with each log message.
CR224513 | NSAPI plug-in now blocks requests that match the directory names specified as values for the WLExcludePathOrMimeType property.
CR229338 | Now, the plug-in infrastructure logs errors when it fails to open the default log file and when it fails to resolve the hostname.
CR229990 | To avoid a delay of 200 milliseconds when receiving the response from the ISAPI plug-in, the Nagle algorithm has been turned off.
CR231085, CR205852 | This problem has been resolved by removing the transfer-encoding header from the response and the web container, where the HTTPClusterServlet is deployed, now decides if the transfer-encoding header should be sent to the client or not.
CR232588 | The CookieName parameter in the WebLogic Apache module overrides the CookieName parameter in Apache mod_usertrack module. Replace the CookieName parameter with WLCookieName for a WebLogic Apache module.
CR233924 | Now, HTTPClusterServlet first tries the preferred PRIMARY and then tries the SECONDARY server. If both these servers are unavailable, the request is directed to the next available server.
CR235434 | When the NSAPI plug-in with Sun One 6.1 is used, the HTTP response header no longer records two instances of the "Date" field.
CR237058 | The W3SVC IIS application pool that ran iisproxy.dll sometimes crashed. This problem has been resolved.
CR237675 | When a resource hosted on IIS was directly requested, the response was sent in one packet. However, when a resource hosted on WebLogic server was requested via the IIS plug-in, the response generated by the server was sent in two packets, although the server itself sends it as one packet to IIS. IIS Proxy Plug-in now sends the response as one TCP packet including headers and body (as sent by the WebLogic Server to IIS).
CR238106 | In a clustered environment, WebLogic Server no longer throws a java.net.SocketTimeoutException when a client with WebDAV implementation accesses the Managed Server through the HTTPClusterServlet.
CR240593 | Graceful shutdown of a cluster node no longer causes in-flight sessions to fail.
CR243059 | When the backend WebLogic cluster was on high load, the NSAPI plug-in caused the Web server process to crash. This problem has been resolved.
CR245461 | When the Welcome page of a web application was accessed from an Apache Plug-in that had the PathPrepend and PathTrim properties set, an endless loop of HTTP requests were sent from the browser via the plug-in to WebLogic Server. This problem has been resolved.
CR251562 | Apache plug-in no longer fails when client sends large POST data as HTTP chunked transfer.
CR253814 | Apache plug-in no longer fails when HTTP transfer encoding is chunked.
CR255498 | The WebLogic plug-in for Apache (for versions prior to Apache 2.0.48) has now been redesigned to create mutexes only if MPM is multi-threaded.
CR259649 | WLExcludePathOrMimeType property did not work correctly if its value was set to a directory. This problem has been resolved.

RMI

Change Request Number | Description
--- | ---
CR215390 | RMI ClassCastException no longer occurs when the server sends a request to the client.
CR249240 | Java level deadlock no longer occurs in IIOP ConnectionManager when two code paths try to acquire the locks in different order.

Security

Change Request Number | Description
--- | ---
> CR136729 | Prior to this release, events with severity level greater than or equal to the configured audit severity level were logged. Now, the default audit provider configuration has a CUSTOM severity option. If the level is set to CUSTOM and one or more severity levels are specified, only events of the specified severity levels are audited. However, if this option is not set, all events with severity level greater than or equal to the configured audit severity level are logged. The system properties that indicate the severity levels are weblogic.security.auditInformation, weblogic.security.auditWarning, weblogic.security.auditError, weblogic.security.auditSuccess, and weblogic.security.auditFailure. For example, to log just INFORMATION and FAILURE events, configure your provider for CUSTOM and set these system properties for WebLogic Server:
>     -Dweblogic.security.auditInformation=true
>     -Dweblogic.security.auditFailure=true
CR182006 | Certificate verification was failing because the SubjectAlternativeName extension to the X.509 certificate was marked as critical. WebLogic Server now allows X.509 certificates with this extension marked as critical to be verified during the SSL handshake.
CR210310, CR231457 | CA certificates that had the path length constraint field omitted in their basic constraints extension were not recognized as CA certificates. As a result, certificate chains containing such certificates failed certificate validation during SSL connection. Now, such certificates are interpreted correctly as CA certificates with no path length constraint.
CR212348 | The listGroupMembers() method's SSPI call was aborting with an exception if one of the group member's Distinguished Names was invalid. Now, the listgroupmembers() method shows the valid groups and ignores the members whose Distinguished Names cannot be validated.
CR215515 | Some versions of Internet Explorer hang when WebLogic Server sends 0 length packets. Now, you can disable sending 0 length packets by adding the public property, -Dweblogic.security.SSL.DisableSSLEmptyRecords=true. Enabling this property can prevent Internet Explorer from hanging due to this cause. The default value of this property is false.
CR215960 | JSAFE native library support has been added. Since WebLogic Server 7.0 SP7 ships only the jsafe.jar (version 3.4.3), please contact the support service of the vendors for other native libraries.
CR218240, CR231517, CR230119, CR230439, CR233424 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/122
CR234477 | An InvalidParameterException was thrown while deploying a resource adaptor when the associated deployment descriptor contained permission statements that used wildcard characters or escaped quotes. This problem has been resolved.
CR242606 | Managed Servers no longer fail at startup when the MasterFirst flag is set to True (as part of the domain-side security configuration), and the default embedded LDAP access control lists are in use.
CR243242 | Now, user locking, unlocking and bad password counts behave correctly if the authentication provider is user name case insensitive and caseSensitiveUserNames is set to false (the default value) or if the authentication provider is user name case sensitive and caseSensitiveUserNames is set to true.
CR250189, CR240904 | The memberURL attribute of the dynamic group now correctly retrieves the users belonging to the group.
CR250264 | Due to the default access control lists shipped with WebLogic Server, users could not change associated passwords. This problem has been resolved.
CR252670 | Outbound SSL connection was very slow because weblogic.jar was verified for every call made to javax.crypto.Cipher. This problem has been resolved.
CR261064 | Now, WebLogic Keystore providers can be specified as per the JCA specification and can be configured by an administrator.

Servlets

Change Request Number | Description
--- | ---
CR106364 | When a URL that includes a relative path (for example, /../../test.jsp) is passed to the RequestDispatcher.forward () method, a 404 error is no longer generated.
CR173426 | The servlet-name element definition has now been added to the weblogic700-web-jar.dtd file.
CR185454, CR110293 | The session count was an approximate number but was not initialized back to 0 when the server was restarted. Also the increment/decrement was not synchronized. As a result, a race condition could have contributed to a wrong count. In addition, for replicated sessions the count was not incremented/decremented for becomePrimary, becomeSecondary, and becomeUnregistered callbacks. WebLogic Server now obtains the count from the map directly for memory and replicated sessions. For file-based sessions, the count is obtained from the file system and for JDBC, it is obtained via a database query. As a result of this fix, counts will no longer be broken. Note, however, that the runtime MBean returns now two more counts: 1. Total sessions opened by the server so far. 2. The maximum open sessions in memory. These two counts remain unaffected by this change. They will still use the old method of increment and decrement; they are approximate and represent a number since the time the server was restarted. These two counts will be reset to 0 after the server restarts.
CR204553, CR136735, CR256088 | A SessionData memory leak occurred in the Servlet Container when using Custom Logger and calling getRemoteUser. The reference count of a SessionData may be increased while logging the request if a custom logger calls the HttpAccountingInfo.getRemoteUser(), getRemoteUse(), getRequestedSessionId(), getUserPrincipal() or isRequestedSessionIdValid(), because these methods try to acquire the SessionInternal object. But the reference count is not decremented. The problem has been resolved. With the change, the values returned from getRemoteUse(), getRequestedSessionId(), getUserPrincipal() and isRequestedSessionIdValid() of ServletRequestImpl are now cached into the HttpAccountingInfoImpl object before logging the request, and uses the cached value if a custom logger calls the methods of HttpAccountingInfo. This avoids incrementing the reference count.
CR208696 | When the external_stage mode was used for deploying a war archive, existing war archives in the .wlnotdelete directory were deleted on shutdown and again copied on startup. This problem resulted in performance degradation. Now, there is a significant decrease in server boot up time because existing war archives are no longer deleted on shutdown.
CR214104, CR222683, CR228624 | SessionID generated with reserved keyword in the first 4 letters was impacting performance. The sessionID generation logic was modified to fix this issue.
CR214457, CR202495, CR236810, CR239392, CR206002 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/130
CR223609 | Web application ClassLoader ignored the manifest classpath entry in the application web archive. So, a class not found exception occurred while trying to run the web application. This problem has been resolved.
CR229577 | In FormBasedAuthentication, the requested URL was not getting properly stored, both before and after the user was being authenticated using the form-based login page. To store the complete URL (including the http or https protocol scheme) of the original request, the following parameter was added to the weblogic.xml file: <container-descriptor> <retain-original-url> true </retain-original-url> </container-descriptor>
CR236526 | During failover between servers, requests containing stale sessions are no longer served in case of JDBC persistence.
CR239831 | When a large file was forwarded from a JSP with autoFlush=false, an infinite loop occurred in ChunkOutput.writeStream(). This problem has been resolved.

Simple Network Management Protocol (SNMP)

Change Request Number | Description
--- | ---
CR222114 | The enterprise OID for the SNMP coldStart trap was incorrect. It has been changed to ".1.3.6.1.4.1.140.625".

Web Services

Change Request Number | Description
--- | ---
CR214959 | When an array of elements was populated within a SOAP message, a subsequent element was always passed as a null value to the webservice method variable irrespective of the actual value that was passed in the method.
CR257606 | When web service calls were made using SSL, java.net.SocketException occurred because the socket that was used to retrieve the WSDL was not closed. This error occurred because there were too many open files. This problem has been resolved.
CR258325 | Web service client making an outbound SSL call no longer generates a memory leak.
CR259227 | On Red Hat Enterprise Linux 4.0 AS, generateClientJar (clientgen API) failed with a ClientGenException. This problem has been resolved.
CR262186 | ServiceException is now thrown when a Service object with no access to WSDL metadata is unable to determine port information.

XML

Change Request Number | Description
--- | ---
CR215016 | When doing lookup of DTDs over HTTP from a central Web server, if the URL failed (that is, if the Web server was down momentarily), the XML registry did not renew the DTD in the cache and failed each time the DTD was used. Now, the XML registry renews the DTD in the cache, which resolves the problem.