Skip navigation.
Downloads | Product Documentation | Support

Known and Resolved Issues

# WebLogic Server Known and Resolved Issues

The following sections describe known problems in WebLogic Server 9.1, as well as problems that were resolved in 9.1. Entries include a description of the problem, and a workaround or solution where appropriate. A notation in the Fixed In column indicates that the problem has been resolved.

For information about new and changed functionality in WebLogic Server 9.1, see What's New in WebLogic Server 9.1.

- Administration Console
- Apache Beehive Support
- Core Server
- Deployment
- EJBs
- Examples
- Installation
- J2EE
- JDBC
- JMS
- JSP and Servlet
- JTA
- Java Virtual Machine (JVM)
- Monitoring
- Node Manager
- Online Help
- Operations, Administration, and Management
- Plug-ins
- Security
- Spring Framework on WebLogic Server
- Web Services and XML
- WebLogic Tuxedo Connector

# Administration Console

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR063594 | Information about cached JDBC statements is not displayed on the JDBC Monitoring pages. | 9.0 Beta |
CR186966 | The Administration Console uses the JMX management interfaces to interact with WebLogic Server. WebLogic Server supports several MBean servers that provide access to management features from different perspectives. Although these MBean servers may be disabled in the WebLogic Server configuration files, the Administration Console requires these MBean servers during operation and will not run successfully without them. | 9.0 |
CR198678 | The Administration Console still shows the default table size even after the preferred table size is set to something other than the default size. | 9.0 |
CR200627 | After a page flow completes in the Administration Console, it forwards to a different page, typically a table. Pressing the browser back button at this point results in an attempt to load the last JSP file in the completed assistant. At this point, all of the context for this assistant is discarded. Workaround or Solution: BEA recommends that you do not use the browser back button to step back into an assistant once changes are cancelled or finished, and that you do not go back to a previous step in an assistant. Instead, use the navigation links and buttons in the Administration Console. | 9.0 |
CR202364 | On the Domain Logging page, if the limit of 100 logs was reached, additional logs were not visible. | 9.0 Beta | 9.1
CR202565 | You can use the Administration Console to shut down the Administration Server, but as the Administration Console attempts to refresh itself, it often encounters a problem displaying the page because the Administration Server is no longer available to service requests. This failure manifests itself in different ways, depending on the timing, machine load, and other deployments. | 9.0 |
CR204630 | An EJB-style Web service can not be tested through the Administration Console. The EJB Module-->Testing tab cannot be used to test the deployment of an EJB Module (JAR file). | 9.0 Beta |
CR204886 | No more than 50 users or groups from an external LDAP server or database can be displayed in the Administration Console. | 9.0 Beta |
CR205669 | The Administration Console did not support JMS message management for distributed queue and uniform distributed queue members. Workaround or Solution: The Administration Console has been extended to support these features. A new button, Show Messages, has been added to the Distributed Queue and Uniform Distributed Queue Monitoring pages. To access the JMS Message Management page for a member, select the member instance and click this button. | 9.0 | 9.1
CR206499 | Applications can have dependencies on resources that are configured outside the scope of that application. The Administration Console represented these dependencies (in the deployment plan and deployment descriptors) just like any other configuration setting, making it inconvenient to discover and edit resource dependencies. The Administration Console should represent these dependencies differently. Workaround or Solution: The Administration Console now includes an additional page under the application's Deployment Plan tab that includes a tree of resource dependencies for an application. Any missing or unresolved dependencies are highlighted by a red icon. | 9.0 | 9.1
CR207640 | After you add security providers to a security realm, the new security providers appear in the Change list, and the Change list will indicate which servers need to be rebooted to add the providers to the realm. | 9.0 Beta | 9.1
CR208120 | The Dump Thread Stacks feature in the Administration Console (Server page --> Monitoring --> Performance --> Lock&Edit --> Dump Thread Stacks) only works if the server is running on JRockit. Workaround or Solution: Thread dumps work on all Virtual Machines if you use the WebLogic Scripting Tool. | 9.0 |
CR208258 | Applications deployed on a cluster do not appear in the list of deployments for each server in the Deployments tab. | 9.0 |
CR208373 | Message-Driven Beans (MDB) may specify adapter-jndi-name in the deployment descriptor to indicate that the MDB is receiving messages from a resource adapter rather than from JMS. Such a binding entails configuring an ActivationSpec object which is passed to the resource adapter during deployment. The Administration Console does not currently provide a way to view or configure the Resource Adapter that an MDB is bound to. The Administration Console does not currently provide a way to view or configure the ActivationSpec properties on the MDB. | 9.0 |
CR208388 | In resource adapters, JNDI names are used for the following three types of objects: The Resource Adapter bean Each outbound connection pool Each administered object The Administration Console did not display the Resource Adapter bean JNDI name. | 9.0 | 9.1
CR208653 | On the Cluster -> Configuration -> Migration page, you must select the Candidate Machines that you want to use for Migratable Servers at the same time that you specify a cluster-wide data source in the Data Source for Automatic Migration field. | 9.0 Beta |
CR209073 | JMS service migration does not work when you use the Administration Console. Workaround or Solution: Use the `weblogic.Admin` command-line utility. Or configure a migratable server in place of migrating a JMS server, as described in "Server Migration". | 9.0 Beta | 9.1
CR209110 | The Administration Console sends log messages to the Administration Server log, but you cannot use the Console to filter the messages or use the log configuration pages to reconfigure Console logging. Workaround or Solution: Use `-Dlog4j.configuration=path-to-config`. | 9.0 |
CR210869 | When a role or policy condition is created or modified in the Administration Console, you must click the Save button before leaving the role/policy editor page. Otherwise, all the changes made during the creation or modification of the condition(s) that are displayed get lost when you return to the same page. No warning pop-up or message appears to tell you that leaving the page without clicking Save negates your changes. | 9.0 |
CR213392 | The ability to configure and monitor durable subscribers was available through the WebLogic Server 8.1 Administration Console, but was not available through the WebLogic Server 9.0 Administration Console. | 9.0 | 9.1
CR217559 | Configuring a JDBC Data Source using the Administration Console was too complicated as there were too many configuration settings on a single page. Workaround or Solution: The Administration Console pages for JDBC Data Sources have been redesigned to ensure information is better organized and that the user is able to navigate easily. The following new pages have been added for JDBC Data Sources: Configuration/Transaction, Configuration/Diagnostics, and Security. In addition, the General and Connection Pool pages have also been redesigned. | 9.0 | 9.1
CR217569 | The Administration Console presented JMS configuration values even if a Message-Driven Bean (MDB) was sourced by a resource adapter. The Administration Console did not provide a way to configure (read and/or write) the adapter-jndi-name for an RA-MDB. | 9.0 | 9.1
CR221062 | After you enable the administration port from the Administration Console and click the Activate button, the Administration Console is not reachable until the URL used to communicate with the Administration Console is changed to HTTPS and the administration port number. Because the administration port setting is dynamic, the Administration Console should redirect after activating any changes regarding the use of the administration port. | 9.0 |
CR223221 | As part of the JMS Modules > [module] > [topic] > Monitoring > Durable Subscribers > Monitoring tab, the table of durable subscribers should provide a link to browse the messages queued for the subscriber. The New, Move and Delete operations should be available for selected messages. | 9.0 | 9.1
CR223221 | The Administration Console should support JMS Message Management for durable subscribers. Workaround or Solution: The Administration Console has been extended to support this feature. To access the JMS Message Management page for a durable subscriber, select an instance of the durable subscriber and click 'Show Messages'. | 9.0 | 9.1
CR223643 | If you upload a non-ascii name application in the Administration Console, the file name appears garbled. | 9.0 |
CR226270 | After you specify the location for the new plan for a resource adapter, the Administration Console takes you back to the "Settings for <adapter name>" screen where it says that no Deployment Plan is selected. Workaround or Solution: You must have separate directories for the application and the plan instead of placing both files in the same directory. | 9.0 |
CR226301 | As administrators configure applications in the Administration Console, some configuration changes are saved as deployment plan variables. The Deployment Plan pages allow you to view the variables that have been set in the deployment plan and to delete one or more variables from that plan. The Deployment Plan pages used to view and edit variables are only available for an application, but should also be available for stand-alone deployments. Workaround or Solution: Administrators should navigate to the individual configuration pages for a deployment, module, or component, viewing and editing configuration settings that are specific to that deployment. Deployment plans can also be edited outside of the Administration Console environment by using an XML or text editor. | 9.0 |
CR226684 | The following pages, which were visible in the WebLogic Server 8.1 Administration Console, were not available in WebLogic Server 9.0: Active JMS Sessions, Active JMS Producers and Active JMS Consumers. Workaround or Solution: The missing pages have been reinstated. Select the instance of WebLogic JMS Server you would like to monitor, and then click the Monitoring > Active JMS Connections link. Links to JMS Sessions page are provided in the Sessions Current Count column. In the JMS Sessions page, the links to JMS Consumers and JMS Producers pages are provided in Consumers and Producers columns. | 9.0 | 9.1
CR228003 | Configuring request classes and constraints, in the Administration Console, for a Work Manager needed to be simplified. Workaround or Solution: The Administration Console Work Management Configuration pages and assistants have been redesigned to simplify the process of configuring and targeting Work Manager artifacts. Buttons to create and assign request classes and constraints have also been included. | 9.0 | 9.1
CR228589 | The Jolt Connection Pool monitoring pages in the Administration Console cannot access the Jolt Runtime MBeans, and therefore Jolt connection pools cannot be monitored or reset using the Administration Console. Workaround or Solution: Use WebLogic Scripting Tool (WLST) to access the Jolt Runtime MBean. | 9.0 |
CR228878 | The WebLogic Server 9.0 Administration Console Monitoring pages did not reflect the right status when the Server was JACC Enabled. Workaround or Solution: The JACC Enabled fields in the Administration Console Server table and the Monitoring and General pages now correctly reflect the security setting. | 9.0 | 9.1
CR230275 | The following attributes are currently missing from the Domain > Configuration > JTA page under Advanced: `MaxXACallMillis` `weblogic.management.configuration.JTAMBean` Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain. Default: `120000` `MaxResourceUnavailableMillis` `weblogic.management.configuration.JTAMBean` The maximum duration (in milliseconds) that an XA resource is marked as unhealthy. After this duration, the XA resource is declared available again, even if the resource is not explicitly re-registered with the transaction manager. This setting applies to the entire domain. Default: `1800000` `MaxResourceRequestOnServer` `weblogic.management.configuration.JTAMBean` Maximum number of concurrent requests to resources allowed for each server in the domain. Default: `50` Minimum: `10` Maximum: `java.lang.Integer.MAX_VALUE` | 9.0 |
CR230611 | The Administration Console can be used to attach a policy to a Web Service. However, if you attach more than one policy to a Web Service operation, you receive a `BeanAlreadyExists` exception when you click Activate to redeploy the application with the new policies. Workaround or Solution: Manually redeploy the application. | 9.0 | 9.1
CR231734 | The chooser control is used in several pages in the Administration Console and presents a list of available items, chosen items, and controls to move items from one list to the other. This control does not support moving more than one item at a time using a CTRL+mouse click interaction. Workaround or Solution: Select and move one item at a time. | 9.0 |
CR233056 | The Administration Console did not always recognize Web Services that were defined within stand-alone EJB or WAR deployments. Workaround or Solution: Web Service descriptors within EARS and stand-alone EJB and WAR deployments are now correctly represented in the Administration Console. | 9.0 | 9.1
CR233421 | The Web Services Description Language Compiler hung when non-ascii characters were used in complexType. | 9.0 | 9.1
CR233862 | If an installed JDBC module has a password-encrypted field encrypted with the wrong key, an exception occurs in the Administration Console. This can occur when you copy a JDBC module from one domain to another. Workaround or Solution: To re-set the password correctly, use `java weblogic.security.Encrypt <password>` in the domain home directory and modify the module file to change the password value. | 9.0 |
CR233933 | The Administration Console occasionally displayed an incorrect JDNI table for a Server (the JNDI table did not include the names for any newly created management objects). To display the JNDI table correctly, the user had to restart the Server. In addition, the Administration Console sometimes attempted to display details for application-scoped names that were not resolvable outside of the application, resulting in exceptions. Workaround or Solution: The Administration Console now displays the JNDI tree and nodes for a server correctly. | 9.0 | 9.1
CR234112 | When you use the Summary of Asynchronous Tasks function in the Administration Console, invoking Cancel on a running task results in a `UIControlException`. | 9.0 |
CR234156 | If the Administration Console has been modified through a console extension, images and CSS pages get cached by the browser. You may notice the caching when using the MedRec Console. Workaround or Solution: Close all the browser windows and then re-open the browser. | 9.0 |
CR234373 | The Administration Console required an Administration port for the Suspend and Force Suspend buttons, even though the suspend and force suspend operations did not strictly require it. | 9.0 | 9.1
CR234411 | When you create a security provider (any provider such as PKI credential mapper, auditing provider, authentication provider, and so on), the creation assistant takes the name of the provider and then returns to that provider's configuration summary page showing the newly added entry. However, the creation is not yet complete. You need to enter provider-specific details for it to be a valid provider configuration. | 9.0 |
CR234782 | The Administration Console should provide for a centralized subdeployment management interface for the JMS System Module. Workaround or Solution: A new subdeployment table page has been added, using which the user can add and delete subdeployment for the JMS System Module and assign or reassign targets for the subdeployment. | 9.0 | 9.1
CR234938 | The JMX MBean server only allows security management operations on the runtime bean tree. The Administration Console also prevents security management operations while a pending configuration change is in progress. For example, if an authentication provider configuration is changed, the Administration Console prevents creating a new user for that authentication provider until the configuration change is complete, which typically requires a server re-boot. | 9.0 |
CR235930 | Mail encoding was not configurable on the SMTP configuration page in the diagnostic module. Upon SMTP notification, the mail body and subject were encoded in JVM default encoding. On Japanese Windows and UNIX, JVM default encoding was not mail-safe, which caused various problems such as character garbling, delivery failure, and so on. | 9.0 | 9.1
CR236585 | Using the Administration Console search pane results in a 404 error when it is run on other than the original locale. For example, the 404 error occurs if a French user uses the English version on the French locale. Workaround or Solution: Switch the browser's locale to en-us. | 9.0 |
CR237828 | When a user deleted a JMS resource from JMS system module, the subdeployment associated with the resource was also deleted. The problem has been resolved. | 9.0 | 9.1
CR238023 | The Administration Console occasionally reported a `NullPointerException` while activating changes after configuring destinations on a SAF agent. Workaround or Solution: The Administration Console now correctly configures destinations for SAF agents. Validation issues are reported as expected. | 9.0 | 9.1
CR242940 | The Administration Console mandates that a user understands and knows how to create a subdeployment. The pages and flow should be simplified such that the user has the option of simply accepting the default targets for a resource type, or click on a button to create a new subdeployment or select an existing subdeployment for the resource. Workaround or Solution: The Targets page for the JMS System module has been redesigned to simplify tasks. When creating a resource in a JMS system module, the Targets page will now list the default targets for a resource type. The user has the option of accepting this setting by clicking Finish, or clicking 'Advanced Targetting' to create a new subdeployment or select an existing subdeployment for the resource. | 9.1 | 9.1
CR243260 | In some cases, the WebLogic Server Administration Console displayed only the first Web Service selected in a deployed application. It ignored any subsequent Web Service that was selected. Occasionally, exceptions were encountered while displaying the wsdl for a Web Service. Workaround or Solution: The wsdl pages now work correctly, displaying selected Web Services. | 9.0 | 9.1
CR244259 | Application deployments which had references to library deployments were not represented correctly in the Administration Console. Workaround or Solution: The console pages that deploy and monitor applications and library deployments have been enhanced to enable you to: View library references for an application and also the applications that reference a library. Upgrade versioned libraries, redeploying referencing applications as needed. A number of checks have been added to the update, install, and lifecycle assistants to ensure the consistency of the operations with library modules. View and configure modules within a library from the perspective of the referencing application. In addition, the Monitoring pages for applications now include information from libraries referenced by these applications. | 9.0 | 9.1
CR244350 | When an application containing JMS modules is deployed, each module defined in the application is targeted. The Administration Console was not correctly targeting JMS module subdeployments. Further, it was cumbersome to determine how each of the modules within an application were targeted, as the targets for each module were displayed on separate pages. Workaround or Solution: During deployment, JMS modules are now correctly targeted by the Administration Console. To improve usability, the targeting pages for deployments have been redesigned to present a tree table describing the current target assignments for each module and submodules within a deployment. In addition, a new target assistant assists in setting target assignments for deployments. | 9.0 | 9.1

# Apache Beehive Support

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR210907 | Netui databinding expression language fails when BeanInfo overrides JavaBean property names. Evaluation of expressions in the Netui databinding expression language throws errors when BeanInfo netui databinding EL does not to work when java.beans.BeanInfo is used to override JavaBean property names. Workaround or Solution: Do not override JavaBean property names using BeanInfo if you use a JavaBean in Netui databinding. If you must databind to such a bean, wrap the bean in a UI version of the bean that follows the JavaBean property naming convention. | 9.0 |
CR227429 | The service control generator does not support implicitly wrapped WSDL types. In the 8.1 release of WebLogic Server, service controls generated from wrapped style WSDLs hid the wrapping details from the user, resulting in implicitly wrapped types. In 9.0 and 9.1, implicitly wrapped types are not supported, that is, the generated control does not hide that parameters are wrapped when the service is called. | 9.0 |
CR234997 | The application.xml file contained in `BEA_HOME/weblogic90/common/deployable-libraries/weblogic-beehive-1.0.ear` has whitespaces before the xml declaration and causes errors when parsed with the Xerces XML parser. `<?xml version=?1.0? encoding=?UTF-8??>` Workaround or Solution: Remove the whitespaces at the beginning of the file: 1. Extract all files in `BEA_HOME/common/deployable-libraries/weblogic-beehive-1.0.ear` into a folder. 2. Edit application.xml, removing the whitespace preceding `<?xml version=?1.0? encoding=?UTF-8??>` 3. Make a new EAR file of the same name (weblogic-beehive-1.0.ear) containing all files extracted from the original EAR file. 4. Replace the original EAR file with the new one. | 9.0 |
CR237173 | The build-control-module task references a CLASSPATH property that does not exist. If you use the build-control-module task and see the following error message during the build process: `<drive>:\bea\weblogic90\beehive\weblogic-beehive\ant\weblogic-beehive-buildmodules.xml:140: taskdef class org.apache.beehive.controls.runtime.packaging.ControlJarTask cannot be found` you need to modify the Ant build script that calls it. Workaround or Solution: Add the following line to the Ant build script: `<property name="controls.jars.prop" refid="controls.dependency.path"/>` after importing `weblogic-beehive-imports.xml` and `weblogic-beehive-tools.xml`, but before importing `weblogic-beehive-buildmodules.xml`, as indicated by the following example: `<import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-imports.xml"/> <import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-tools.xml"/> <property name="controls.jars.prop" refid="controls.dependency.path"/> <import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-buildmodules.xml"/>` | 9.0 |

# Beangen

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR199361 | The user needed flexibility to remove elements from a deployment plan. Workaround or Solution: The user can now add a 'remove' element to the 'variable-assignment' element in the plan as follows: `<variable-assignment>` `...` `<operation>remove</operation>` `</variable-assignment>` Note: Only elements of primitive array can be removed. | 9.0 | 9.1
CR200754 | If a deployment plan has overrides of non-configurable elements, WebLogic Server does not currently reject the elements or fail to parse them. Workaround or Solution: Use configurable elements that use these annotations: @configurable @dependency @declaration @dynamic | 9.0 |

# Core Server

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR185820 CR185821 | If a client has installed a reverse-proxy server with IP mapping, an IP address and domain name may be externally exposed and discovered by someone outside the firewall. | 8.1 |
CR217067 | The `Low Memory Granularity Level` attribute was disabled. WebLogic Server logged a warning message when the average free memory value is smaller than the `Low Memory GC Threshold` value. | 9.0 Beta | 9.1
CR227086 | After you migrated a JTA service, changes to the Hosting Server available from the JTAMigratableTarget did not appear in the Administration Console. Because the changes did not appear, it was not obvious whether the migration succeeded or failed. | 9.0 | 9.1
CR227959 | A server that crashes may not be restarted successfully by the NodeManager on the current machine because it reads the lease as still active when it is not. (HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis) < FencingGracePeriodMillis is enforced in the code. Currently, the following equation determines the length of the lease: (HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis * 2) + FencingGracePeriodMillis Workaround or Solution: A server that crashes is automatically migrated to a new machine where it will start successfully. So, the only negative effect is slightly increased downtime and a migration. The unnecessary migration can be avoided by increasing the `RestartDelaySeconds` value in `wlscontrol.sh` to equal the amount of time that the lease will last. | 9.0 |
CR228876 | If you misconfigure a channel, your instance of WebLogic Server may become unstable. For example, if you accidently point to an incorrect IP address, you will see an error message in the server log, but you cannot access the Administration Console via the original port and protocol. Workaround or Solution: The only way to regain access to the Administration Console is to restart all servers. | 9.0 | 9.1
CR233272 | If you use a multi-threaded WebLogic Server 8.1 client (rather than a WebLogic Server 9.0 client) with a WebLogic Server 9.0 server, threads immediately fail with RJVM class cast exceptions. Workaround or Solution: Retry a few times. The problem only seems to occur with a newly booted server. | 9.0 | 9.1

# Deployment

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR067087 | The `security-permission` element is available in the `weblogic.xml` and `weblogic-ejb-jar.xml` deployment descriptors, but is not available in the `weblogic-application.xml` descriptor. Therefore, in an Enterprise application, you can only apply security policies to JAR files that are EJBs or Web applications. | 7.0 |
CR071138 | The `weblogic.Deployer` tool interprets any extra string values between command-line arguments as a file specification. For example, if you enter the command: `java weblogic.Deployer -activate -nostage true -name myname -source c:\myapp\mymodule` the tool attempts to activate a file specification named "true", because the `-nostage` option takes no arguments and "true" is an extraneous string value. | 7.0 |
CR091020 | If you deploy an application to a cluster and one or more clustered servers are unavailable (for example, servers partitioned from the cluster due to a network outage), the deployment operation may appear to hang. In addition, the partitioned servers may not deploy the application even after they successfully rejoin the cluster. Workaround or Solution: Reboot the partitioned servers after they rejoin the cluster. | 8.1 |
CR222004 | When you deployed only one module of an application, WebLogic Server deployed the entire application (all modules) to all the targets on which any single module was deployed or targeted. Although not apparent in the Administration Console, the application was accessible through all available servers. | 9.0 | 9.1
CR225655 | WebLogic Server did not support side-by-side deployment of applications with a Web Services module. (Side-by-side deployment introduces new application functionality without disrupting the existing traffic to the deployed application.) | 9.1 | 9.1
CR225867 | If you tried to deploy an application that referenced a missing library, the application did not start. | 9.0 | 9.1
CR231498 | When you deployed some services with an ant target, the XBus cluster DRT (part of remote.all) sometimes failed on remote machines and threw the following error: The domain edit lock is owned by another session in exclusive mode in XBus cluster DRTs. | 9.0 | 9.1
CR231643 | Killing the deploy command causes the activate operation to stay in preparing state for one hour. If you start a deployment operation through weblogic.Deployer and kill the command before the deployment actually starts, the underlying configuration manager activate operation may be left in the preparing state until the activate times out (one hour). If you attempt to perform another configuration manager save, undo, or activation operation during this time, you receive the following error: `weblogic.management.provider.EditFailedException: Unable to start new activation while preparing` Workaround or Solution: Cancel the edit session, which resets the state for the activate operation that is incorrectly left in the preparing state. You can cancel the edit session in the Administration Console or with the WebLogic Scripting Tool (WLST). To cancel the edit session in the Administration Console, log into the Administration Console and then click "Lock and Edit". To cancel the edit session using WLST, use the `cancelEdit()` command after connecting to the server. | 9.0 | 9.1
CR279281 | Some OS and NFS combinations result in deployment failures or configuration updates. Example exception is : `weblogic.management.DeploymentException: Attempt to operate 'distribute' on null BasicDeploymentMBean` Workaround or Solution: Run `statd()` and `lockd()` processes on every NFS client that accesses a remote NFS volume. If multiple servers that share the same domain root are started with different user Ids of same group, set the correct "umask" for the server processes so that a file created by one server can be opened for read/write by other servers without security exceptions. | 9.1 |

# EJBs

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR092577 | The EJBGen attribute, joinTable, was incorrectly named as jointTable. Workaround or Solution: The attribute has been renamed as joinTable. Users attempting to use the jointTable attribute will see a deprecation warning message. | 8.1 | 9.1
CR217875 | If you use Web Services with reliable messaging, you will see a warning message such as: `<Jun 8, 2005 9:33:36 AM PDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'uuid-677826faf045b124-7059d65b-1045cccaa 17--7ffb', class weblogic.wsee.server.jms.MdbWS was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>` Workaround or Solution: Ignore the message; it has no effect on the applications. | 9.0 | 9.1
CR217889 | Deploying a Web Service using a security model with custom roles or policies generates warnings about deployment descriptor roles or policies being ignored. Disregard these warning messages. Because the default security model is deployment descriptors only, these messages are not typically logged. | 9.0 | 9.1
CR225239 | The EJB QL parser did not allow the use of the UPPER and LOWER functions in the ORDER BY and GROUP BY clauses in an EJB QL query. Workaround or Solution: Support for these functions have been added. | 9.1 | 9.1
CR225261 | EJBGen did not provide a mechanism for setting the cluster-invalidation-disabled flag in the RDBMS deployment descriptor. Workaround or Solution: A new attribute `clusterInvalidationDisabled` has been added to the EJBGen annotation @Entity, enabling EJBGen to generate a cluster-invalidation-disabled element into weblogic-cmp-rdbms-jar.xml. | 9.0 | 9.1
CR227246 | The remote-client-timeout parameter was added as a WebLogic RMI compiler option in WebLogic Server 9.0. This parameter specifies an RMI-level timeout in seconds for remote clients that call the home and remote methods of the EJB. The remote-client-timeout parameter is not available for EJBGen. | 9.0 | 9.1
CR231076 | Monitoring information is not always available for Message Driven Beans. | 9.0 |
CR231909 | Using automatic table creation to deploy EJBs for Sybase results in every column in every table being non-null. As a result, if the EJB create method only takes a few of the CMP fields, creating EJBs fails with the following error: `column does not allow nulls` | 9.0 |
CR232006 | The <BEA-010212> error message incorrectly warned that a transaction attribute was not set for the method local[getLocalHandle()]. The problem has been resolved. | 9.0 | 9.1
CR233275 | A Messaging Proxy Service still receives and routes messages after it has been deleted if the user sends the messages to it. Workaround: Do not use the JMS destination to which the deleted Messaging Proxy Service was listening. | 9.0 |
CR233301 | WebLogic Server threw a `NullPointerException` when it does not find the weblogic-ejb-jar.xml file. | 9.0 | 9.1
CR234045 | When WebLogic Server 7.0 or WebLogic Server 8.1 is interoperating with WebLogic Server 9.0 and WebLogic Server 9.0 throws a `WorkRejectedException` (for example, when WebLogic Server 9.0 is in ADMIN mode instead of RUNNING), the following exception is raised on the WebLogic Server 7.0 or 8.1 server: `java.lang.ClassNotFoundException: Can't load class: weblogic.work.WorkRejectedException` Workaround or Solution: Fix the problem that causes the `WorkRejectedException`, or use WebLogic Server 8.1-style execute queues in WebLogic Server 9.0. | 9.0 | 9.1
CR237648 | For self-relationships, WebLogic Server threw an `IllegalStateException` when a related bean was created in the ejbPostCreate() method of the first bean. This problem has been resolved. | 9.0 | 9.1
CR238558 | During EJB deployment, a `NullPointerException` was thrown if the `EJBComponentMBean` was null. The problem has been resolved. | 9.1 | 9.1
CR239677 | WebLogic Server was creating multiple EJBTimerRuntimeMBeans with the same name. As a result of the duplicate names, subsequent EJBTimerRuntimeMBeans with the same name failed to register/unregister. Workaround or Solution: WebLogic Server now uses unique names for the EJBTimerRuntimeMBean. | 9.1 | 9.1
CR240418 | WebLogic Server threw an `UnimplementedOperationException` when running dynamic queries in EJB using the Sybase jConnect or jConn2 driver. Workaround or Solution: This problem has been resolved for both the drivers. To ensure the error is not thrown, the user needs to specify the sql-shape for the SQL query in the deployment descriptor. | 9.1 | 9.1
CR244720 | Prepared SQL queries, for CMP entity beans, that contained strings like '?1' were not returning any results. Workaround or Solution: The queries now execute correctly. | 9.1 | 9.1
CR244961 | During undeployment, MDBs were not unregistered from the migration service, causing a `NullPointerException` to be thrown during JMS migration. The problem has been resolved. | 9.0 | 9.1

# Examples

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR191354 | Medical Records does not yet use deployment plans. | 9.0 Beta |
CR208965 | The medrec.wls.config target in SAMPLES_HOME/server/medrec/setup/build.xml has a known issue with respect to security configuration. | 9.0 Beta |
CR234212 | In the JMS Queue example instructions, the queue's corresponding connection factory instance is referred to as `exampleQueue`. However, the actual connection factory name in the Examples server is `weblogic.examples.jms.QueueConnectionFactory`, which is identical to the connection factory's JNDI name. | 9.0 |
CR234523 | When you start the MedRec server, the following exception was thrown: `javax.naming.NameNotFoundException: While trying to look up comp/jmx/runtime in .; remaining name 'comp/jmx/runtime'` This exception prevented `RecordSessionEJBLifecycleListener` from registering the MedRec's custom model MBean, which affected the ability to disable the feature that keeps track of how many times `RecordSessionEJB` writes a prescription to the database. In addition, when you stopped the MedRec server and/or undeployed the `medrecEar`, a `NullPointerException` occurs in `RecordSessionEJBLifecycleListener.preStop()`. This exception prevented `RecordSessionEJBLifecycleListener` from unregistering the model MBean in the MBean server. Both issues were related to CR234476. | 9.0 | 9.1

# Installation

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR233609 | The Beehive documentation on the install CD does not contain Web Service Management information, which may result in broken links. Workaround or Solution: Use the Beehive documentation that is on the install CD rather than the documentation on the Apache website. | 9.0 |

# J2EE

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR209623 | XMLBeans was placing items in a ThreadLocal variable of `ExecuteThreads` causing items to stay in memory significantly longer than required. Workaround or Solution: XMLBeans now uses a cache to store items. Once the application is undeployed, these items are removed from the cache. | 9.1 | 9.1
CR222344 | The implementation of WebLogic Web application libraries does not support the registration of listeners from tag library descriptor (TLD) files within a Web application library. Workaround or Solution: Copy the listener registration to the `web.xml` file in your Web module. | 9.0 | 9.1
CR222344 | Servlet context listeners were not registered when the associated Web application referred to J2EE library modules. The problem has been resolved. | 9.0 | 9.1
CR233860 | WebLogic Server 9.0 threw a `NameNotFoundException` when the postStart method was called. Workaround or Solution: WebLogic Server now correctly sets the JNDI environment and no longer throws an exception. | 9.0 | 9.1
CR234476 | In `ApplicationLifecycleListeners` methods such as `preStop` and `postStart`, JNDI bindings such as `workarea`, `jmxRuntime`, and `UserTransaction` are currently unavailable. | 9.0 |
CR236011 | Web Application deployment failed if its web.xml file contained a description element, on the context-parameter element. This problem has been resolved. | 9.0 | 9.1
CR236808 | An application can refer to multiple libraries, each of which can do the same. The order of precedence is defined by the following two rules: The referring application/library has precedence over the library being referred to. Among the libraries being referred to by an application/library, a given library has precedence over the library declared after itself. The second rule was not being followed. The problem has been resolved. | 9.1 | 9.1
CR239947 | The JSP compiler was compiling JSP files in the staging directory, preventing the redeployment of the application. Workaround or Solution: The JSP compiler now uses a temporary directory to compile JSP files. | 9.0 | 9.1
CR241055 | A missing schemaLocation element in `weblogic-application.xsd` caused Eclipse to display an error when displaying the weblogic-application.xml file. Workaround or Solution: The missing schemaLocation element for the J2EE namespace has been added. | 9.2 | 9.1
CR244774 | The getReferencingRuntimes() method sometimes threw an exception. This problem has been resolved. | 9.0 | 9.1
CR245098 CR245099 | For stand-alone web applications, the ApplicationRuntimeMBean.getLibraryRuntimes() method returned null instead of the `LibraryRuntimeMBean`. Workaround or Solution: To get module level LibraryRuntimes - a new method, getLibraryRuntimes, has been added. | 9.0 | 9.1

# JDBC

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR188442 | The Oracle Thin JDBC driver has not been certified with JDK 5.0. In internal testing, BEA has noted test failures with the DECIMAL data type (TAR 4019650.995). Workaround: This issue has been fixed in Oracle's 10.2.0.2 thin driver. Please obtain the driver from Oracle. | 9.0 Beta | Oracle 10.2.0.2 thin driver.
CR223899 | Clear text passwords are not allowed if `ProductionModeEnabled` is set to true. Workaround or Solution: To deploy an application that contains application-scoped DataSource descriptors with `ProductionModeEnabled` set to true, the password for the Datasource must be in an encrypted format. To encrypt the Datasource password: 1. Create the domain in which you will be deploying the application. 2. From within the domain, run the following utility: `java weblogic.security.Encrypt` 3. Open the EAR file, and cut and paste this encrypted password into the appscoped descriptor (remove the clear text password). The usage for encrypt is simply: `java weblogic.security.Encrypt <password-to-be-encrypted>` | 9.0 |
CR229068 | When loading a new JDBC application-scoped DataSource descriptor file that used a deployment plan, WebLogic Server only searched locations inside the application EAR file. Workaround or Solution: WebLogic Server searches the inside and outside locations of the application EAR file. | 9.0 | 9.1
CR236331 | WebLogic Server failed to clean up internal data structures after a deployment failure was encountered for application-packaged JDBC modules. As a result, even after the cause of the error was fixed, subsequent deployment of the application failed. Workaround or Solution: WebLogic Server no longer needs to be restarted in order to deploy the application. | 9.0 | 9.1
CR236606CR236755 CR237109 CR238323 | Application-scoped JDBC data sources using the XA JDBC driver with multiple JNDI names got bound to the wrong context in the JNDI tree. As a result, errors occurred during a search. Workaround or Solution: You can now use multiple JNDI names for application-scoped JDBC data sources that use the XA JDBC driver. | 9.0 | 9.1
CR237985 | The `JDBCPreparedStatementCacheProfile` interface was mistakenly included in the WebLogic Server distribution. Workaround or Solution: This interface has been removed from the 9.1 release. | 9.0 | 9.1
CR239730 | The number of JDBC pool connections provided by WebLogic Server exceeded the limit defined by the maximum capacity. | 9.0 | 9.1
CR240059 | Performing multiple administrative actions on a JDBC data source configuration entity resulted in an `AssertionError`. This problem occurred because old task MBean instances were not removed from the MBean server, resulting in a name conflict each time a new task MBean is created for subsequent operations. | 9.1 | 9.1
CR241183 | Multi-threaded tests that use the `CachedrowsetImpl` method on an HP-UX machine are hanging. Workaround or Solution: To ensure the system does not hang, declare the spin lock object as volatile. | 9.0 | 9.1
CR241662 | An `EncryptionServiceException` occurred when a stand-alone domain upgrade process tries to convert a JDBC connection pool that contained plaintext passwords. | 9.1 | 9.1
CR242094 | Due to compatibility issues with Sybase's jConnect driver, a `SQLException` was displayed when an attempt was made to enlist an XATransaction. Workaround or Solution: WebLogic Server 9.1 now supports the Sybase jConnect 6.0 driver. | 9.1 | 9.1
CR242896 | When using the BEA MSSQL driver, the thread continued to be associated with the transaction even after the asynchronous transaction was rolled back. This problem has been resolved. | 9.1 | 9.1
CR280439 | There is a performance degradation in the WebLogic Type 4 JDBC Driver for Oracle `getAsciiStream()` method call caused by fixes and enhancements to character set support in the driver. In general, the updated driver outperforms the previous version of the driver. Workaround or Solution: Use the `getCharacterStream()` method instead of `getAsciiStream()`. | 9.1 |

# JMS

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR210328 | The SAFAgentRuntimeMBean statistic returned the wrong value for MesssageReceivedCount, MesssageCurrentCount, and MessagesPendingCount. | 9.0 | 9.1
CR229803 | In WebLogic Server 9.0, the error destination for a Uniform Distributed Destination was interpreted as a normal destination instead of a Uniform Distributed Destination (UDD). Workaround or Solution: The problem has been resolved. However, for UDDs the error destination has to be a UDD with identical targeting. Setting the error destination to a normal destination will lead to an error. | 9.0 | 9.1
CR230554 | MBean for SAF WindowInterval and support for the same in the Administration Console was needed. Workaround or Solution: The WindowInterval attribute was added to the SAFAgentMBean. This is the maximum amount of time, in milliseconds, that a JMS sending agent will wait before forwarding messages in a single batch. In addition, support for the WindowInterval attribute has been provided in the Store-and Forward Agents: Configuration: General [Advanced] page of the Administration Console. | 9.0 | 9.1
CR232015 | The user did not have permission to dynamically edit the FileStore's SynchronousWritePolicy attribute. The problem has been resolved. | 9.0 | 9.1
CR232327 | WebLogic Server does not clean up persistent data after there has been a failed persistent store upgrade. | 9.0 |
CR233120 | WebLogic Server unnecessarily persisted 2-Phase Commit records when it did not have any other IO work for a transaction in that store. Workaround or Solution: Users should see a significant performance improvement for JMS non-persistent message that are part of 2-Phase Commit transactions. | 9.0 | 9.1
CR233223 | Negatively acknowledged messages got a new SAF sequence number inside the messaging kernel, which caused out-of-order messages on the SAF endpoint. In the event that errors occurred during forwarding of messages from one server to another, messages were sometimes dropped. | 9.0 | 9.1
CR233815 | If you tried to use the Path Service Runtime Bean, or had more than one Path Service in the same domain, a couple of issues were encountered: The bean name from the JNDI used a '.' The names generated for the beans across clusters in the same domain were not unique. Workaround or Solution: The Path Service Bean name now uses the Configuration Bean name. | 9.0 | 9.1
CR233910 | WebLogic Server threw a `NullPointerException` when one attempted to view the BytesMessage details page in the Administration Console. | 9.0 | 9.1
CR234114 | When a client disconnected without closing the subscription, it took some time for the socket to determine that the client abruptly disconnected. As a result, JMS topic message listeners stopped receiving messages for some time. Workaround or Solution: Start the WebLogic 9.1 Server hosting the Topic with either of these properties: `-Dweblogic.jms.DisablePushEnvelope=true` `-Dweblogic.jms.DisableMultiSender=true` These settings will cause the server to serialize each message several times (to the same remote ConnectionFactory or TopicSession). In addition, single blocked sockets due to a disconnected client will no longer delay other subscriptions. Note: Might cause the system to slow down a bit. | 9.0 | 9.1
CR236062 | WebLogic Server allowed a JMS stand-alone application deployment to have the same name as a JMS System Resource. As a result, there was no way to distinguish between the destinations of the system resource and the application deployment. Workaround or Solution: A validation check is now performed that ensures no application deployment has the same name as a JMS System Resource. If you have prior configurations that use a System Resource Name for an application deployment, you need to rename one of the configuration elements. | 9.1 | 9.1
CR236651 | When non-persistent messages with a unit-of-order were forwarded through an imported destination configured with the at-most-once non-persistent override option, messages were delivered out of order. Workaround or Solution: The messages are now delivered in the correct order. | 9.0 | 9.1
CR236655 | In WebLogic Server 9.0, when JMS messages were sent with WLProducer.setUnitOfOrder, the size of user data was incorrectly calculated. Workaround or Solution: The Unit-of-Order (UOO) is no longer considered in determining user data size. | 9.0 | 9.1
CR236656 | In WebLogic Server 9.0, when JMS messages were sent to an SAF (Store-and-Forward) imported destination, the size of user data was incorrectly calculated. This problem has been resolved. | 9.0 | 9.1
CR236686 | The JMS C API incorrectly handled `javax.jms.* class` methods which returned -1 or NULL in non-error cases, causing the Sun JVM to crash. This problem has been resolved. | 9.1 | 9.1
CR236795 | When a user called the destroyJMSDurableSubscriberRuntime() API from `JMSDestinationRuntimeMBean`, the `JMSDurableSubscriberRuntimeMBean` was not deleted. Workaround or Solution: The destroyJMSDurableSubscriberRuntime() API from `JMSDestinationRuntimeMBean` now successfully deletes the associated `JMSDurableSubscriberRuntimeMBean`. | 9.1 | 9.1
CR237171 | Sending a large number of messages using the Unit-of-Order feature led to performance degradation. This problem has been resolved. | 9.0 | 9.1
CR237967 | JDBC Persistent XA map failed when used within a 2-phase transaction. This problem has been resolved. | 9.0 | 9.1
CR238559 | Debugging scope values for SAF debug APIs were incorrectly defined. Workaround or Solution: Correct values now appear in the Administration Console. | 9.0 | 9.1
CR239747 | An `ArrayIndexOutOfBoundsException` was displayed when the user tried to undeploy an undeployed JMS Server. Workaround or Solution: A more accurate JMSException is now displayed if a user tries to undeploy an undeployed JMS server. | 9.1 | 9.1
CR239861 | In many-to-many queuing benchmarks using a JDBC store, WebLogic Server 9.0 was slower than 8.1SP4. JMS stored the message header and the message body in separate records (applies only to messages with a message body greater than 1000 bytes). Workaround or Solution: This problem has been resolved. Significant performance improvement should occur with larger messages with a JDBC store but otherwise should not be visible. To obtain the original behavior, use the following command line option. `-Dweblogic.messaging.kernel.persistence.InLineBodyThreshold=1000` | 9.0 | 9.1
CR242086 | The Messaging Bridge could not send or receive messages when the MQSeries QOS level was set to 'Exactly-Once', causing transactions to be incorrectly proxied. The problem has been resolved. | 9.0 | 9.1
CR242117 | WebLogic Server could not start the JMS bridge if the connection URL was not provided. The problem has been resolved. | 9.0 | 9.1
CR242177 | When the 9.0 Upgrade Wizard upgraded a configuration with an 8.1 bridge, the path to the JMS bridge RAR did not update to reflect the new installation directory, which caused deployment to fail. This problem has been resolved. | 9.0 | 9.1
CR242729 | The following JMSModuleHelper API did not support the targeting of a newly created SAF imported destination onto a SAFAgent. `static void createSAFImportedDestinations(Context ctx, String resourceName, String safImportedDestinationsName, String safRemoteContextName, String targetName)` The problem has been resolved. | 9.1 | 9.1
CR243484 | Deployment of a JMS Module failed and a `NullPointerException` was thrown when a SAF imported destination group was configured without a SAF Remote Context. The problem has been resolved. | 9.1 | 9.1
CR243511 | In a cluster, failure in SAF caused JMS messages to remain undelivered, resulting in some messages getting lost. Workaround or Solution: Messages are no longer lost when forwarding to a distributed destination, in spite of an SAF failure. | 9.0 | 9.1
CR243664 | When a JMS destination in a packaged JMS module was paused for consumption using the Administration Console, the destination name was incorrectly displayed as NULL in the Server log. Workaround or Solution: The Server log now displays the correct JMS destination name. | 9.1 | 9.1
CR243728 | In some cases, due to the high volume of message acknowledgements and session recovery activities, JMS asynchronous message delivery went out-of-sync. Hence, some messages were not being delivered. This problem has been resolved. | 9.1 | 9.1
CR243924 | After a server reboot, if an application in a clustered environment attempted to access a JMS queue or topic that a client previously looked-up in JNDI, the location could not be used. Workaround or Solution: The application can now access the JMS Queue or topic. | 9.1 | 9.1
CR244002 | WebLogic Server was not naming all transactions. This problem has been resolved. | 9.0 | 9.1
CR244466 CR246779 CR246998 | In WebLogic Server 9.0, the weblogic.jms.extensions.WLMessageProducer.send(jmsMessage) caused the client application to hang when the following circumstances occurred at the same time: WLMessageProducer.setUnitOfOrder("example1") was set before the application called wlMessageProducer.send(message) The distributed destination for the message contained DistributedDestinationBean.setUnitOfOrderRouting("PathService") instead of the default "Hash" An exception occurred when using the path service. This could be attributed to a network problem or the server not being rebooted. Workaround or Solution: The client no longer hangs and the correct exception is thrown. | 9.1 | 9.1
CR244652 | When JMS messages queued in the 'At-Least-Once' delivery mode failed in delivery, the messages were re-sent, but not necessarily in the right order. Workaround or Solution: All the messages are now delivered in the correct order. | 9.0 | 9.1
CR244778 | Due to a synchronization issue, SAF occasionally could lose JMS persistent messages sent to an imported topic. This problem has been resolved. | 9.1 | 9.1
CR244802 | Support for the weblogic.jms.extensions.WLMessage.getSize() method no longer exists. For information about JMS message management, refer to http://bernal.bea.com/stage/wls/docs91/jms_admin/manage_msg.html. | 9.0 | 9.1
CR245012 | When a target JMS System resource entity was created using JMSModuleHelper APIs, a `SubDeploymentMBean` was automatically created with the name of the resource (as specified by the sub-deployment-name parameter). However, a check was not done to ensure this name is unique. As a result, the user could not create a UDD with another UDD as its error destination. Workaround or Solution: A check is now in place to verify the name. If there is no matching `SubDeploymentMBean`, a new `SubDeploymentMBean` will be created (using the name specified by the sub-deployment-name parameter). If the sub-deployment-name parameter is not specified or there is no `SubDeploymentMBean` that matches the resource name, a new `SubDeploymentMBean` will be created using the name of the target resource. | 9.0 | 9.1
CR245022 | Some JMS messages were not delivered by the SAF agent if there was a change in the Distributed Destination membership. Workaround or Solution: The SAF agent now acknowledges the changes to the Distributed Destination membership and then delivers the messages. | 9.1 | 9.1
CR245066 | JMS messages were sent to an incorrect (older) erroneous destination even after the Uniform Distributed Destination configuration parameter was updated. Workaround or Solution: The location change in the Uniform Distributed Destination configuration parameter is acknowledged and the JMS message is sent to the updated location. | 9.1 | 9.1
CR245449 | The Non-XA adapter incorrectly behaved as an XA adapter, thereby attempting to support XA transactions. Workaround or Solution: The adapter's configuration descriptor information is now used to determine whether or not it is an XA adapter. | 9.0 | 9.1
CR245539 | JMS messages sent through SAF could stall if any Distributed Destination members were in the pause state. This problem delayed message delivery until the member returned to the unpaused state. Workaround or Solution: The paused status of a Distributed Destination member is conveyed to SAF, so that it can balance the message delivery load amongst the unpaused members. | 9.1 | 9.1
CR245608 | In a Web module, if an ejb-ref element was bound to a JNDI name in weblogic.xml, and the JNDI name contained a ${APPNAME} token, the token was incorrectly resolved to the Web module name, instead of the enterprise application name. Workaround or Solution: This problem was resolved. If your code is dependent on the earlier incorrect behavior, you need to modify your code. | 9.2 | 9.1
CR245809 | When a JMS message was sent to a JMS queue, topic or an SAF agent, statistics on the destination and the JMS server (or SAF agent) sometimes were not updated accurately. The problem occurred if the message expired (as per the predetermined expiry time), before it was actually delivered to a JMS queue or topic. This problem has been resolved. | 9.1 | 9.1
CR239218 | Message ordering is not always preserved when messages are produced by a single producer with a positive TimeToDeliver (that is, birth time) value. TimeToDeliver represents the delay before a sent message is made visible on its target destination. | 9.0 |

# JSP and Servlet

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR177147 | The WebLogic Server HTTP stack should implement a property that allows users to timeout connections in the 'Connect' phase. This problem has been resolved. You can now timeout connections in the 'Connect' phase by calling `setConnectTimeout` on `HttpURLConnection`. | 8.1 | 9.1
CR224130 | JSP expressions, provided in the JSPX document template text, were incorrectly evaluated. The problem has been resolved. | 9.0 | 9.1
CR227224 | In case of an error, the error request attributes were not set and the user defined error pages could not see these attributes. The problem has been resolved. | 9.0 | 9.1
CR228894 | The `WebAppComponentRuntimeMBean` and `ServletRuntimeMbean` interface names, created by the sub systems, were too long. Workaround or Solution: The names are now shorter as they now contain only the Web server and the Web application names. | 9.0 | 9.1
CR229405 | Folded headers in HTTP requests were not parsed properly. The problem has been resolved. | 9.0 | 9.1
CR229639 | Bad requests were not logged in the `access.log` file. The problem has been resolved. | 9.0 | 9.1
CR234493 | JMX reserves certain characters for its use. The names specified by users for WebLogic Server configuration artifacts or J2EE artifacts were used by WebLogic Server to create JMX ObjectNames. If a user name for any WebLogic Server configuration artifacts such as servers, or clusters, or J2EE artifacts such as beans, servlets, modules, or applications contains the following special characters: comma(,) colon(:) asterisk(*) question mark (?) equals (=) WebLogic Server will throw the following exception: `java.lang.Error: Unable to build an ObjectName for the instance` Workaround or Solution: Avoid using these special characters when naming these artifacts. | 9.0 | 9.1
CR234786 | In some cases, redeployment of a Web Application failed if an exception was encountered during a previous attempt at deployment. Workaround or Solution: The context registration is now purged before an application is redeployed. | 9.1 | 9.1
CR235154 | WebLogic Server HTTP handlers could not handle read and connect timeouts. This problem has been resolved. | 9.0 | 9.1
CR235453 | An infinite loop may occur when you print enormous numbers of multi-byte characters. Workaround or Solution: If your BEA_HOME is created by the Japanese, Chinese, and Korean installer kits for WebLogic Server 9.0, the fix is included in your kit. Otherwise, call customer support to request the patch for this problem. | 9.0 | 9.1
CR238074 | The `request.getContextPath()` method returned an incorrect value when JSPs were included from different contexts. This problem has been resolved. | 9.0 | 9.1
CR238704 | WebLogic Server could not resolve relative JSP nested include statements. The problem has been resolved. | 9.0 | 9.1
CR241298 | If you used a replicated session that had not been modified, the last-accessed-time change did not get propagated to secondary servers. The problem has been resolved. | 9.0 | 9.1
CR241334 | The Javelin Framework could not find JSP tag libraries which are in signed jar files. The problem has been resolved. | 9.1 | 9.1
CR241812 | The `access.log` file reported the total number of bytes as blank. The file should reflect the actual number of bytes or '-', if zero. The problem has been resolved. | 9.0 | 9.1
CR243378 | JSP expression language identifiers that started with an underscore (_) character were not getting resolved. Workaround or Solution: The underscore character is now treated as a valid character. | 9.0 | 9.1
CR244252 | WebLogic Server could not resolve functions from JSP expressions in JSPX or JSP XML documents. The problem has been resolved. | 9.0 | 9.1
CR244263 | The response generated by WebLogic Server contained XML headers. Workaround or Solution: XML headers are no longer printed as part of the response. | 9.0 | 9.1
N/A | The JSP 2.0 servlet class to be used for compiling JSPs on the server side is weblogic.servlet.JavelinxJSPServlet. Custom patterns other than *.jsp or *.jspx should be mapped to this servlet. For example: `<servlet>` `<servlet-name>JSPServlet</servlet-name>` `<servlet-class>weblogic.servlet.JavelinxJSPServlet</servlet-class>` `</servlet>` `<servlet-mapping>` `<servlet-name>JSPServlet</servlet-name>` `<url-pattern>*.psp</url-pattern>` `</servlet-mapping>` | 9.0 Beta |

# JTA

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR236160 | During migration of JTA services, data from the source server sometimes was not taken into account when recovery is initiated on the target server. This lead to a transaction collision between the coordinating (source) server's transaction context and the participant (target) server's transaction context in the target server. As a result, the transaction had to be rolled back even though the transaction had previously passed the commit point on the source server. Workaround or Solution: JTA migration services now work smoothly for transactions that exist on the participant (target) server as a subordinate to the coordinating (source) server. | 9.0 | 9.1
CR238835 | When migrating the JTA recovery service from a candidate server to a primary server, the primary server failed to boot as the candidate server continued to control the default file store for the primary server. Workaround or Solution: The file store for a migrated transaction recovery service is now closed when the service fails back to the primary server. | 9.1 | 9.1
CR231482 | Migration issues were encountered when migrating a XA JDBC data source that was configured with a non-XA driver, from WebLogic Server 7.0 to WebLogic Server 9.0. Workaround or Solution: The upgrade process has been corrected to ensure seamless transition. All recovered transactions will now be completed. | 9.0 | 9.1

# Java Virtual Machine (JVM)

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR183099 | In J2SE 1.5, certain garbage collector optimizations caused virtual machine crashes. | 9.0 | 9.1
CR229034 | An unexpected error was detected by HotSpot Virtual Machine. For more information about this issue, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4282986. Workaround or Solution: Download the J2SE 1.5.0.4 kit provided by Sun, and put it into the jdk150_04 directory instead of the jdk150_03 directory. | 9.0 | 9.1
CR231522 | After an upgrade of MedRec from WebLogic Server 8.1 to 9.0 on Solaris, the server crashes with a JVM error. Workaround or Solution: To start the upgraded server without crashing it, remove `-Xverify:none` from the server start command by setting `JAVA_OPTIONS=""` in the `setDomainEnv.sh` file after the following line: `. ${WL_HOME}/common/bin/commEnv.sh` | 9.0 |

# Monitoring

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR230807 | JDBC-based events and the harvester archive require that the data source is properly configured and that required tables are created in the database. If this is not done, SQL exceptions are thrown while diagnostic data is being written and read. Workaround or Solution: While the archive is being instantiated, checks should be made to confirm that the settings are valid. If not, the system should fall back on using the default store-based archive. WebLogic Server currently does not perform these checks. | 9.0 | 9.1
CR232645 | The deleteDataRecords method should work on records whose timestamp satisfies the following condition: startTime <= timestamp < endTime The newer implementation stores a collection of events into a single snapshot object. If any record within the snapshot satisfied the above condition, all records within the snapshot were processed for deletion. This resulted in a deletion of some records in the snapshot even though their timestamp does not fall in the range. | 9.0 | 9.1
CR233803 | If WebLogic Server is configured to have a WebLogic Diagnostic Framework (WLDF) Module deployed with Instrumentation enabled and the DyeInjection Monitor configured, any client application that attempts to use the provided WebLogic client jars, (instead of the `weblogic.jar`), encounters the following exception: `Exception in thread "main" org.omg.CORBA.COMM_FAILURE`. Workaround or Solution: Change the client application environment to use the `weblogic.jar`. | 9.0 | 9.1

# Node Manager

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR232997 | Usually, the custom stop script is used to clean up any server-specific resources. If the custom stop script is empty, `UnixProcessControl.createProcess0` may throw the following exception: `InternalError: waitpid() failed (errno = 10)` Workaround or Solution: Add a sleep 1 to the custom stop script if the script is empty. | 9.0 |

# Online Help

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR235341 | The suspend command description for WebLogic Scripting Tool includes the following note, which should be removed: Note: The domain administration port must be enabled to invoke the suspend command. In addition, the Note that appears in the startNodeManager command description should be updated as follows: Note: The WebLogic Server custom installation process optionally installs Node Manager as a Windows service on Windows systems, so that it starts automatically when you boot the computer. For more information, see "About Node Manager Installation as a Windows Service" in the BEA Products Installation Guide. In this case, you do not need to start the Node Manager manually. | 9.0 |
CR235773 | The following task help was incorrect in WebLogic Server 9.0 and was corrected as follows: Create Digital Signature Keystore In particular, following is wrong: The title is misleading. It should instead be "Specifying key pair for signing SOAP messages" The following prerequisite is missing: That user has obtained the private key and x.509 certificate pair and has added it to WebLogic Server's keystore, or a keystore that user has previously created. The initial blurb says that task is for specifying the key pair, but should say that task is for creating a key store. Step 11 says to enter "exact values". This is only true for the Name field. For the Value field, user should enter the name of the key store that contains the key pair which will be used for signing. Step 14 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the password of the key store that contains the key pair which will be used for signing. Step 17 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the name of the private key X.509 certificate pair (stored in keystore) which will be used for signing. Step 20 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the private of the private key X.509 certificate pair (stored in keystore) which will be used for signing. | 9.0 | 9.1
CR235775 | The following task help was incorrect in WebLogic Server 9.0 and was corrected as follows: Create Encryption Keystore In particular, following is wrong: The title is misleading. It should instead be "Specifying key pair for encrypting SOAP messages" The following prerequisite is missing: That user has obtained the private key and x.509 certificate pair and has added it to WebLogic Server's keystore, or a keystore that user has previously created. The initial blurb says that task is for specifying the key pair, but should say that task is for creating a key store. Step 11 says to enter "exact values". This is only true for the Name field. For the Value field, user should enter the name of the key store that contains the key pair which will be used for encrypting. Step 14 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the password of the key store that contains the key pair which will be used for encrypting. Step 17 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the name of the private key X.509 certificate pair (stored in keystore) which will be used for encrypting. Step 20 says to enter "exact values". This is only true for the Name field; for the Value field, user should enter the private of the private key X.509 certificate pair (stored in keystore) which will be used for encrypting. | 9.0 | 9.1

# Operations, Administration, and Management

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR226286 | If the execution of a WebLogic Server Scripting Tool (WLST) script failed, WLST ended without proper failure notification. As a result, calling components that depend on a successful WLST script execution were not aware of the failure, such as when WLST was employed via Ant, which is a common use case. | 9.0 | 9.1
CR231633 | Multi-byte characters were garbled when WebLogic Scripting Tool (WLST) ran in interactive mode. | 9.0 | 9.1
CR232858 | WebLogic Server Scripting Tool failed to launch when multi-byte characters were used in the installation path. | 9.0 | 9.1
CR233635 | The Managed Server failed to boot and a `SecurityInitializationException` was thrown if either the administrator user name or the Managed Server name included multi-byte characters. | 9.0 | 9.1
CR234394 | When invoking `nmConnect` from WLST with a Node Manager type of SSH or RSH, WLST copies the `wlscontrol.sh` to a temporary directory before invoking it, but the execute permission is not set for the file. As a result, the attempt to invoke `nmConnect()` with nmType SSH or RSH will fail. Workaround or Solution: After running java weblogic.WLST and a failed first attempt to run `nmConnect()`, change the file permission so that the temporary file created by WLST (for example `/var/tmp/wlstTemp/wlscontrol.sh`) has the execute bit on. | 9.0 | 9.1
CR236930 | Users with 'Monitor' and 'Operator' roles were unable to view the Deployments table in the Administration Console. This problem has been resolved. | 9.0 | 9.1
CR240969 | The Domain Runtime MBean Server did not reflect changes made to system resources during an 'activate'. The problem has been resolved. | 9.1 | 9.1

# Plug-ins

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR204640 | The ISAPI and NSAPI log files did not provide Uniform Resource Identifier (URI) information. Workaround or Solution: The log files are now more informative; the URI is now logged at the start of every request handled. | 9.0 | 9.1
CR233476 | Failover using Apache plug-in on Linux is not working because the POST requests are timing out. Workaround or Solution: Set KeepAliveEnabled=false in httpd.conf or use Apache MPM worker. | 9.0 | 9.1
CR233924 | The `HTTPClusterServlet` returned a 503 Error for a client whose primary and secondary servers had been killed using the Memory Replicated persistence type. Workaround or Solution: Initially, WebLogic Server accessed preferred servers in a loop; they are now accessed only once. | 9.0 | 9.1

# Security

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR182523 | Information on how to configure domains to enable inter-domain transactions (that is, all participating domains run on WebLogic Server 9.x, 8.x, 7.x, and 6.x domains or a combination of 9.x, 8.x, 7.x and 6.x) is incorrect in the Administration Console Help. Workaround: The information required to configure domains to enable inter-domain transactions is located online. See Configuring Domains for Inter-Domain Transactions in Programming WebLogic JTA. | 9.0 Beta | 9.2
CR200004 | If the server's SSL identity is changed, the SAML credential mapper continued to use the original SSL identity until the server was re-booted. For example, the SSL configuration was dynamic, but SAML only used the SSL configuration available when the server booted. | 9.0 | 9.1
CR226651 | When deploying a Web application with `CustomRolesAndPolicies` mode, the following warning message appeared: `<Warning> <Security> <BEA-090669> <Ignored deployment of policy for resource "type=<url>, application=XBus Kernel, contextPath=/asdf, uri=/">` This warning also appeared at server startup. | 9.0 | 9.1
CR231321 | The option, `-Dweblogic.system.StoreBootIdentity`, only works if the appropriate server security directory exists. This directory is usually created by the Configuration Wizard or upgrade tool. However, the appropriate server security directory could be absent in domains checked into source-control systems. | 9.0 |
CR233284 | The Web Service-based predicate "Element requires signature by" is listed twice when policy conditions on a Web Service resource are added. The predicate implementations are in fact the same. | 9.0 |
CR233887 | The 9.0 WebLogic Server javadocs mistakenly published the following internal classes that are not part of public API. Do not use them. `weblogic.management.security.authentication.UserLockoutManagerImpl` `weblogic.management.security.audit.ContextHandlerImpl` | 9.0 | 9.1

# Spring Framework on WebLogic Server

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR242675 | NullPointerException in the RMI classloader. | 9.0 | 9.1
CR236708 | There is an Antlr conflict between Hibernate 3 and WebLogic Server. | 8.1SP05, 9.0 | 9.1
CR242923 | T3 runtime cannot decode class descriptors that contain primitive types. | 9.0 | 9.1
CR242883 | IIOP runtime cannot decode class descriptors that contain primitive types. | 9.0 | 9.1
CR237532 | There is a WebApp classloading problem with the Spring Framework. | 8.1SP05, 9.0 | 9.1
CR241195 | Updating a record in the Spring Pet Clinic sample application can result in the following error: `java.lang.IllegalStateException: Cannot access session scope since the` `requested page does not participate in a session. at` `weblogic.servlet.jsp.PageContextImpl.getAttr ibute(PageContextImpl.java:273)` `at javax.servlet.jsp.jstl.core.Config.get(Confi g.java:145) at` `javax.servlet.jsp.jstl.core.Config.find(Conf ig.java:393) at` `org.apache.taglibs.standard.tag.common.fmt.T imeZoneSupport.getTimeZone(TimeZoneSupport.j ava:140)` Workaround or Solution: Comment out the first line in the includes.jsp file. | 9.0 |
CR244683 | HP-UX requires jdk150_01, not jdk150_03. Workaround or Solution: In the `medrec-spring` directory, replace jdk150_03 with jdk150_01. | 9.0 |
CR244693 | MedRec-Spring logout functionality does not work when you access MedRec-Spring from a remote machine. Workaround or Solution: Do not access the MedRec-Spring application from a remote machine and do not use localhost for request redirection. | 9.0 |
CR244691 | The Spring extension to the WebLogic Administration Console only supports Web applications (.war) files and cannot be used to monitor Spring Beans in non-.war files (such as in MedRec-Spring). | 9.0 |
CR243957 | When using `CTRL-C` to shut down WebLogic Server, a shutdown exception may occur when destroying the bean `domainMBeanServerConnection`. Workaround or Solution: Use the flag `-Dweblogic.slc=true` in order to determine when `domainRuntimeServerService` is started and stopped. | 9.0 |

# Web Applications

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR227462 | The web.xml deployment descriptor file used with a JPF webapp must correspond to the current version, version 2.4, of the Servlet Deployment Descriptor Schema from Sun. Use of a web.xml based on an older version of the schema will cause an XmlException. Workaround or Solution: For a JPF webapp, make sure your web.xml file corresponds to version 2.4 of Sun's Servlet Deployment Descriptor Schema, which can be found at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd. | 9.0 |

# Web Services and XML

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR189158 | WebLogic Server does not support Sparse Arrays and Partially Transmitted Arrays as required by the JAX-RPC 1.1 Spec. | 9.0 |
CR189856 | WebLogic Server does not support soap arrays when the `soapenc:Array` type is used directly as the type of an element as in the following example: `<xs:element name="generic" type="soapenc:Array"/>` | 9.0 |
CR200359 | Web Services of type document-literal wrapped are not supported with XMLBeans data types as input parameters or return values. | 9.0 Beta |
CR204454 | When you sign a SOAP message, an error is returned if you specify an xmldsig-filter2 transform in a Confidentiality assertion by setting the URI attribute of the `Policy/Confidentiality/Target/Transform` element in a WS-Policy file to `http://www.w3.org/2000/09/xmldsig#base64".` | 9.0 Beta |
CR208416 | The `wsdl2service` Ant task does not generate the JAX-RPC data type mapping file if the WSDL from which it is generating a Web Service specifies a fault. This means that, although you might be able to deploy the generated Web Service, you will not be able to correctly invoke its operations. Similarly, the `clientgen` Ant task also does not generate the client-side JAX-RPC mapping file when the WSDL file contains a fault. Workaround or Solution: Create the JAX-RPC mapping file manually. | 9.0 Beta | 9.0
CR218519 | Applicable to jwsc, wsdlc, and clientgen: Web Service interfaces, implementations and parameter types with upper case package names may have problems building and running in some operating systems. Workaround or Solution: BEA strongly recommends that you use lowercase letters for the package names. | 9.0 |
CR223291 | When a client sends an instance of complex type to a service, the service echoes back the received instance. If the complex type contains the "any" element as shown below, and the "any" content contains data, this data is not passed to the service. <element name="collection"> <complexType> <sequence> <element name="description" type="r:anycontent"/> <element ref="r:recipe" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> </element> | 9.0 |
CR225767 | The WebLogic Web Service rejected requests that contained an invalid Authorization header even though the security constraint was not defined in the web.xml file. The problem has been resolved. | 9.0 | 9.1
CR227068 | The wsdlc Ant task should support the `failOnError` parameter. Workaround or Solution: Both the wsdlc and jwsc Ant tasks now support the `failOnError` parameter. | 9.0 | 9.1
CR228385 | The Web Service Description Language (WSDL) compiler does not generate serializable data types, so data cannot be passed to remote EJBs or stored in a JMS destination. | 9.0 |
CR230549 | WLHttpsTransport causes the following error: `AsyncReponseService returned a 404` | 9.0 |
CR231508 | When a WebLogic Server Web Service uses XMLObject as a parameter, a `java.lang.IncompatibleClassChangeError` exception is thrown at runtime when the client tries to access the service. | 9.0 |
CR233310 | In WebLogic Server 9.0, if a Reliable Messaging request is sent to a Web Service that has a security policy or encryption configured, the send will fail. The problem has been resolved. | 9.0 | 9.1
CR233778 | Controls declared public in a JWS File cannot be compiled using `<jwsc>`. When an annotated control is declared public in a JWS class (a class annotated with `@WebService`) and is compiled with `<jwsc>`, improper wrapper code is generated. This will result in a compile-time error (`com.bea.util.jam.internal.javadoc.JavadocParsingException`). For example, the following code will result in a compile-time error if compiled with `<jwsc>`, because the control myControl is a public field: `@WebService public class Foo` `{` `@Control` `public MyControl myCtrl;` `?` `}` Workaround or Solution: Change the access modifier to private, protected, or package protected. | 9.0 | 9.1
CR234178 | The jwsc Ant task generated a WSDL of document-literal-wrapped Web Service that missed an input part, resulting in a request envelope with an empty body. This problem has been resolved. | 9.0 | 9.1
CR234262 | The javax.xml.transform.Source attachment does not work when the source xml has non-ascii characters. | 9.0 |
CR234316 | Signature reference validation failed if encrypted data contained special characters like the '&'. This problem has been resolved. | 9.0 | 9.1
CR235270 | The `wsdlc` Web Services Ant task cannot handle doc-literal-bare style Web Service when the element is not defined in `wsdl:part` as in the following example: `<message name="getTempRequest"> <part name="zip" type="xsd:string"/> </message>` Workaround or Solution: Add the element as in the following example: `<message name="getTempRequest"> <part name="zip" element="s0:getTemp" type="xsd:string"/> </message>` | 9.0 | 9.1
CR237192CR237196 | The `@weblogic.jws.security.SecurityRoles` JWS annotation did not work as documented; specifying it in your JWS file had no effect. | 9.0 | 9.1
CR238943 | The `webservices.xml` generated in the wsdlc ant task referred to the EJB implementation with an absolute path, instead of a relative path, leading to a deployment error. This problem has been resolved. | 9.0 | 9.1
CR239574 | For a specific WSDL, the bindings had the same local name, but belonged to different namespaces when the wsdlc task requested for the `srcBindingName` attribute. Workaround or Solution: Allow `srcBindingName` to set the namespace URI in the following format. `srcBindingName={NS}LocalPart` | 9.0 | 9.1
CR241480 | An `AssertionError` was encountered while deploying an EJB-implemented JWS from the WSDL. This problem has been resolved. | 9.0 | 9.1
CR242611 | WebLogic Server could not retrieve dynamic WSDLs when the service was protected. Workaround or Solution: Use the following to pass your username and password for basic authentication: `HttpTransportInfo info = new HttpTransportInfo();` `info.setUsername("foo".getBytes());` `info.setPassword("foo_pass5678".getBytes());` `SecureWebService service = new SecureWebService_Impl(args[0], info);` For proxy support: `HttpTransportInfo info = new HttpTransportInfo();` `Proxy p = new Proxy(Proxy.Type.HTTP, new` `InetSocketAddress(proxyHost,Integer.parseInt(proxyPort)));` `info.setProxy(p);` `info.setProxyUsername(user.getBytes());` `info.setProxyPassword(pass.getBytes());` `HttpProxySampleService service = new HttpProxySampleService_Impl(args[0],` `info);` | 9.0 | 9.1

# WebLogic Tuxedo Connector

####

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR127660 | View classes are not set on a per connection basis. A shared WebLogic Tuxedo Connector hash table can cause unexpected behavior in the server if two applications point to the same VIEW name with different definitions. There should be a hash table for the view classes on the connection as well as for the Resource section. Workaround or Solution: Ensure that all VIEW classes defined across all your WebLogic Workshop applications are consistent, meaning that you have the same VIEW name representing the same VIEW class. | 8.1 SP2 |
CR222778 | Error messages regarding retrieval of the local or remote domain passwords for a connection were insufficient. Workaround or Solution: WebLogic Server now displays the following error message when it encounters a problem retrieving the local or remote domain passwords for the connection being attempted: "A connection cannot be established between local domain {1} and remote domain {2} due to a problem with the local or remote password used to authenticate connections between these domains." | 8.1 | 9.1
CR237915 | WebLogic Tuxedo Connector could not handle network errors when the `TPACALL()` function was set up with an asynchronous callback. | 8.1 SP4 | 9.1
CR253111 | WebLogic Tuxedo Connector cannot re-establish the connection to the second remote domain if there is a network problem between the local domain and the first remote domain. This problem disappears once the remote Tuxedo GWTDOMAIN gateway starts responding to the session negotiation protocol exchange. Workaround or Solution: Establish a connection explicitly. The connection can be established using the "connect" command of dmadmin utility from the Tuxedo side. | 9.0 |