Known and Resolved Issues

WebLogic Server Known and Resolved Issues

This document describes current known issues as well as issues that were known and are now resolved. For information about new and changed functionality in WebLogic Server 9.0, see What's New in WebLogic Server 9.0.

The following sections describe known and resolved issues in WebLogic Server:

Administration Console Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR043645

The Administration Console does not work properly if you make it the default Web application in a Managed Server environment.

Note: The Administration Console was redesigned and no longer exhibits this issue.

6.0

No Longer Applicable

CR063594

Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.

9.0 Beta

CR075845

Deploying an application requires multiple steps. With the exception of the start and stop operations, which can be invoked outside of an edit session, only a single deployment operation (install, upgrade, or delete) can be performed on a single deployment in an edit session.

Workaround:

Re-activate the edit session after each of these operations on each deployment.

7.0

Works As Designed

CR080476

You cannot specify a default Web application for a server from the Administration Console.

Note: The Administration Console was redesigned and no longer exhibits this issue.

8.1

No Longer Applicable

CR082949

When you use the FullSecurityDelegation setting, an empty `<auth-constraint>` or an unchecked method in a deployment descriptor does not delegate security to the Administration Console.

Note: The Administration Console was redesigned and no longer exhibits this issue.

7.0 SP1

No Longer Applicable

CR087951

The Administration Console does not create a new `ldift` file when you create a new security realm. If a new security realm is created and then set as the default security realm, the server may not reboot because there are no Admin accounts for the new security realm.

Note: The Administration Console was redesigned and no longer exhibits this issue.

7.0

No Longer Applicable

CR089480

Modifications to the Monitoring tables are not available.

Note: The Administration Console was redesigned and no longer exhibits this issue.

8.1

No Longer Applicable

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

CR190443

The initial start of the Administration Console on an individual server instance is slow.

9.0 Beta

9.0

CR194454

The DefaultWebAppContextRoot option for Web servers is not yet implemented.

9.0 Beta

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

CR200229

You can not change the order of security providers using the Administration Console.

9.0 Beta

9.0

CR200627

After a pageflow 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:

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

CR202076

Refreshing the page while using the Start/Stop option in the Web application assistant produces a page flow error.

9.0 Beta

9.0

CR202168

If you deploy an 8.1 Web Service, the Administration Console's deployment table displays the Web Application that the Web Service is packaged in and the Web Service.

If you click the Web Application name, the Administration Console displays Security Roles and Policies tabs. However, there are no Security Roles and Policies tabs for the Web Service itself.

Workaround:

Create a new Web Service for 9.0. The Roles and Policies tabs will be displayed for it in the Administration Console.

9.0

CR202364

On the Domain Logging page, if the limit of 100 logs is reached, additional logs are not visible.

9.0 Beta

CR202430

A predicate for a security policy cannot be edited through the Administration Console.

9.0 Beta

9.0

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

CR203422

A JMS Bridge destination requires a Connection Factory JNDI Name and a Destination JNDI Name. If the Destination JNDI Name field is not specified, all bridge destinations are considered one single physical destination, and the following message is displayed:

`"Caused by: weblogic.descriptor.DescriptorValidateException: The following failures occurred: -- Messaging Bridge "Bridge-2": source and target destinations cannot be the same physical destination.`"

9.0 Beta

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

CR204751

Starting or restarting a Web application does not appear in the Change List in the Change Center.

9.0 Beta

Works As Designed

CR204886

Currently, no more than 50 users or groups from an external LDAP server or database can be displayed in the Administration Console.

9.0 Beta

CR204887

Currently, you can not use wildcards in the Administration Console to restrict the search of users and groups.

9.0 Beta

9.0

CR207640

After adding 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

CR207995

When you upgrade a 7.x `config.xml` file with SSL enabled to this release of WebLogic Server, the Administration Console must be accessed over the non-secure port (for example, `http://localhost:7001`). If you try to use the secure port (for example, `http://localhost:7002`), errors are recorded in the server log; a page flow error occurs when accessing the home.jsp for the Administration Console; and the following message is displayed:

`server is currently making changes.`

9.0 Beta

9.0

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:

Thread dumps work on all Virtual Machines if you use the WebLogic Scripting Tool.

9.0

CR208141

The Administration Console can not be used to delete a certificate from the certificate registry.

9.0 Beta

9.0

CR208157

Using the Copy button when copying a registered certificate to a file causes an error message to be displayed in the Administration Console.

9.0 Beta

9.0

CR208168

The information displayed in the Change Center after a deployment action (install, start, stop, delete) is confusing.

9.0 Beta

9.0

CR208258

Applications deployed on a cluster do not appear in the list of deployments for each server belonging to the cluster in the Deployments tab for the Settings of the server.

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 RA 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 should display them all, but does not display the Resource Adapter bean JNDI name.

9.0

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

CR208683

The Deployment Plan and Dependencies pages are incomplete. As a result, you cannot view or edit bindables in a deployment plan through the Administration Console.

9.0 Beta

9.0

CR209073

JMS service migration does not work using the Administration Console.

Workaround:

A JMS server can be successfully migrated using the `weblogic.Admin` command-line utility. Otherwise, you can configure a migratable server in place of migrating a JMS server, as described in "Server Migration".

9.0 Beta

CR209110

The Administration Console sends log messages to the Administration Server log, but there is no way to filter the messages or use the log configuration pages to reconfigure Console logging.

Workaround:

Use `-Dlog4j.configuration=path-to-config`.

9.0

CR209139

JMS servers cannot be targeted to a migratable target server using the JMS Server -> Target & Deploy page of the Administration Console.

Workaround:

Create a persistent file store and target it to a migratable server.

Create a JMS server without selecting a persistent store, and target it to a non-migratable server.

Reopen the JMS server and modify it to use the persistent file store created in step 1.

Target the JMS Server to the same Migratable server that the persistent file store is targeted to.

9.0 Beta

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 results in losing all changes made.

9.0

CR213392

The ability to configure and monitor durable subscribers was available through the WebLogic Server 8.1 Administration Console, but is not currently available through the WebLogic Server 9.0 Administration Console.

9.0

CR215865

The Administration Console does not provide a way to set control security when custom roles and policies are set.

9.0 Beta

9.0

CR217569

The Administration Console presents JMS configuration values even if an Message-Driven Bean (MDB) is sourced by a resource adapter. The Administration Console does not provide a way to configure (read and/or write) the adapter-jndi-name for an RA-MDB.

9.0

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, but does not currently, provide a link to browse the messages queued for the subscriber. The New, Move and Delete operations should be, but are not currently, available for selected messages.

9.0

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:

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 of those 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:

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 may also be edited outside of the Administration Console environment by using an XML or text editor.

9.0

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:

Use WebLogic Scripting Tool (WLST) access the Jolt Runtime MBean.

9.0

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:

Manually redeploy the application.

9.0

CR231700

The Diagnostics/ Log Files pages in the Administration Console default to show only the last ten log file entries recorded in the last five minutes. These defaults may be changed by customizing the individual log tables to reflect your preferences.

If you do not set preferences and no entries have been recorded in the past five minutes, you may see empty tables because no log entries match this default filtering criteria.

Workaround:

Because log files can grow quite large, we limit the size of the log tables in the Administration Console viewer to the most recent 1000 entries that match the filtering criteria. Selecting "ALL" for the maximum results returned on the log table customization pages includes the most recent 1000 entries.

9.0

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:

Select and move one item at a time.

9.0

CR233421

The Web Services Description Language Compiler hangs when non-ascii characters are used in complexType.

9.0

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:

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

CR234112

When using 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:

Close all the browser windows and then re-open the browser.

9.0

CR234373

The Administration Console demands an Administration port for the Suspend and Force Suspend buttons, even though the suspend and force suspend operations do not strictly require it.

9.0

CR234411

When you create a security provider (any provider such as PKI credential mapper, auditing provider, authentication provider, etc.), 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. The provider-specific details must be entered for it to be a valid provider configuration.

Assistants should result in a complete configuration of a provider, but they currently do not.

9.0

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 is currently not configurable on the SMTP configuration page in the diagnostic module.

Upon SMTP notification, the mail body and subject are encoded in JVM default encoding. On Japanese Windows and UNIX, JVM default encoding is not mail-safe, which causes various problems such as character garbling, delivery failure, etc.

9.0

CR236585

Using the Administration Console search pain 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:

Switch the browser's locale to en-us.

9.0

Change Request Number	Description and Workaround	Found In	Fixed In
CR043645	The Administration Console does not work properly if you make it the default Web application in a Managed Server environment. Note: The Administration Console was redesigned and no longer exhibits this issue.	6.0	No Longer Applicable
CR063594	Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.	9.0 Beta
CR075845	Deploying an application requires multiple steps. With the exception of the start and stop operations, which can be invoked outside of an edit session, only a single deployment operation (install, upgrade, or delete) can be performed on a single deployment in an edit session. Workaround: Re-activate the edit session after each of these operations on each deployment.	7.0	Works As Designed
CR080476	You cannot specify a default Web application for a server from the Administration Console. Note: The Administration Console was redesigned and no longer exhibits this issue.	8.1	No Longer Applicable
CR082949	When you use the FullSecurityDelegation setting, an empty `<auth-constraint>` or an unchecked method in a deployment descriptor does not delegate security to the Administration Console. Note: The Administration Console was redesigned and no longer exhibits this issue.	7.0 SP1	No Longer Applicable
CR087951	The Administration Console does not create a new `ldift` file when you create a new security realm. If a new security realm is created and then set as the default security realm, the server may not reboot because there are no Admin accounts for the new security realm. Note: The Administration Console was redesigned and no longer exhibits this issue.	7.0	No Longer Applicable
CR089480	Modifications to the Monitoring tables are not available. Note: The Administration Console was redesigned and no longer exhibits this issue.	8.1	No Longer Applicable
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
CR190443	The initial start of the Administration Console on an individual server instance is slow.	9.0 Beta	9.0
CR194454	The DefaultWebAppContextRoot option for Web servers is not yet implemented.	9.0 Beta
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
CR200229	You can not change the order of security providers using the Administration Console.	9.0 Beta	9.0
CR200627	After a pageflow 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: 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
CR202076	Refreshing the page while using the Start/Stop option in the Web application assistant produces a page flow error.	9.0 Beta	9.0
CR202168	If you deploy an 8.1 Web Service, the Administration Console's deployment table displays the Web Application that the Web Service is packaged in and the Web Service. If you click the Web Application name, the Administration Console displays Security Roles and Policies tabs. However, there are no Security Roles and Policies tabs for the Web Service itself. Workaround: Create a new Web Service for 9.0. The Roles and Policies tabs will be displayed for it in the Administration Console.	9.0
CR202364	On the Domain Logging page, if the limit of 100 logs is reached, additional logs are not visible.	9.0 Beta
CR202430	A predicate for a security policy cannot be edited through the Administration Console.	9.0 Beta	9.0
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
CR203422	A JMS Bridge destination requires a Connection Factory JNDI Name and a Destination JNDI Name. If the Destination JNDI Name field is not specified, all bridge destinations are considered one single physical destination, and the following message is displayed: `"Caused by: weblogic.descriptor.DescriptorValidateException: The following failures occurred: -- Messaging Bridge "Bridge-2": source and target destinations cannot be the same physical destination.`"	9.0 Beta	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
CR204751	Starting or restarting a Web application does not appear in the Change List in the Change Center.	9.0 Beta	Works As Designed
CR204886	Currently, no more than 50 users or groups from an external LDAP server or database can be displayed in the Administration Console.	9.0 Beta
CR204887	Currently, you can not use wildcards in the Administration Console to restrict the search of users and groups.	9.0 Beta	9.0
CR207640	After adding 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
CR207995	When you upgrade a 7.x `config.xml` file with SSL enabled to this release of WebLogic Server, the Administration Console must be accessed over the non-secure port (for example, `http://localhost:7001`). If you try to use the secure port (for example, `http://localhost:7002`), errors are recorded in the server log; a page flow error occurs when accessing the home.jsp for the Administration Console; and the following message is displayed: `server is currently making changes.`	9.0 Beta	9.0
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: Thread dumps work on all Virtual Machines if you use the WebLogic Scripting Tool.	9.0
CR208141	The Administration Console can not be used to delete a certificate from the certificate registry.	9.0 Beta	9.0
CR208157	Using the Copy button when copying a registered certificate to a file causes an error message to be displayed in the Administration Console.	9.0 Beta	9.0
CR208168	The information displayed in the Change Center after a deployment action (install, start, stop, delete) is confusing.	9.0 Beta	9.0
CR208258	Applications deployed on a cluster do not appear in the list of deployments for each server belonging to the cluster in the Deployments tab for the Settings of the server.	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 RA 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 should display them all, but does not display the Resource Adapter bean JNDI name.	9.0
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
CR208683	The Deployment Plan and Dependencies pages are incomplete. As a result, you cannot view or edit bindables in a deployment plan through the Administration Console.	9.0 Beta	9.0
CR209073	JMS service migration does not work using the Administration Console. Workaround: A JMS server can be successfully migrated using the `weblogic.Admin` command-line utility. Otherwise, you can configure a migratable server in place of migrating a JMS server, as described in "Server Migration".	9.0 Beta
CR209110	The Administration Console sends log messages to the Administration Server log, but there is no way to filter the messages or use the log configuration pages to reconfigure Console logging. Workaround: Use `-Dlog4j.configuration=path-to-config`.	9.0
CR209139	JMS servers cannot be targeted to a migratable target server using the JMS Server -> Target & Deploy page of the Administration Console. Workaround: Create a persistent file store and target it to a migratable server. Create a JMS server without selecting a persistent store, and target it to a non-migratable server. Reopen the JMS server and modify it to use the persistent file store created in step 1. Target the JMS Server to the same Migratable server that the persistent file store is targeted to.	9.0 Beta
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 results in losing all changes made.	9.0
CR213392	The ability to configure and monitor durable subscribers was available through the WebLogic Server 8.1 Administration Console, but is not currently available through the WebLogic Server 9.0 Administration Console.	9.0
CR215865	The Administration Console does not provide a way to set control security when custom roles and policies are set.	9.0 Beta	9.0
CR217569	The Administration Console presents JMS configuration values even if an Message-Driven Bean (MDB) is sourced by a resource adapter. The Administration Console does not provide a way to configure (read and/or write) the adapter-jndi-name for an RA-MDB.	9.0
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, but does not currently, provide a link to browse the messages queued for the subscriber. The New, Move and Delete operations should be, but are not currently, available for selected messages.	9.0
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: 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 of those 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: 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 may also be edited outside of the Administration Console environment by using an XML or text editor.	9.0
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: Use WebLogic Scripting Tool (WLST) access the Jolt Runtime MBean.	9.0
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: Manually redeploy the application.	9.0
CR231700	The Diagnostics/ Log Files pages in the Administration Console default to show only the last ten log file entries recorded in the last five minutes. These defaults may be changed by customizing the individual log tables to reflect your preferences. If you do not set preferences and no entries have been recorded in the past five minutes, you may see empty tables because no log entries match this default filtering criteria. Workaround: Because log files can grow quite large, we limit the size of the log tables in the Administration Console viewer to the most recent 1000 entries that match the filtering criteria. Selecting "ALL" for the maximum results returned on the log table customization pages includes the most recent 1000 entries.	9.0
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: Select and move one item at a time.	9.0
CR233421	The Web Services Description Language Compiler hangs when non-ascii characters are used in complexType.	9.0
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: 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
CR234112	When using 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: Close all the browser windows and then re-open the browser.	9.0
CR234373	The Administration Console demands an Administration port for the Suspend and Force Suspend buttons, even though the suspend and force suspend operations do not strictly require it.	9.0
CR234411	When you create a security provider (any provider such as PKI credential mapper, auditing provider, authentication provider, etc.), 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. The provider-specific details must be entered for it to be a valid provider configuration. Assistants should result in a complete configuration of a provider, but they currently do not.	9.0
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 is currently not configurable on the SMTP configuration page in the diagnostic module. Upon SMTP notification, the mail body and subject are encoded in JVM default encoding. On Japanese Windows and UNIX, JVM default encoding is not mail-safe, which causes various problems such as character garbling, delivery failure, etc.	9.0
CR236585	Using the Administration Console search pain 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: Switch the browser's locale to en-us.	9.0

Apache Beehive Support Issues

Change Request Number

Description and Workaround

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:

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 the current 9.0 release 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

CR232509

The Beehive Web Service Control is not included in the version of Beehive shipped with Weblogic Workshop.

Workaround:

Use the Web Service Control included as part of WebLogic Server instead. For details and instructions, see the online documentation at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/service/navServiceControl.html.

9.0

CR233609

The version of Beehive shipped with WebLogic Server 9.0 does not include the Web Service metadata sub-project. Consequently, the Web Service metadata documentation has not been included and hyperlinks to the removed documentation content are broken.

9.0

CR234170

Weblogic 9.0 ships with Beehive v1m1. This is an upgrade of the Beehive v1m1 available from the Apache Web site. The following improvements were made:

Fixed Apache Beehive issue 829, "Controls deserialization broken because it's looking for the wrong delimiter." See http://issues.apache.org/jira/browse/BEEHIVE-829 for details.

Fixed Apache Beehive issue 834, "JDBC Control throws NPE after deserialization." See http://issues.apache.org/jira/browse/BEEHIVE-834 for details.

Weblogic 9.0 Beehive v1m1 ships with XMLBeans v2.

Changes were made to the JMS Control to fix some deserialization problems.

9.0 Beta

9.0

CR234997

The application.xml file contained in weblogic-beehive-1.0.ear causes errors when parsed with the Xerces XML parser.

The application.xml file contained in `BEA_HOME/weblogic90/common/deployable-libraries/weblogic-beehive-1.0.ear` has whitespaces before the xml declaration

`<?xml version=?1.0? encoding=?UTF-8??>`

Workaround:

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:

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	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: 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 the current 9.0 release 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
CR232509	The Beehive Web Service Control is not included in the version of Beehive shipped with Weblogic Workshop. Workaround: Use the Web Service Control included as part of WebLogic Server instead. For details and instructions, see the online documentation at http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/service/navServiceControl.html.	9.0
CR233609	The version of Beehive shipped with WebLogic Server 9.0 does not include the Web Service metadata sub-project. Consequently, the Web Service metadata documentation has not been included and hyperlinks to the removed documentation content are broken.	9.0
CR234170	Weblogic 9.0 ships with Beehive v1m1. This is an upgrade of the Beehive v1m1 available from the Apache Web site. The following improvements were made: Fixed Apache Beehive issue 829, "Controls deserialization broken because it's looking for the wrong delimiter." See http://issues.apache.org/jira/browse/BEEHIVE-829 for details. Fixed Apache Beehive issue 834, "JDBC Control throws NPE after deserialization." See http://issues.apache.org/jira/browse/BEEHIVE-834 for details. Weblogic 9.0 Beehive v1m1 ships with XMLBeans v2. Changes were made to the JMS Control to fix some deserialization problems.	9.0 Beta	9.0
CR234997	The application.xml file contained in weblogic-beehive-1.0.ear causes errors when parsed with the Xerces XML parser. The application.xml file contained in `BEA_HOME/weblogic90/common/deployable-libraries/weblogic-beehive-1.0.ear` has whitespaces before the xml declaration `<?xml version=?1.0? encoding=?UTF-8??>` Workaround: 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: 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 Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR200754

If a plan has overrides of non-configurable elements, WebLogic Server does not currently reject the elements or fail to parse them.

Workaround:

Use configurable elements which use these annotations:

@configurable

@dependency

@declaration

@dynamic

9.0

Change Request Number	Description and Workaround	Found In	Fixed In
CR200754	If a plan has overrides of non-configurable elements, WebLogic Server does not currently reject the elements or fail to parse them. Workaround: Use configurable elements which use these annotations: @configurable @dependency @declaration @dynamic	9.0

Core Server Issues

Change Request Number

Description and Workaround

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:

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

9.0

9.2

CR055352

WebLogic Server does not enforce unique names for configured components. It is possible to configure two different components of the same type that have the same name. The `ObjectName` associated with configured components must be unique. In order to ensure uniqueness, configuration MBeans that are of the same type and have the same parent must have unique names.

Workaround:

Use unique names for components you create. Consider adopting a naming convention for new components.

6.1 SP1

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

CR185847

Specifying a server start script used by Node Manager to start a server is supported only for the Java version of Node Manager, not the shell script version of Node Manager.

9.0 Beta

9.0

CR194490

The Upgrade Wizard does not complete the database configuration when upgrading singleton service migration to server migration.

Workaround:

Use the Administration Console to complete this configuration. See Server Migration.

9.0 Beta

CR205123

A native library (`terminalio`) prevents passwords typed on the command line from being echoed to the terminal. This is a requirement for production mode. In a few cases, WebLogic Server must prompt for a password before the production mode is known. In these cases, production mode is assumed to be enabled and the server will not boot if the `terminalio` native library is not available.

Workaround:

If you are on a platform that does not support `terminalio`, use the `-Dweblogic.management.allowPasswordEcho=true` option to start WebLogic Server.

9.0 Beta

9.0

CR205275

Changes to the configuration are protected by a lock based on the ID of the user that initiates the edit session. While one editor has the lock, other users are prevented from making modifications to the pending configuration. Because this lock is based on user ID, it is possible for two processes to modify the pending configuration at the same time if they are using the same user ID. Simultaneous edits with the same user ID is not recommended because it is extremely difficult to coordinate activities. A runtime exception occurs if two processes attempt to activate a pending configuration at the same time.

Workaround:

If possible, avoid having two processes with the same username access an Administration Server. Use weblogic.Admin (deprecated) rather than WLST. Alternatively, when you use WLST, use the `config` command rather than the `edit` command and avoid using the `startEdit`, `save`, or `activate` commands. These two alternatives serialize the configuration changes and avoid collisions between the changes.

9.0 Beta

9.0

CR206130

When you configure cross-cluster session replication, setting the Session Flush Interval and Session Flush Session attributes to very low values can cause poor performance when the cluster attempts to send the replication data to an unresponsive remote cluster.

9.0 Beta

9.0

CR206938

Large scale deployments on clusters with 10 or more nodes may cause out-of-memory errors.

9.0 Beta

9.0

CR208161

When running on Solaris, the Node Manager logger intermittently throws an `IOException: Bad file number`.

9.0 Beta

9.0

CR208240

The `RestartDelaySeconds` does not function correctly with the SSH version of Node Manager.

9.0 Beta

9.0

CR208661

Node Manager may not be able to find the `nodemanager.domains` file. To correct this, edit the `wlscontorl.sh` file and edit the definition of `DomainDir` to point to your domain directory.

9.0 Beta

9.0

CR208664

The value of the `Interface` variable in `wlscontrol.sh` is not set correctly. When you configure server migration, set the Interface variable in `wlscontrol.sh` to the name of the network interfaces on your machines. The Interface variable usually looks something like:

`'hme0'. Running 'ifconfig -a'`

9.0 Beta

9.0

CR208815

jCom has not been updated to the most recent version and has not been tested for this Beta release.

9.0 Beta

9.0

CR217067

The `Low Memory Granularity Level` attribute is disabled. WebLogic Server logs a warning message when the average free memory value is smaller than the `Low Memory GC Threshold` value.

9.0 Beta

CR227086

After you migrate a JTA service, changes to the HostingServer available from the JTAMigratableTarget do not appear in the Administration Console. Because the changes do not appear, it is not obvious whether the migration succeeded or failed.

9.0

CR227959

(HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis) < FencingGracePeriodMillis is enforced in the code.

Currently, the following equation determines the length of the lease: (HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis * 2) + FencingGracePeriodMillis

A server that crashes may not be restarted successfully by the NodeManager on the current machine because it thinks the lease is still active.

Workaround:

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 will be unable to access the Administration Console via the original port/protocol.

Workaround:

The only way to regain access to the Administration Console is to restart all of the servers.

9.0

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:

Retry a few times. The problem only seems to occur with a newly booted server.

9.0

Change Request Number	Description and Workaround	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: Contact BEA Customer Support for the one-off patch to fix this problem.	9.0	9.2
CR055352	WebLogic Server does not enforce unique names for configured components. It is possible to configure two different components of the same type that have the same name. The `ObjectName` associated with configured components must be unique. In order to ensure uniqueness, configuration MBeans that are of the same type and have the same parent must have unique names. Workaround: Use unique names for components you create. Consider adopting a naming convention for new components.	6.1 SP1
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
CR185847	Specifying a server start script used by Node Manager to start a server is supported only for the Java version of Node Manager, not the shell script version of Node Manager.	9.0 Beta	9.0
CR194490	The Upgrade Wizard does not complete the database configuration when upgrading singleton service migration to server migration. Workaround: Use the Administration Console to complete this configuration. See Server Migration.	9.0 Beta
CR205123	A native library (`terminalio`) prevents passwords typed on the command line from being echoed to the terminal. This is a requirement for production mode. In a few cases, WebLogic Server must prompt for a password before the production mode is known. In these cases, production mode is assumed to be enabled and the server will not boot if the `terminalio` native library is not available. Workaround: If you are on a platform that does not support `terminalio`, use the `-Dweblogic.management.allowPasswordEcho=true` option to start WebLogic Server.	9.0 Beta	9.0
CR205275	Changes to the configuration are protected by a lock based on the ID of the user that initiates the edit session. While one editor has the lock, other users are prevented from making modifications to the pending configuration. Because this lock is based on user ID, it is possible for two processes to modify the pending configuration at the same time if they are using the same user ID. Simultaneous edits with the same user ID is not recommended because it is extremely difficult to coordinate activities. A runtime exception occurs if two processes attempt to activate a pending configuration at the same time. Workaround: If possible, avoid having two processes with the same username access an Administration Server. Use weblogic.Admin (deprecated) rather than WLST. Alternatively, when you use WLST, use the `config` command rather than the `edit` command and avoid using the `startEdit`, `save`, or `activate` commands. These two alternatives serialize the configuration changes and avoid collisions between the changes.	9.0 Beta	9.0
CR206130	When you configure cross-cluster session replication, setting the Session Flush Interval and Session Flush Session attributes to very low values can cause poor performance when the cluster attempts to send the replication data to an unresponsive remote cluster.	9.0 Beta	9.0
CR206938	Large scale deployments on clusters with 10 or more nodes may cause out-of-memory errors.	9.0 Beta	9.0
CR208161	When running on Solaris, the Node Manager logger intermittently throws an `IOException: Bad file number`.	9.0 Beta	9.0
CR208240	The `RestartDelaySeconds` does not function correctly with the SSH version of Node Manager.	9.0 Beta	9.0
CR208661	Node Manager may not be able to find the `nodemanager.domains` file. To correct this, edit the `wlscontorl.sh` file and edit the definition of `DomainDir` to point to your domain directory.	9.0 Beta	9.0
CR208664	The value of the `Interface` variable in `wlscontrol.sh` is not set correctly. When you configure server migration, set the Interface variable in `wlscontrol.sh` to the name of the network interfaces on your machines. The Interface variable usually looks something like: `'hme0'. Running 'ifconfig -a'`	9.0 Beta	9.0
CR208815	jCom has not been updated to the most recent version and has not been tested for this Beta release.	9.0 Beta	9.0
CR217067	The `Low Memory Granularity Level` attribute is disabled. WebLogic Server logs a warning message when the average free memory value is smaller than the `Low Memory GC Threshold` value.	9.0 Beta
CR227086	After you migrate a JTA service, changes to the HostingServer available from the JTAMigratableTarget do not appear in the Administration Console. Because the changes do not appear, it is not obvious whether the migration succeeded or failed.	9.0
CR227959	(HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis) < FencingGracePeriodMillis is enforced in the code. Currently, the following equation determines the length of the lease: (HealthCheckPeriodsUntilFencing * HealthCheckIntervalMillis * 2) + FencingGracePeriodMillis A server that crashes may not be restarted successfully by the NodeManager on the current machine because it thinks the lease is still active. Workaround: 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 will be unable to access the Administration Console via the original port/protocol. Workaround: The only way to regain access to the Administration Console is to restart all of the servers.	9.0
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: Retry a few times. The problem only seems to occur with a newly booted server.	9.0

Deployment Issues

Change Request Number

Description and Workaround

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

CR085298

If you distribute an application to one or more Managed Servers that are unavailable (for example, because they are shut down or temporarily disconnected from the Administration Server), and the Administration Server is restarted, the unavailable server instances do not receive the distribute request when they become available. This problem does not occur with deployment, undeployment, or redeployment requests.

7.0

9.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:

Reboot the partitioned servers after they rejoin the cluster.

8.1

CR100540

ComponentMBean names generated during deployment are inconsistent between modules within an Enterprise application and stand-alone modules. Modules within an Enterprise applications receive a component name with a full file extension, while stand-alone modules receive a component name without a file extension.

For example, if you deploy an Enterprise application containing an EJB named `ejb.jar`, the component is named "ejb.jar" and you can refer to the component using "ejb.jar" in subsequent deployment commands. However, if you deploy a stand-alone EJB named `ejb.jar`, the component is named "ejb" and you must use "ejb" to refer to that component in subsequent deployment commands.

7.0 SP1

CR136717

This release of `weblogic.Deployer` does not support the `-sourcerootforupload` option. (This option enables you to specify a remote root directory or archive file to upload to the Administration Server upload directory for redeployment operations.)

8.1

9.0

CR177695

The deployment API does not provide an implementation for the JSR-88 `TargetModuleID.getWebUrl()` method. `getWebUrl()` always returns null.

9.0 Beta

9.0

CR179465 CR191650 CR202600

A call to the JSR-88 `DeploymentManager.getRunningModules()` method returns a list of all configured modules, rather than just those modules that are currently active. Because of this problem, the Administration Console may show deployed modules as "Running" when in fact they were not successfully deployed.

9.0 Beta

9.0

CR203630

When you use the Administration Console to deploy multiple applications within a single change list, clicking Activate Changes deploys only the first application installed. The remaining applications are listed as "Distribute Initializing."

Workaround:

To deploy the remaining applications, select the application names on the Deployments page and use the Start/Restart button.

9.0 Beta

9.0

CR207565

The Builder and DDInit utilities, used to generate deployment descriptors, are not provided in this release.

9.0 Beta

9.0

CR208271

If a configuration change is made to a DTD-based application, the change is persisted to the deployment plan, as it is for schema-based applications. However, the application does not pick up the new values from the deployment plan, either dynamically after a reboot of the server, or after a redeploy of the application. The Administration Console displays a message after a configuration save to indicate to the user that the persisted changes will not be used for DTD-based applications.

The example applications installed in this Beta release use older, DTD-based WebLogic Server deployment descriptors. Configuring Applications for Production Deployment in Deploying Applications to WebLogic Server provides a link to an updated sample application that uses newer schema-based deployment descriptors, and that can be configured using a deployment plan.

The Single Threaded Servlet Pool Size option on the Web Application configuration page in the Administration Console is deprecated and will be removed for the GA of this release. Currently, changing this option in the Administration Console has no effect on the Web application whether it is DTD or schema-based.

9.0 Beta

9.0

CR222004

When deploying only one module of an application, WebLogic Server deploys 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 is accessible through all of the available servers.

9.0

CR223700

Using a common working directory in a Web application that is deployed on a cluster may result in corrupted or locked files.

Workaround:

Remove the working directory when deploying on a cluster.

9.0

CR225655

For applications that have the Web Services module, WebLogic Server currently does not support side-by-side application deployment, which allows for the reliable introduction of new application functionality without disrupting the existing traffic to the deployed application.

9.0.1

CR225867

If you try to deploy an application that references a missing library, the application will not start.

9.0

CR227707

WebLogic Server does not detect the removal of application files when the server is not active, which may result in the domain tree not being in sync.

Workaround:

Remove the autodeploy application while the server is in an active state.

9.0

CR228435

If you pin an application to a particular server in a cluster and then deploy or redeploy that application to the cluster, the original target is left in the target list. Future attempts to undeploy the application from that single server will fail with an exception stating that the server cannot undeploy an application from a subset of the cluster.

Workaround:

Use the Administration Console to remove the target.

9.0

CR231313

When a plan is used to update a descriptor, the updated in-memory descriptor is not validated against any schema.

9.0

CR231498

When deploying some services via an ant target, the XBus cluster DRT (part of remote.all) may fail on remote machines and throw the following error:

The domain edit lock is owned by another session in exclusive mode in XBus cluster DRTs.

9.0

CR231543

When deploying an application in a multi-machine environment, remote Managed Servers that are not targeted or do not belong to a cluster where some or all of the servers are targeted may get the following error message in the Managed Server logs:

`Failed to create App/Comp mbeans for AppDeploymentMBean <application name>. Error - weblogic.management.DeploymentException: No such file or directory with : <application path>.`

Despite the above exception in the Managed Server logs, no adverse affect or incorrect behavior will occur because the Compatibility MBeans are not needed on these servers.

9.0

CR231643

Killing the deploy command causes the activate operation to stay in preparing state for one hour.

If you start a deployment operation via 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:

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

Change Request Number	Description and Workaround	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
CR085298	If you distribute an application to one or more Managed Servers that are unavailable (for example, because they are shut down or temporarily disconnected from the Administration Server), and the Administration Server is restarted, the unavailable server instances do not receive the distribute request when they become available. This problem does not occur with deployment, undeployment, or redeployment requests.	7.0	9.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: Reboot the partitioned servers after they rejoin the cluster.	8.1
CR100540	ComponentMBean names generated during deployment are inconsistent between modules within an Enterprise application and stand-alone modules. Modules within an Enterprise applications receive a component name with a full file extension, while stand-alone modules receive a component name without a file extension. For example, if you deploy an Enterprise application containing an EJB named `ejb.jar`, the component is named "ejb.jar" and you can refer to the component using "ejb.jar" in subsequent deployment commands. However, if you deploy a stand-alone EJB named `ejb.jar`, the component is named "ejb" and you must use "ejb" to refer to that component in subsequent deployment commands.	7.0 SP1
CR136717	This release of `weblogic.Deployer` does not support the `-sourcerootforupload` option. (This option enables you to specify a remote root directory or archive file to upload to the Administration Server upload directory for redeployment operations.)	8.1	9.0
CR177695	The deployment API does not provide an implementation for the JSR-88 `TargetModuleID.getWebUrl()` method. `getWebUrl()` always returns null.	9.0 Beta	9.0
CR179465 CR191650 CR202600	A call to the JSR-88 `DeploymentManager.getRunningModules()` method returns a list of all configured modules, rather than just those modules that are currently active. Because of this problem, the Administration Console may show deployed modules as "Running" when in fact they were not successfully deployed.	9.0 Beta	9.0
CR203630	When you use the Administration Console to deploy multiple applications within a single change list, clicking Activate Changes deploys only the first application installed. The remaining applications are listed as "Distribute Initializing." Workaround: To deploy the remaining applications, select the application names on the Deployments page and use the Start/Restart button.	9.0 Beta	9.0
CR207565	The Builder and DDInit utilities, used to generate deployment descriptors, are not provided in this release.	9.0 Beta	9.0
CR208271	If a configuration change is made to a DTD-based application, the change is persisted to the deployment plan, as it is for schema-based applications. However, the application does not pick up the new values from the deployment plan, either dynamically after a reboot of the server, or after a redeploy of the application. The Administration Console displays a message after a configuration save to indicate to the user that the persisted changes will not be used for DTD-based applications. The example applications installed in this Beta release use older, DTD-based WebLogic Server deployment descriptors. Configuring Applications for Production Deployment in Deploying Applications to WebLogic Server provides a link to an updated sample application that uses newer schema-based deployment descriptors, and that can be configured using a deployment plan. The Single Threaded Servlet Pool Size option on the Web Application configuration page in the Administration Console is deprecated and will be removed for the GA of this release. Currently, changing this option in the Administration Console has no effect on the Web application whether it is DTD or schema-based.	9.0 Beta	9.0
CR222004	When deploying only one module of an application, WebLogic Server deploys 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 is accessible through all of the available servers.	9.0
CR223700	Using a common working directory in a Web application that is deployed on a cluster may result in corrupted or locked files. Workaround: Remove the working directory when deploying on a cluster.	9.0
CR225655	For applications that have the Web Services module, WebLogic Server currently does not support side-by-side application deployment, which allows for the reliable introduction of new application functionality without disrupting the existing traffic to the deployed application.	9.0.1
CR225867	If you try to deploy an application that references a missing library, the application will not start.	9.0
CR227707	WebLogic Server does not detect the removal of application files when the server is not active, which may result in the domain tree not being in sync. Workaround: Remove the autodeploy application while the server is in an active state.	9.0
CR228435	If you pin an application to a particular server in a cluster and then deploy or redeploy that application to the cluster, the original target is left in the target list. Future attempts to undeploy the application from that single server will fail with an exception stating that the server cannot undeploy an application from a subset of the cluster. Workaround: Use the Administration Console to remove the target.	9.0
CR231313	When a plan is used to update a descriptor, the updated in-memory descriptor is not validated against any schema.	9.0
CR231498	When deploying some services via an ant target, the XBus cluster DRT (part of remote.all) may fail on remote machines and throw the following error: The domain edit lock is owned by another session in exclusive mode in XBus cluster DRTs.	9.0
CR231543	When deploying an application in a multi-machine environment, remote Managed Servers that are not targeted or do not belong to a cluster where some or all of the servers are targeted may get the following error message in the Managed Server logs: `Failed to create App/Comp mbeans for AppDeploymentMBean <application name>. Error - weblogic.management.DeploymentException: No such file or directory with : <application path>.` Despite the above exception in the Managed Server logs, no adverse affect or incorrect behavior will occur because the Compatibility MBeans are not needed on these servers.	9.0
CR231643	Killing the deploy command causes the activate operation to stay in preparing state for one hour. If you start a deployment operation via 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: 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

Diagnostics Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR206872

Use of the DiagnosticContext in conjunction with JMS may cause a `java.lang.UnsupportedOperation` exception. This exception is most likely to occur if you are using the Dye Injection monitor with JMS monitors from the Diagnostic Monitor library.

9.0 Beta

9.0

CR209086

If an application contains diagnostic information defined in the `weblogic-diagnostics.xml` descriptor, the weblogic.Configure tool may fail with the following message:

`Failed to parse descriptor at META-INF/weblogic-diagnostics.xml for module`

Workaround:

Specify the CLASSPATH on the weblogic.Configure command line. For example:

`java -classpath "%CLASSPATH%; %BEA_HOME%\weblogic90b\server\lib" \ -plan plan.xml-type ear app.ear`

When you deploy the application using the weblogic.Configure tool, the diagnostics information is modified during the initial deployment. However, subsequent updates to the plan do not take effect.

9.0 Beta

9.0

CR209137

Currently, dynamic updates to application-level diagnostic information in deployment plans do not work.

Workaround:

To modify the configured diagnostic information, edit the `weblogic-diagnostics.xml` descriptor in the application or deployment plan and redeploy the application.

9.0 Beta

9.0

Change Request Number	Description and Workaround	Found In	Fixed In
CR206872	Use of the DiagnosticContext in conjunction with JMS may cause a `java.lang.UnsupportedOperation` exception. This exception is most likely to occur if you are using the Dye Injection monitor with JMS monitors from the Diagnostic Monitor library.	9.0 Beta	9.0
CR209086	If an application contains diagnostic information defined in the `weblogic-diagnostics.xml` descriptor, the weblogic.Configure tool may fail with the following message: `Failed to parse descriptor at META-INF/weblogic-diagnostics.xml for module` Workaround: Specify the CLASSPATH on the weblogic.Configure command line. For example: `java -classpath "%CLASSPATH%; %BEA_HOME%\weblogic90b\server\lib" \ -plan plan.xml-type ear app.ear` When you deploy the application using the weblogic.Configure tool, the diagnostics information is modified during the initial deployment. However, subsequent updates to the plan do not take effect.	9.0 Beta	9.0
CR209137	Currently, dynamic updates to application-level diagnostic information in deployment plans do not work. Workaround: To modify the configured diagnostic information, edit the `weblogic-diagnostics.xml` descriptor in the application or deployment plan and redeploy the application.	9.0 Beta	9.0

Documentation Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR196210

Previous versions of WebLogic Server documentation describe `weblogic.management.Admin.getInstance().getAdminMBeanHome()` as a means of looking up the MBeanHome interface on the Administration Server. However, the `weblogic.management.Admin` class is not public.

Workaround:

Instead of using this non-public class, use JNDI to retrieve MBeanHome. See Determining the Active Domain and Servers in Programming WebLogic Server JMX Services.

9.0 Beta

9.0

Change Request Number	Description and Workaround	Found In	Fixed In
CR196210	Previous versions of WebLogic Server documentation describe `weblogic.management.Admin.getInstance().getAdminMBeanHome()` as a means of looking up the MBeanHome interface on the Administration Server. However, the `weblogic.management.Admin` class is not public. Workaround: Instead of using this non-public class, use JNDI to retrieve MBeanHome. See Determining the Active Domain and Servers in Programming WebLogic Server JMX Services.	9.0 Beta	9.0

EJB Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR202400 CR203119

Using EJBGen to generate XML Schema Definition-based (XSD) deployment descriptors is not supported in the Beta release; you can use EJBGen to generate Document Type Definition-based (DTD) deployment descriptors only.

Workaround:

Use DDConverter to convert your DTD-based descriptors to XSD-based deployment descriptors, and then, as necessary, manually edit or create descriptors in the deployment descriptor files. You can use an XML editor to edit deployment descriptor files.

9.0 Beta

9.0

CR207543

When you deploy to a cluster an application that contains many EJBs, the following error occasionally occurs:

`# An unexpected error has been detected by HotSpot Virtual Machine:`

`#`

`# SIGSEGV (0xb) at pc=0xfec6a454, pid=16651, tid=27`

`#`

`# Java VM: Java HotSpot(TM) Server VM (1.5.0-b64 mixed mode)`

`# Problematic frame:`

`# V [libjvm.so+0x46a454]`

`...`

Workaround:

Create multiple applications that each contain fewer EJBs instead of one application that contains all of the EJBs.

9.0 Beta

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.>`

Work around:

Ignore the message; it has no effect on the applications.

9.0

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

CR227246

The remote-client-timeout parameter was added as an 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 currently not available for EJBGen.

9.0

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

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

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:

Fix the problem that causes the `WorkRejectedException`, or use WebLogic Server 8.1-style execute queues in WebLogic Server 9.0.

9.0

Change Request Number	Description and Workaround	Found In	Fixed In
CR202400 CR203119	Using EJBGen to generate XML Schema Definition-based (XSD) deployment descriptors is not supported in the Beta release; you can use EJBGen to generate Document Type Definition-based (DTD) deployment descriptors only. Workaround: Use DDConverter to convert your DTD-based descriptors to XSD-based deployment descriptors, and then, as necessary, manually edit or create descriptors in the deployment descriptor files. You can use an XML editor to edit deployment descriptor files.	9.0 Beta	9.0
CR207543	When you deploy to a cluster an application that contains many EJBs, the following error occasionally occurs: `# An unexpected error has been detected by HotSpot Virtual Machine:` `#` `# SIGSEGV (0xb) at pc=0xfec6a454, pid=16651, tid=27` `#` `# Java VM: Java HotSpot(TM) Server VM (1.5.0-b64 mixed mode)` `# Problematic frame:` `# V [libjvm.so+0x46a454]` `...` Workaround: Create multiple applications that each contain fewer EJBs instead of one application that contains all of the EJBs.	9.0 Beta
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.>` Work around: Ignore the message; it has no effect on the applications.	9.0
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
CR227246	The remote-client-timeout parameter was added as an 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 currently not available for EJBGen.	9.0
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
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
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: Fix the problem that causes the `WorkRejectedException`, or use WebLogic Server 8.1-style execute queues in WebLogic Server 9.0.	9.0

Examples Issues

Change Request Number

Description and Workaround

Found In

Fixed In

CR191354

Medical Records does not yet use deployment plans.

9.0 Beta

CR200319

Examples descriptor definitions need to be updated from version 8.1 and J2EE 1.3 to version 9.0 and J2EE 1.4.

9.0 Beta

9.0

CR208963

README.TXT instructs you to run setup\config to build the domain. This is no longer necessary because the Medical Records domain template does that.

Change Request Number	Description and Workaround	Found In	Fixed In
CR191354	Medical Records does not yet use deployment plans.	9.0 Beta
CR200319	Examples descriptor definitions need to be updated from version 8.1 and J2EE 1.3 to version 9.0 and J2EE 1.4.	9.0 Beta	9.0
CR208963	README.TXT instructs you to run setup\config to build the domain. This is no longer necessary because the Medical Records domain template does that.