Skip navigation.
Downloads | Product Documentation | Support

Release Notes

# Resolved Problems for Service Pack 6

Service Packs are cumulative; Service Pack 6 contains all fixes made in earlier Service Packs released for BEA WebLogic® Server 8.1. The following sections describe problems that were resolved in BEA WebLogic Server® 8.1 Service Pack 6:

- Administration Console
- Builder
- Classloaders
- Cluster
- Connector
- CORBA
- Core WebLogic Server
- Deployment
- EJB
- JDBC
- jDriver
- JMS
- JTA
- JNDI
- JVM
- Node Manager
- Operations, Administration, and Management
- Plug-Ins
- RMI
- Security
- Servlets and JSPs
- SNMP
- Tools
- Web Services
- WebLogic Tuxedo Connector
- XML

## Administration Console

####

Change Request Number | Description
--- | ---
CR102753 | The Network Channel Configuration page on the WebLogic Server Administration Console did not have a link to go back to the Channel lists page. This problem has been resolved. You can now access the Network Channel Configuration page by clicking on the link in the bread-crumb trail.
CR106558 | The WebLogic Server Administration Console displayed `Type` values only after the `DefaultIdentityAsserter` MBean was created. The problem has been resolved. The WebLogic Server Administration Console now displays the `Type` values at the time the `DefaultIdentityAsserter` MBean is being created. In addition, the `Available` and `Chosen` columns have been widened to improve usability.
CR109929 | The bread-crumb trail providing information about the resource to which a scoped role is associated is not displayed in the Title tag. Also, to view defined roles, users and groups after creating or editing them, you have to right-click the node in the nav-applet. This information should be made available through the bread-crumb trail. This problem has been resolved. The WebLogic Server Administration Console now displays the association between a scoped role and a resource in the bread-crumb trail. In addition, clicking on the appropriate link in the bread-crumb trail now provides information about roles, users and groups.
CR111253 | WebLogic Server did not initialize the Console Extension if the user who logs-in for the first time belonged to the "Operator" group. Subsequent logins as "Administrator" also did not initialize the extension. The extension is initialized only when WebLogic Server was rebooted and the "Administrator" logs on at first instance itself. This problem has been resolved. The console extension is now initialized for all groups with appropriate permissions.
CR122389 | WebLogic Server ignored case sensitivity with respect 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.
CR130398 | Redeploying one application caused another application to be deleted. A slow refresh rate gave the user the impression that the click to delete the application was not recorded. When the user clicked Delete again, the next application was deleted. As a result, making the user believe that deploying one application caused another to be deleted. This problem has been resolved.
CR133506 | Policies inherited from the parent JNDI node that were defined for the lookup, modify and list JNDI methods were displayed incorrectly by the WebLogic Server Administration Console for JNDI sub-nodes. This problem has been resolved. Policies inherited from the parent JNDI node that are defined for the lookup, modify and list JNDI methods are now displayed as inherited policies for the lookup, modify and list methods respectively, in the JNDI sub-nodes.
CR209803 | Console Extension pages did not require user login and password even when the user session had expired. This problem has been resolved.
CR212333 | In the Administration Console, users belonging to the Monitors, Operators, or Deployers group could view (but not modify) security information using the Realms link in the right navigation pane, but the security node was not available in the left navigation pane. This problem has been resolved.
CR225707 | Users belonging to the "Monitor" group could not view the Pools List of JDBCMultiPool. This problem has been resolved.
CR233559, CR256737 | When the default load order was modified, the deployment path changed from absolute to relative (that is, the leading "/"before the deployment path was removed) and this caused the deployment to fail on restart. This problem occurred only when the path attribute value had more than 50 characters. This problem has been resolved.
CR236810 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/196
CR238260 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/190
CR238260 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/191
CR239145 | When the Auto Deploy tab was clicked to assign the destination queue to the distributed destination, the JMS server list displayed in the target selection window was not properly formatted. This problem has been resolved.
CR239403, CR265216 | Due to insufficient permissions, users assigned to the Monitor role could not view the Deploy and Test page from the Administration Console. This problem has been resolved.
CR241785 | Administration Console did not prevent the setting of null values for MBean Attributes with `@legalNull` annotation. This problem has now been resolved.
CR241816 | From the Administration Console, switching between the tabs in the application page during application deployment was slow. In addition, after successful deployment, rendering the Deploy tab was slow. This problem has been resolved.
CR241825 | In the Administration Console, while configuring a custom security provider, the existing list of attribute values was not properly displayed in the drop-down list in this page. This problem has been resolved.
CR243415 | The Administration Console Login page was accessible through the administration port even after the domain-wide administration port was configured in the Administration Console. This problem has now been resolved.
CR243427 | Calls to `assertIdentity()` could only be made when the user belonged to the "Admin" role. Now, the security policy to call the `assertIdentity` method can be defined through the Administration Console.
CR246438 | When WebLogic Server was run as a Windows Service, applications located in remote mapped drives could not been deployed from the Console. The set new Location option has been added in the Locate Application or Component to configure page to enable you to deploy applications from a mapped network drive on Windows, using the UNC path.
CR246599 | Session monitoring of archived Web applications was disabled on Administration Console even when session monitoring was enabled in `weblogic.xml`. Now, Administration Console displays the statistics of the currently active sessions of Web applications for which session monitoring has been enabled in `weblogic.xml`.
CR247206 | Administration Console displayed the users of only the first authentication provider in a list of multiple configured authentication providers. Now, Administration Console displays the users of all configured authentication providers.
CR248303 | A cloned connection pool was deployed even when the connection parameter was wrong. Now, the cloned connection pool is not deployed and appropriate error messages are shown in the Target and Deploy screens.
CR251390 | On Compatibility Security domain, `javax.management.ServiceNotFoundException` occurred when resources like Web Application, EJB, JDBCConnectionPool, and so on were deleted from the Administration Console. This problem has been resolved.
CR252286 | When an EJB was deployed to a domain that had a Managed Server running on a remote machine, the EJB test on the Administration Console incorrectly displayed a failure message when the test was successful. This problem has been resolved.
CR255268 | The `AuthCookieEnabled` attribute associated with a Web Server MBean can now be set via the Administration Console.
CR256101 | When users clicked the Embedded LDAP tab, a dialog that prompts them to save changes was displayed even when no changes were made. This problem has been resolved.
CR264010 | The Administration Console used to hang when a large application that contained many modules was deployed. This problem has been resolved.
CR264965 | Due to the value of `MaxPageSize` set in the LDAP Server configuration, only an incomplete list of users of all configured authentication providers was displayed on Administration Console. This problem has been resolved.
CR267540 | An application was not properly deployed when the Target Each Module button was used to deploy the EAR file that contained one or more Web modules. This problem has been resolved.
CR269934 | `NullPointerException` occurred when an EJB with an invalid deployment descriptor was deleted from Administration Console. This problem has been resolved.
CR270210 | Servlet session replication over SSL could not be disabled from Administration Console. You can now disable secured replication from the Cluster —> Configuration —> General tab page.

## Builder

####

Change Request Number | Description
--- | ---
CR253219 | Components that used weblogic.management.descriptor.weblogic.WeblogicEnterpriseBeanMBean to generate the XML for the bean were not able to detect if the value of the remote-client-timeout attribute was set in weblogic-ejb-jar.xml. This problem has been resolved.

## Classloaders

####

Change Request Number | Description
--- | ---
CR244763 | `ApplicationException` occurred when a signed JAR file was deployed from the Administration Console. This problem has been resolved.

## Cluster

####

Change Request Number | Description
--- | ---
CR250953 | Even when other Managed Servers were shutdown, a Managed Server could not detect the timeout of those Managed Servers. This problem has been resolved.
CR258097 | Error occurred while deploying a large clustered application running on a large cluster. This problem has been resolved.
CR264052 | Managed Server could not dynamically pickup cluster debug flags in `config.xml`. This problem has been resolved.

## Connector

####

Change Request Number | Description
--- | ---
CR244472 | `XAER_PROTO` errors sometimes occurred when WLS Connector adapters were configured to use `XAResources`, and shrinking was allowed. This problem has been resolved.
CR262160 | After SwiftMQ was restarted, the MessagingBridge could not reconnect and failed with `MessagingBridgeException`. This problem has been resolved.

## CORBA

####

Change Request Number | Description
--- | ---
CR245702 | `EOFException` sometimes occurred when external CORBA service was called as IDL client from WebLogic Server.
CR264454 | `ClassCastException` occurred in `UtilDelegateImpl.isLocal()`when the delegate's stub was not a WebLogic Server stub. This problem has been resolved.

## Core WebLogic Server

####

Change Request Number | Description
--- | ---
CR196369 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/197
CR217793 | `ClassCastException` occurred on the secondary server when a dynamic proxy that also implemented the remote interface was put in a replicated HTTP Session. This problem has been resolved.
CR223348 | There was a problem with `TrustedClientPrincipals` and `DefaultIdentityAsserter` for CSIV2 tokens. This problem occurred because the IIOP CSI layer called the security framework for identity assertion as kernel ID and WebLogic Server kernel was not in the trusted client principals set. Now, Identity Asserter works properly when the ID of the client identity token is in the trusted client principals set.
CR229764 | When the client application was connected to WebLogic Server using a thin client, using IIOP protocol, and a `UserTrasaction.begin` call was initiated, the transaction call failed with `OBJECT_NOT_EXIST` exception when the remote server was shutdown and restarted. This problem has been resolved.
CR234740 | `OutOfMemoryError` occurred when an EJB was called from a Java client using `wlclient.jar`. This problem has been resolved.
CR235893 | `SQLexception` occurred on generated CMP code resulting in Blob/ClobUnsupported feature and further `DuplicateKeyExceptions`. This problem has been resolved.
CR241234 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/174
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.
CR244772 | `NoSuchObjectException` occurred when an EJB JAR module was un-deployed if Session Beans and Message-Driven Beans were part of the same EJB JAR file. This exception occurred because Message-Driven Beans were un-deployed after the Session Beans. Now, Message-Driven Beans are first un-deployed when an EJB JAR file that has multiple beans (session, entity and MDBs) is deployed.
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.
CR248420 | When the IIOP protocol was used, Socket timeout did not clear the `SocketInfo` objects. This problem occurred because the socket IO pending state was never cleared. The SocketInfo objects are now removed.
CR249320 | Remote call to a method in an updated EJB was activating the wrong method. This problem has been resolved.
CR252696 | When the application tried to get the result set, and when there was a foreign JMS resource and other resource in the transaction, a call was made to check if the resource was registered. This method call threw a `ClassCastException` instead of checking if the resource was of the same class as that of the foreign JMS resource. This problem has been resolved.
CR254617 | `beasvc` sometimes stopped rotating the logs, especially when multiple systems were used. In the log file, if`ROTATION_TYPE` was set to `SIZE` after this problem occurred, `beasvc` never started rotating the logs again. However, if `ROTATION_TYPE` was set to `TIME`, `beasvc` sometimes restarted rotating the logs. This problem has been resolved.
CR259784 | On HP-UX, when I/O operation on a file descriptor was cancelled, the socket was not properly cleaned and this caused a File Descriptor leak eventually leading to an `OutofMmemory` exception. This problem has been resolved.
CR265510 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/186

## Deployment

####

Change Request Number | Description
--- | ---
CR237801 | Concurrent redeployment of applications caused memory leak. This problem has been resolved.
CR246997 | `ConcurrentModificationException` occurred when a deployed cancel request was sent while the deployment request is still being processed. The problem is now resolved.
CR252916 | `ConcurrentModificationException` occurred when portal applications were deployed. This problem has been resolved.
CR254807 | `DeploymentException` occurred when `weblogic.Deployer` was used to redeploy an empty folder. This problem has been resolved.
CR264428 | `AccessException` occurred during deployment of a stateless session EJB when the application code corrupted the security stack. This problem has been resolved.
CR265566 | Redeploy sometimes failed because non-empty directories were not deleted during redeploy on Managed Server. This problem has been resolved.
CR270507 | `FileNotFoundException` occurred when an application was deployed using the `wldeploy` ant task, and the file associated with the `File` attribute passed by the task was on a remote machine running on a different operating system. This problem has been resolved.

## EJB

####

Change Request Number | Description
--- | ---
CR106234 | Using a composite primary key with DBMS column type defined as 'Oracle BLOB/CLOB' led to syntax errors. This problem has been resolved.
CR107439 | A `NullPointerException` was encountered when the weblogic.appc utility was run against an EJB that contained a deployment descriptor that had an ejb-ql query with an empty 'where' clause. For example: `<ejb-ql><![CDATA[SELECT DISTINCT OBJECT(ma) FROM MasterAgreements AS ma WHERE]]></ejb-ql>`. This problem has been resolved.
CR133972 | The EJB resource reference and resource type for a Connection Factory recognized only the non-XA definitions for automatic transaction enlistment. Now, the `javax.jms.XAQueueConnectionFactory` and `javax.jms.XATopicConnectionFactory` resource reference and resource type are automatically enlisted in a transaction.
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.
CR188106 | The changes made to a bean in the ejbStore of another bean were not persisted at the end of a transaction. This problem has been resolved.
CR194941 | When there was a parent-child relation between the beans in a transaction, a finder configured to flush the cache did not flush the parent beans. This problem has been resolved.
CR214139 | WebLogic Server threw a `DuplicateKeyException` instead of the actual `SQLException` when BLOB/CLOB was used with CMP entity beans. This problem has been resolved.
CR229290 | During EJB compilation, Weblogic Server did not honor the options specified in the `extra-rmic-options` element of the `config.xm`l file. This problem has been resolved.
CR240869 | Auto key generation failed when a CMP EJB used a primary key class that contained only one field of type `java.lang.Integer` or `java.lang.Long`. This problem has now been resolved.
CR242078 | `java.rmi.UnexpectedException` was thrown instead of the actual exception in the case of exceptions like `java.io.FileNotFoundException`, `java.io.EOFException`, etc. (subclasses of java.io.IOException) even when the bean's business methods declared that an `IOException` must be thrown. This problem has now been resolved.
CR247208 | When the remote or home interface was invalid, `NullPointerException` was displayed instead of the appropriate error message during EJB compilation. This problem has been resolved.
CR248877 | `NullPointerException` occurred when WebLogic Server did an EJB lookup on WebSphere via IIOP. This problem has been resolved.
CR254198 | `IllegalStateException` was thrown when a stateful Session Bean was removed in a transaction. This problem has been resolved.
CR257937 | When a local interface was used to call EJBs, if there is an exception, the transaction was rolled back and a `TransactionRolledBackLocalException` was thrown. However, the root cause of the exception was lost. This problem has been resolved.
CR260850 | In a cluster environment, CMP/One-To-One CMR field returned a stale reference of the child bean when cache-between-transactions was set to true. This problem has been resolved.
CR266648 | WebLogic Server did not check access restrictions for EJB methods that take array parameters as arguments. This problem has been resolved.
CR267655 | `classNotFoundException` occurred when Message-Driven Beans with `start-mdbs-with-application` set to `false` in the application descriptors were deployed. This problem has been resolved.
CR268449 | WebLogic Server threw a `SQLException` (ORA-01000: maximum open cursors exceeded) for Beans with Many-to-One relation ship and Optimistic concurrency set to `true`. The problem has been resolved.
CR269628 | EJB deployment failed with `TimedOutException`. WebLogic Server no longer fires a query to check `FOR UPDATE` support for Oracle, which caused a full table scan and sub-sequent transaction timeout exception. In the case of DB2, WebLogic Server no longer checks for `FOR UPDATE` support when the bean is not using optimistic concurrency, and when `<use-select-for-update>` is set to `false`.
CR272888 | When prepared statement caching was used in WebLogic Server, Oracle specific batch calls were not effective when they were called on the Connection object. This problem has been resolved.

## JDBC

####

Change Request Number | Description
--- | ---
CR228447 | Data source lookup that was based on multiple JNDI names failed. Now, only the first JNDI name is returned.
CR231621 | While using DB2 XA configurations, there was a negative impact on performance when the application was running for an extended period of time. This problem has been resolved.
CR231679 | In WebLogic Server, connections could only be obtained using `java.sql.Driver` and `javax.sql.XADataSources`. So, pools could not handle a driver that was presented as a non-XA`javax.sql.DataSource`. Now, connections can also be obtained using `java.sql.DataSource`.
CR238794 | With Oracle RAC, load balancing did not always work in a multipool. When the current connection request hanged, any subsequent requests did not go to the next connection in the pool instead they waited for the current request to be satisfied. This problem has been resolved.
CR239116 | Invalid configurations consisting of multiple `JDBCTxDataSource` entities that referenced a single `XA JDBCConnectionPool` entity were allowed. Now, during data source deployment, if more than one `JDBCTxDataSource` referenced the same `XA JDBCConnectionPool`, an error message is written to the server log.
CR239170 | Differences in implementation of `JDBCConnectionPoolRuntimeMBean` between the WebLogic Server 7.0 to 8.1 releases led to migration problems. This problem has been resolved.
CR239407 | jDriver for Oracle had a fixed allowance of cursors that could be simultaneously open across all connections. This allowance was not sufficient when there were a large number of cached statements. This problem has been resolved by increasing the array size for output parameters.
CR239420 | Even when connection leak profiling was enabled, leak information was not printed in the server Logs when `JDBCDataSource` was used. This problem occurred because the link to idle user connection objects was retained and so these objects were unavailable for garbage collection. Leak information was not available because leak tracing is triggered only after garbage collection. This problem has been resolved.
CR239529 | `NullPointerException` occurred while inserting a record with duplicate primary key. This problem has been resolved.
CR242009 | After the patch created to fix CR239170 was applied, the Connection Pool Manager did not test the connection after the interval specified for the `TestFrequencySeconds` attribute. 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.
CR243053, CR239420 | The implementation of `idle-connection-timeout` unintentionally prevented the garbage collector from reclaiming leaked JTA connections. This problem has been resolved.
CR243306 | WebLogic wrapper around a Prepared Statement used a new wrapped Prepared Statement every time a `SQLException` occurred when calling `executeUpdate()`. So, memory resources were also impacted when the same statement was used multiple times. Now, to enable reuse, reference to the prepared statement is not lost until you explicitly close the statement.
CR243730 | MultiPool failed to calculate the correct health check frequency when the value of `HealthCheckFrequencySeconds` attribute, associated with the `JDBCMultiPool` element, was larger that the max Integer value. This problem has been resolved.
CR243741 | When an XA transaction was used with two resources, Sybase XA JDBC resource and JMS resource, only the first transaction worked fine. Subsequent transactions failed. This problem has been resolved installing a new driver from Sybase.
CR243824 | When the BEA MSSQL driver was used, the thread continued to be associated with the transaction even after the asynchronous transaction was rolled back. This problem has been resolved.
CR247033 | When the EJB Wizard was used to create an Entity Bean from an existing table, the wizard failed with an `NullPointerException` on receiving metadata delivered by BEA Informix Type 4 JDBC driver. This problem has been resolved.
CR247217 | `NullPointerException` occurred while creating a application scoped `LocalDataSource`. This problem has been resolved.
CR249009 | 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.
CR251945 | When a connection pool failed to satisfy a user request, the multipool tried to disable that pool. However, the disable action could only be done by a user belonging to the "Admin" group. `ResourcePermissionsException` occurred when the current user did not have the required permissions. This problem has been resolved.
CR254548 | While upgrading from WLS 8.1 SP3 to WLS 8.1 SP4, `NullPointerException` occurred at `weblogic.jdbc.wrapper.JTSConnection.initCopy`. This problem has been resolved.
CR256316 | `InvalidTransactionException` occurred when a suspended transaction that had timed out was resumed. This problem has been resolved.
CR257026 | While testing the health of the multipool based on the value of `HealthCheckFrequencySeconds` of JDBCMultiPool, BEA-000622 and BEA-001261 messages were sometimes unexpectedly displayed in the server logs. This problem has been resolved.
CR259992, CR267064 | Under heavy load, the number of connections could be more than the maximum value. This problem has been resolved.
CR262763 | `NullPointerException` occurred when select list included a Null DATE value and `RowPrefetchEnabled` was set to `true` for the data source. This problem has been resolved.
CR264361 | Non-transactional JDBC may sometimes be blocked on Oracle RAC disconnect. This problem has been resolved.
CR266573, CR212898, CR219822 | Invalid XML was generated when JDBC Connection leak profiling was enabled. This problem has been resolved.
CR272721 | Database connections leaked when the JDBC data source was shutdown and restarted from Administration Console during database procession by application. This problem has been resolved.

## jDriver

####

Change Request Number | Description
--- | ---
CR238484 | Some `DataBaseMetaData` methods took longer time to execute than Oracle driver. The order of search arguments in the SQL used by jDriver to execute these methods has been modified to resolve this lag.

## JMS

####

Change Request Number | Description
--- | ---
CR224458 | `InvalidClientIDException` was not included in `wljmsclient.jar` causing the exception class to be loaded via Sun RMI classloader from WebLogic Server. Now, `InvalidClientIDException.class` has been added to `wljmsclient.jar`.
CR228586, CR253160, CR258904, CR276086 | Server sometimes hanged when a large number of JMS thin clients tried to create a connection over IIOP and the server was unable to communicate with one of the clients. This problem has been resolved.
CR229495 | Client no longer hangs while waiting for acknowledge completion when the backend JMS server goes down.
CR235134 | When JMSServers were targeted to migratable targets, `JMSException` occurred when a distributed queue was created using `JMSHelper createDistributedQueueAsync()`. This problem has been resolved.
CR235392, CR257796 | When paging was configured and a JDBC Store was used for persistent messaging, messages with null message body were sometimes returned because a race condition existed between writing messages to the JDBC store and making the message body null for paging. This problem occurred when JDBC store was used as persistence store and simultaneously File Store was used as paging store. This problem has been resolved.
CR237143 | JMS paging did not work with `no_ack` consumers. Now, message consumers using the `AUTO_ACKNOWLEDGE` and `NO_ACKNOWLEDGE` acknowledge mode will see the same paging behavior.
CR240125 | `java.rmi.ConnectException` occurred when a JMS server was deployed to a Managed Server after the Administration Server was restarted. This problem has been resolved.
CR240553 | `IllegalStateException` occurred when the Bridge adapter tried to stop a connection that was already closed. However, this exception did not have any impact on the bridge behavior. The problem has been resolved.
CR243416, CR259753 | When an `IOException`, `SecurityException`, etc. exception occurred when sending a JMS message, an `IllegalStateException` was displayed instead of the actual exception. Now, the correct underlying exception is displayed instead of the `IllegalStateException`.
CR244787 | A client application that used either transacted sessions of user transactions could hang on `TransactionRolledBackException` when the JMSServer was not located on the same server as the JMS connection. This problem has been resolved.
CR244874 | Zombie consumers were sometimes observed when remote Java client spawned multiple threads and each thread created a JMS connection. This problem has been resolved.
CR247580 | Message-Driven Beans stopped receiving messages after JMS quotas was exceeded. This problem has been resolved.
CR252085 | JMS server migration failed when the migration attempt was made after the Administration Server bounced, and the JMS Server hosted distributed destination members. This problem has been resolved.
CR256298 | JMS threw `java.util.ConcurrentModificationException` during backend security check. This problem has been resolved.
CR267776 | Memory leak in JMS subsytem of WebLogic Server caused OutofMemory error. Producer security participant hashmap logic has been optimized to handle this situation.
CR268986 | Persistent messages published to a distributed topic that were pending on the distributed topic's internal system subscriber were not forwarded after server restart. Now, the system subscribers are durable even after server restart and so, the durable subscriber need not be explicitly configured.
CR274483 | When the allowed maximum value, `2147483647`, was specified for the `Transaction Timeout` attribute for the JMS Connection Factory, the value was treated in milliseconds rather than seconds. This problem has been resolved.

## JTA

####

Change Request Number | Description
--- | ---
CR182523 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/195
CR213034 | Redelivery of JMS message did not occur after migration on transacted messages. This problem has now been resolved.
CR258893 | When messages were transferred via messaging bridge, a few pending messages remained on a target destination after `javax.transaction.SystemException` occurred in messaging bridge. This problem has been resolved.
CR265136 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/187
CR265260 | Security error occurred when inter-domain transactions were used without enabling inter-domain trust. This problem has been resolved.
CR269661 | `HEURISTIC_HAZARD` exception occurred when a foreign JMS resource responded with `XA_RBROLLBACK`. This problem occurred only when the transaction branch was marked for roll back. Now, when `XA_RBROLLBACK` response is sent, the transaction is rolled back.
CR270180 | `HeartbeatMonitorUnavailableException` occurred when connection to the remote server was lost. Since list exception was ignored instead of removing the reference to the unavailable server, distributed transaction failed with `ConnectException`. This problem has been resolved.

## JNDI

####

Change Request Number | Description
--- | ---
CR241138 | Removal of the notification listener was not thread-safe and it caused `ConcurrentModificationException`. This problem has been resolved by synchronizing the removal of the notification listener.

## JVM

####

Change Request Number | Description
--- | ---
CR133367 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/194
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
--- | ---
CR219954 | When you tried to start two managed servers simultaneously from the Node Manager, WebLogic Server failed to start one of the managed servers due to an `InstanceAlreadyExistsException`. This problem has been resolved.
CR245364 | The default Cipher Suite for NodeManager could not be changed. The Cipher Suite can now be changed using `CipherSuite`, which is a new property in `nodemanager.properties`. However, only one cipher suite can be specified in `nodemanager.properties`.
CR256502 | After restart, Node Manager waited for the interval specified for `ScavangerDelaySeconds` before recovering monitored processes. This problem has been resolved.
CR270560 | When no parameters were passed to remote start a Managed Server, the Managed Server did not pick up these properties from `nodemanager.properties`. `ServerStartArgs` property has to been added to `nodemanager.properties`. So, to pick up properties from this file for starting Managed Servers, specify `'ServerStartArgs= '` in the file.

## Operations, Administration, and Management

####

Change Request Number | Description
--- | ---
CR135890 | While upgrading from 8.1 to 8.1 SP2, `ambiguous reference` errors occurred when the `<JMSTemplate>` tag was nested inside the `<JMSDistributedQueue>` or `<JMSDistributedTopic>` tags and the `<JMSTemplate>` was moved out of the distributed destination and placed under the distributed destination parent domain. This problem has been resolved.
CR186017 | JDK did not print the seconds value of a date when the `Full` format was used on certain locales such as `fr_FR`. The `Long` format for date, however, included the seconds value. Although the default formats of Date and Time have not been changed, these formats can now be configured.
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 now been resolved.
CR224350 | When there was an unhandled exception in the`handleNotification()` method of `weblogic.management.timer.Timer`, delivery of timer notifications did not take place.
CR225812 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/184
CR236930 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/188
CR238988 | Since the `CommoMBeanProxy` stub cached the `adminMBeanServer` stub as an instance variable, the `adminMBeanServer` stub was stale after the Administration Server was rebooted. This problem has been resolved.
CR240599 | When the `Properties` attribute of type `Map` was set on `JDBCDataSourceFactoryMBean` using the `weblogic.Admin` tool, the command line values were not parsed correctly when comma (`,`) was used as a delimiter. The expected delimiter for `Map` type attributes has been changed to semicolon (`;`). Now, the `Properties` attributes can be set correctly using the `weblogic.Admin` tool.
CR242664 | Users belonging to the "Operator" group could start and stop servers, but they could not reconnect to the managed server using the `discovermanagedservers` command line option because of insufficient privileges. Now, users belonging to the "Operator" group have permission to run the `discovermanagedservers` command.
CR248574 | Users belonging to the "Operators" and "Deployer" groups had permission to start and stop individual servers, but did not have permissions to start or stop servers in a cluster. This problem has been resolved.
CR254404 | In the JMX Timer implementation, certain threads were unused (not started) if the notifications was added to the timer before the timer was started. These unused thread objects could not be garbage collected and caused a memory leak. This problem has been fixed.
CR255020 | After the JMS Services were migrated to a server other than the hosting server, the services remained on the destination server only until the Administration Server was not restarted. After the Administration Server was restarted, the `PreferredServer` was reset to point to the original server. This problem has been resolved.
CR256343 | When running the EXISTS_POOL command on the Administration Server of a domain with Managed Servers, the command only returned `true` if the pool was deployed on the Administration Server. Since connection pool names must be unique in a domain, this command should have returned `true` if the pool existed in the domain, not only on the server. WebLogic Server now returns `true` if a pool with the specified name has been configured in the domain.
CR258534 | The `weblogic.admin` command behaved incorrectly when it was run with a BATCHUPDATE and the batch file contained commands to add a cluster. This problem has been resolved.
CR263973 | `NullPointerException` occurred on Administration Server when Managed Server was started using the Node Manager. This problem has been resolved.
CR266157 | `weblogic.admin BATCHUPDATE` command threw an error when commands in a batch file contained space or escape characters as part of the MBean name. The problem has been resolved.
CR266288 | Users belonging to the "Monitor" role could not view the deployment descriptor in the EAR due to insufficient permissions. So, users could view EJB Desriptors, WebApp Descriptors, Connector Descriptors, etc. but not Application Descriptors. This problem has been resolved.
CR271905 | Parallel access to an un-synchronized data structure that tracked version numbers for `DeploymentTaskRuntimeMBeans` caused `InstanceNotFoundException` during partial redeployment. This problem has been resolved.
CR273152 | When the Administration Server was restarted, parallel access to un-synchronized data structure caused `NoSuchElementException` from Managed Server. This problem has been resolved.

## Plug-Ins

####

Change Request Number | Description
--- | ---
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.
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.
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).
CR239561 | WebLogic Apache Plug-in did not correctly handle MIME types for cascading style sheets. This problem has been resolved.
CR240593 | Graceful shutdown of a cluster node no longer causes in-flight sessions to fail.
CR243059 | When the back end WebLogic cluster was on high load, the NSAPI plug-in caused the Web server process to crash. This problem has now been resolved.
CR243676 | Using the IIS plug-in and downloading large static files hosted on WebLogic Server was very slow. For files larger than 20 MB, several TCP packets were being sent to the client leading the performance degradation. The response buffer size has now been increased to reduce the number of partially filled TCP packets.
CR243845 | Now, when Sun One Web Server is configured as a reverse proxy along with BEA WebLogic plug-in, chunked transfer encoding no longer fails for large content.
CR244797 | Since the logs folder could be customized in the httpd.conf file, Apache plug-in could not create the necessary lock file while starting Apache server. Now, the lock file (with PID appended to the file name) is created under the /tmp folder for UNIX and under APACHE_HOME for Windows.
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 now been resolved.
CR251562 | Apache plug-in no longer fails when client sends large POST data as HTTP chunked transfer.
CR253814 | Apache plug-in failed when HTTP transfer encoding was chunked. This problem has been resolved.
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.
CR264288 | For a HEAD request (size of body is 0), Content-Length Header was missing in the response sent by Apache. This problem has been resolved.
CR269057 | `HttpClusterServlet` and `HttpProxyServlet` did not forward multiple response headers with the same name. When more than one response header with the same name was sent, only one of those headers was sent to the client. This problem has been resolved.

## RMI

####

Change Request Number | Description
--- | ---
CR193157 | When an EAR file was redeployed, the EJB stub was regenerated using the originally deployed classloader. This caused a `ClassCastException` because the classloader of the EJB stub differed from the current application classloader. This problem has been resolved.

## Security

####

Change Request Number | Description
--- | ---
CR130515 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/181
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`
CR196456 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/193
CR208126 | The size of the change logs that record the updates made to the Administration Server became very large over a period of time. Now, the change logs do not grow in an unbound manner. In addition, you can use the `-Dweblogic.security.ldap.changeLogThreshold=<number of changes>` property to truncate the updates to the change log.
CR217083 | WebLogic Server rejected certificates with a `Certificate Policies` extension. The problem has been resolved.
CR225070 | WebLogic Server plug-in for IPlanet 6.0 SP3 on Solaris did not correctly pass the client certificate. This problem has been resolved.
CR235145, CR262180 | When an interrupt or exception occurred while closing the SSL connection, the underlying socket was not closed. This problem has been resolved.
CR238944 | Calls to `WLSSLAdapter.loadLocalIdentity` failed with `java.security.KeyManagementException`. Older private keys can now be loaded by Web Service clients.
CR239255 | On Linux platforms, a socket that was closed could remain open if it was polled by something else. This could result in many open sockets. This problem has been resolved.
CR239321 | The entitlement property for preloading the cache was not set correctly. This problem has been resolved.
CR239657, CR264049 | Unique members on a managed server were lost when the embedded LDAP of the Administration Server was not in sync with the managed server. Now, entries that have more than 127 values are correctly replicated in the managed server.
CR240904 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/196
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 | User locking, unlocking and bad password counts were incorrect when the authentication provider was user name case insensitive and `caseSensitiveUserNames` was set to `false` (the default value) or when the authentication provider was user name case sensitive and `caseSensitiveUserNames` was set to `true`. This problem has now been resolved.
CR243498 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/175
CR244418 | When data is available, WebLogic Server reads data from the socket. Sometimes, the socket showed that data was available for read, but the read operation did not return any data. The server then went into a recursive loop leading to a StackOverflowError. This problem has been resolved.
CR249521, CR215718 | Multiple step identity assertion interfaces were available in the WebLogic Server security framework in 8.1SP5. However, this feature could break existing custom providers that used auditing, and custom auditors themselves, and clients that received audit events. The AuditAtnEventV2 interface has been removed. This change should have no affect on your code written to the 8.1SP4 `AuditAtnEvent` interface. However, if you modified your code to the AuditAtnEventV2 interface, you need to change it back in order to use it in the 8.1SP5 or 8.1SP6 release.
CR250189 | 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.
CR253594 | The fix for CR210310 was only included in `weblogic.jar` and not IN `webserviceclient+ssl.jar`. Now, this fix is included in all web services `.jar` files.
CR255630, CR264699, CR259757 | WebLogic Server did not always handle proxy properties correctly. This problem has been resolved.
CR257400 | Failed to create a SPNEGO provider because the MBean's `ActiveTypes` attribute was not writable. This problem has been resolved.
CR263358 | Two-way SSL connection to IIS 5.0 failed with `SSLHandshakeException`. This problem has been resolved.
CR266441 | Authentication to an external LDAP did not work when `useRetrievedUserNameAsPrincipal` was set to `true` for the configured ADS security provider. This problem has been resolved.

## Servlets and JSPs

####

Change Request Number | Description
--- | ---
CR132872 | If you are using the `ServletResponseWrapper` class and include an HTML file in the JSP after calling `getWriter()`, `weblogic.servlet.FileServlet` throws an `IllegalStateException` while calling the `getOutputStream()` method. This problem has been resolved. `FileServlet` no longer throws an exception when you use the `ServletResponseWrapper` class with a JSP that includes a call to static files after calling the `getWriter()` method.
CR181868 | Webapp Container ignored Authentication information for unsecured resources and invoked the resource as Anonymous. Now, Webapp Container looks for Authentication Headers even for an unsecured resource, and tries to authenticate the user specified using those headers and later calls the unsecured resource using that user. However, this is only applicable if the user has not already been authenticated using a different user.
CR198547 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/185
CR211974 | Under heavy load, memory leak occurred because WebLogic Server did not consistently invalidate the HttpSessions. This problem has been resolved.
CR218694 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/192
CR219805 | Compilation of JSP no longer fails when Java comments span multiple scriptlets as shown below. `<%/*%>` `[HTML code]` `<%*/` `{` `/*comment*/` `}` `%>`
CR222820 | URL parameters were lost when WebLogic Server switched from HTTP to HTTPS This problem has been resolved.
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.
CR240141 | When ErrorPage was configured in `web.xml`, `StackOverflowError` occurred if in-flight requests existed while undeploying the application. This problem has been resolved.
CR241734 | When an application threw a 403 exception, the error page mapped to this error code was correctly displayed in the browser only once. The 403 error message was displayed in the browser for subsequent attempts to access the same application. This problem has now been resolved.
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.
CR244689 | `ArrayIndexOutOfBoundsException` occurred when a zero length string was returned by Accept-Language header. Now, default locale is used when Accept-Language header returns a zero length string.
CR245164 | In the case of HTTPS requests, multiple applications deployed on WebLogic Server did not work with single sign-on. This problem has been resolved.
CR246424 | When servlet filters were used, wrapped responses did not correctly handle changes in the character set. This problem has been resolved.
CR247655 | Refer to the security advisory information available at: http://dev2dev.bea.com/pub/advisory/189
CR248397 | Since the number of socket muxer threads is limited in the server, deadlock sometimes occurred when the incoming requests had bad headers and the error page was served on the socket muxer thread instead of on a separate thread. This problem has been resolved.
CR250915, CR273129 | Sometimes, under heavy load, messages related to BEA-101326 or BEA-101083 were logged in WebLogic Server logs when valid sockets were closed prematurely due to corruption in data structures. However, these exceptions had no impact when the client was a web browser because only idle TCP connections and not active connections were prematurely closed when this problem occurred. A socket is now closed only after the socket times out.
CR251800 | When `DirectoryIndexEnabled` was set for a Web application and there was a multi-bytes name in the Web application directory, the generated response did not correctly display the multi-bytes name. This problem has been resolved.
CR253615 | When the `WebAppComponentRuntimeMBean.getDeploymentState()` API was used, WebLogic Server always returned `UNPREPARED` as the deployment state for web applications (even for applications in active and running state). This problem has been resolved.
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.
CR258755 | During undeployment or server shutdown, WebLogic Server did not wait for in-flight requests of all applications to finish. Now, the weblogic.http.inflightRequestTimeoutSecs property has been added. When this property is passed during server startup, server waits for the duration specified by this property (in seconds) for in-flight requests of all applications to finish. This value overrides any value declared in weblogic.xml.
CR259956 | Attempt to change the Content-Type after calling `getWriter()` threw an `IllegalStateException`. This exception no longer occurs. However, the new content type is ignored and the response is written back to the client with the original content type.
CR263388 | `SessionData.getInternalAttribute` threw an `IllegalStateException` when `EncodeSessionIdInQueryParams` was used, and the session was invalidated programmatically. This problem has been resolved.
CR264139 | `DestroyContext` was not called during rollback for the webapp module when some other module in the application failed to deploy. This problem has been resolved.
CR265340 | A secure cookie (`_wl_authcookie_`) was not generated when an application used `ServletAuthentication` WebLogic class to authenticate and pass a custom `JAAS CallbackHandler` to it. This problem has been resolved.
CR265365 | `NameNotFoundException` occurred on JNDI lookup when `web.xml` contained `<res-type>java.net.URL</res-type>`. The client can now do the JNDI lookup if `<res-type>` in `web.xml` has been declared as `java.net.URL` and the JNDI name is given as `http://$HOST:PORT$/$CONTEXT_ROOT/Resource`.
CR267058 | When HTTP requests were received at the same time as log-rotation, deadlock sometimes occurred when the ELF Headers were written to the Log file. This problem has been resolved.
CR267161 | `ClassNotFound` Exceptions were not logged in the log file or shown on standard output. All the exceptions except for the `SocketResetException` are now logged.
CR271538 | Exception occurred when EJB lookup was done using `HttpClusterServlet` with the EJB deployed on the backend server, and HTTP Tunneling was enabled. The client can now lookup EJB on the backend server by using the new `weblogic.tunnel.prefix` property when the lookup is done using proxy server having `HttpClusterServlet` with HTTP Tunneling enabled.

## SNMP

####

Change Request Number | Description
--- | ---
CR258759 | Intermittent timeout on the SNMP Tool occurred due to mismatches found in the SNMP Request Handlers. These mismatches caused infinite looping of the client until the server returned correct data. This problem has been resolved.
CR268380 | The SNMP Request Handler for EntityCacheCurrentState entity updated the wrong data structure. These values were not correctly returned and so the SNMP client executed infinitely until the expected values were returned. This problem has been resolved.

## Tools

####

Change Request Number | Description
--- | ---
CR232808 | Prepared statement leak occurred on inserting more than 1000 chars to the database field because of a bug in Oracle driver. The bug has been resolved by Oracle.
CR247592 | There was a negative impact on performance when BEA Type4 driver was used with Oracle 10G. This problem has been resolved.

## Web Services

####

Change Request Number | Description
--- | ---
CR126453 | An attempt to change the JMS store used for Reliable Soap Messaging leads to a 'Server already exists' message. The default JMS server for Reliable Soap Messaging is `WSStoreForwardInternalJMSServer<servername>`. An attempt to change the JMS store causes WebLogic Server to fail on restart. WebLogic Server now allows you to change the JMS store. However, any messages used for Reliable Soap Messaging in the previous store would be lost.
CR187361 | Soap messages containing attachments were not handled correctly. This problem has been resolved.
CR189319 | When the included schema did not specify targetNamespace, `XSDValidityException` occurred when the client application was generated using clientgen. This problem has been resolved.
CR189630 | When `SOAPBody` was replaced by `SOAPBody.detachNode()` and `SOAPEnvelope.addBody()`, and again added using `addBody()`, the resultant SOAPMessage did not contain the `SOAPBody`. This problem has been resolved.
CR202225 | The value associated with `<soap:address location="..." />` in the WSDL could not be customized in `servicegen` or using `web-service.xml` file. Now, the `defaultEndpoint` attribute can be used both in`servicegen/client` and `clientgen` ant tasks to update the endpoint URL of the WSDL.
CR227508, CR229067 | The WSDL file generated by WebLogic Server was not compatible with WS-I Basic Profile 1.0 when extra text nodes (spaces, tabs) were generated in the resultant WSDL, and when the namespace was added to the `soap:binding` in the case of document style WSDL service. Now, the WSDL generated by WebLogic Server is compatible with WS-I Basic Profile.
CR232701 | When the input and output message names were the same, compilation failed because the generated stub had the same name for the arguments of the method. Now, `2` is appended to the second argument in the argument list. For example, if the input and output message name is `msg`, then the argument list is `msg, msg2`.
CR237756 | When two-way SSL was used to secure the connection when invoking a WebLogic Web Service, WebLogic Server always asserted the identity of the certificate to ensure that it mapped to a valid WebLogic Server user. Now, when you use two-way SSL to secure the connection when invoking a WebLogic Web Service, WebLogic Server uses anonymous identity to authorize access to the Web Service. If this authorization fails, WebLogic Server first asserts the identity of the certificate to ensure that it maps to a valid WebLogic Server user and then uses that user identity to invoke the Web Service.
CR238017 | Clientgen generated wrong stub method signature when the complex type extended from another type and had a single array of element. This problem has been resolved.
CR239515 | The `targetNamespace` attribute for the autotype ant task was being ignored by the tool. This problem has been resolved.
CR239750 | XML generated using `SOAPElement.toString()` method was formatted based on the pretty-format. This problem has been resolved.
CR240277 | `OutOfMemoryError` occurred at `weblogic.xml.babel.scanner.ScannerState` under heavy load when the Babel parser was used. This problem has been resolved.
CR240673 | WebLogic Server was unable to parse `&#0;(&#x0;)` character references. This problem has now been resolved.
CR244903 | When the plug-in was configured to use the `PathPrepend` parameter, the web service `soap:address` location contained the `PathPrepend`. Now, WebLogic Server removes any `PathPrepend` value found in the location URI before setting the location headers.
CR246728 | `clientgen` failed to generate code from a WSDL that contained elements without a prefix (elements in the default namespace) This problem has been resolved.
CR250750 | Web Service client failed when the client request was via a HTTP proxy that required authentication. This problem has been resolved.
CR253973 | When two beans that inherit from a single class were compiled using a single servicegen task, the generated Codec were incorrect and did not follow the inheritance hierarchy. This problem has been resolved.
CR254204 | Clients that invoked one-way operation over JMS binding opened receiving threads to poll the JMS queue for a web service response. Since one-way methods do not return anything, the thread should not be waiting for a response. This problem has been resolved.
CR254212 | When a proxy host is used for a few, but not all web services clients, and when the non-proxy host property `-Dhttps.nonProxyHosts` was set to `true`, the container still attempted to use the proxy to connect to these hosts. Now, the `-Dweblogic.webservice.transport.https.proxy.nonProxyHosts` system property has been added for the web service client. Using this property, you can specify the hosts that should be directly connected using SSL, even when `-Dweblogic.webservice.transport.https.proxy.proxyHost` is set to `true`.
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.
CR258574 | SOAP fault was not thrown when a java class-based web service client made a request without the required username token. This problem has been resolved.
CR265930 | Clientgen failed to create the `client jar` file for `simpleType` with `restriction base="xsd:base64Binary"`. This problem has been resolved.
CR266255 | Under heavy load, obtaining session from the web service caused `weblogic.webservice.context.ContextNotFoundException`. This problem has been resolved.
CR266913 | WebLogic Web Services client created using clientgen failed to parse the response when it interacted with the Axis Server using `multirefs` element. The problem has been resolved.
CR268607 | When the web service name contained a `.` (period) character, the service was not compiled properly. This problem has been resolved.
CR268909 | `java.lang.NoClassDefFoundError` occurred when a web service with an attachment was sent from the server to the client. This problem occurred only when the web service client used `webservicesclient.jar`. This problem has been resolved.

## WebLogic Tuxedo Connector

####

Change Request Number | Description
--- | ---
CR236397 | Undeploying or removing a WTC server leaves the local domain listening port open. Now the WTCService ensures the proper shutdown of the thread and closes the server socket.
CR236618 | When using WTC with Tuxedo applications, a transaction will be committed even when TPENOENT is returned. Now, when a call fails with TPENOENT, the commit will also fail.
CR237600 | When a communication problem occurred between WebLogic Tuxedo Connector (WTC) and Tuxedo during a transaction commit, the following problems occurred: WTC did not timeout when no response was received. WTC did not retry to commit the transaction. After communications were reestablished, the transaction on Tuxedo was rolled back. These problems have been resolved.
CR239312 CR256289 | WebLogic Server hangs due to no response between WTC and Tuxedo CORBA requests. A timeout value for CORBA requests has been added that resolves the WebLogic Server hang.

## XML

####

Change Request Number | Description
--- | ---
CR218364 | `NullPointerException` occurred when `RegistryDocumentBuilder` was used with schema validation to parse XML documents. This problem has been resolved.
CR262338 | `OutofMemory` exception occurred while parsing large XML documents. This problem has been resolved.