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

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

CR218667

Heap Size Current was not getting displayed on the Servers > Monitoring > Performance page of WebLogic Server 9.1 Administration Console.

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

CR316926

You can no longer view the version number of WebLogic Server through the Preferences > Version tab in Administration Console. This page was removed from the WebLogic Server Administration Console. The online help for WebLogic Server Administration Console states otherwise.

9.1

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
CR218667	Heap Size Current was not getting displayed on the Servers > Monitoring > Performance page of WebLogic Server 9.1 Administration Console.	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
CR316926	You can no longer view the version number of WebLogic Server through the Preferences > Version tab in Administration Console. This page was removed from the WebLogic Server Administration Console. The online help for WebLogic Server Administration Console states otherwise.	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

Change Request Number	Description and Workaround or Solution	Found 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

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

CR259784

On HP-UX, when an I/O operation on a file descriptor was cancelled, the socket was not getting properly cleaned and this caused a File Descriptor leak: this was leading to an OutofMemory exception.

Workaround or Solution:

Contact BEA Customer Support for the one-off patch to fix this problem.

9.0

9.2

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

Change Request Number	Description and Workaround or Solution	Found In	Fixed In
CR259784	On HP-UX, when an I/O operation on a file descriptor was cancelled, the socket was not getting properly cleaned and this caused a File Descriptor leak: this was leading to an OutofMemory exception. Workaround or Solution: Contact BEA Customer Support for the one-off patch to fix this problem.	9.0	9.2
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

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

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

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

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

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

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