WebLogic Server Known and Resolved Issues

The following sections describe known problems in WebLogic Server 9.2 and later Maintenance Packs, as well as problems that were resolved in 9.2 and subsequent Maintenance Packs. 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.

Change Request Number

Description and Workaround or Solution

Found In

Fixed In

When importing security data that was exported using releases of WebLogic Server prior to 9.2, BEA recommends:

If the default formats for providers in the exporting and importing security realm are exactly the same, there should be no problems
If the default formats for the providers in the exporting and importing security realms are different, the original security realm should be upgraded to WebLogic Server 9.2, the security data should be exported, and then imported into the 9.2 security realm.

If the older domain can not be upgraded, the original domain should be booted and instead of using the Export feature in the realm, use the Migration > Export tab for each provider and export the security data into a file. To import the security data into a provider in a new security realm, use the Migration > Import tab for each provider.

CR063594

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

9.0 Beta

CR089385

The Start, Shutdown, ForceShutown, and Restart operations for JDBC connection pools were missing from the Administration Console.

Workaround or Solution:

These operations have been added to the Administration Console.

8.1

9.2

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

9.2

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

9.2

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

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

9.2

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

9.2

CR206925

Deployment to one target server in a cluster deployed an application to all servers in the cluster. The Javascript that selected the appropriate user selection computed the incorrect HTML element representing the cluster.

This problem has been resolved.

9.0

9.2

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.

This problem has been resolved.

9.0

9.2

CR208258

Applications deployed on a cluster did not appear in the list of deployments for each server in the Deployments tab.

This problem has been resolved.

9.0

9.2

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 that is passed to the resource adapter during deployment.

The Administration Console does not 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.

This problem is resolved.

9.0

9.2

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

9.2

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

9.2

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

9.2

CR214481

Specifying Jakarta Commons Logging in the system classpath prevents the Administration Console from initializing.

The problem occurred when a user specified a class in the system classpath that was already used by the Administration Console. The classloader could load versions of the classes that were potentially incompatible. Specifically, the version of Struts used internally by the Administration Console was certified with a particular version of Log4j and Commons logging. However, when a newer version of Commons logging was specified in the classpath, the Administration Console failed to initialize because Struts failed to initialize classes needed by the Administration Console.

Workaround or Solution:

The resolution was to use a Filtering classloader. A Filtering classloader allows applications to be configured to use the application classloader over the system classpath for configured Java packages. These packages are:

org.apache.log4.*
org.apache.commons.*
org.apache.beehive.*
org.apache.struts.*
org.apache.oro.*
org.apache.taglibs.*

9.0

9.2

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.

This problem has been resolved.

9.0

9.2

CR223643

If you uploaded a non-ascii name application in the Administration Console, the file name appeared garbled.

This problem has been resolved.

9.0

9.2

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

9.2

CR226301

The Deployment Plan tab in the Administration Console was missing for stand-alone module deployments. Therefore, the user could not make changes to the deployment plan or the descriptors of the standalone resource adapter.

This problem has been resolved.

9.0

9.2

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

9.2

CR230275

The following attributes are 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

9.2

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

9.2

CR233719

If you register custom MBeans in a WebLogic Server MBean server, you can use roles and policies along with the WebLogic Security Service to protect your MBeans. Note the following restrictions:

Your MBean's object name must include a "Type=value" key property.
You must describe your roles and policies in an XACML 2.0 document and then use the WebLogic Scripting Tool to add the data to your realm.
If your XACML document describes authorization policies, your security realm must use either the WebLogic Server XACML Authorization Provider or another provider that implements the weblogic.management.security.authorization. PolicyStoreMBean interface.
If your XACML document describes role assignments, your security realm must use either the WebLogic Server XACML Role Mapping Provider or another provider that implements the weblogic.management.security.authorization. PolicyStoreMBean interface.

9.1

9.2

CR233862

If an installed JDBC module has a password-encrypted field encrypted with the wrong key, an exception occurs in the Administration Console.

This exception 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

9.2

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

9.2

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 you use the MedRec Administration Console.

Workaround or Solution:

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

9.0

9.2

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, which shows 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

9.2

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 the creation of a new user for that authentication provider until the configuration change is complete, which typically requires a server re-boot.

9.0

9.2

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

9.2

CR238625

Web Services deployed in a Web library module did not show up in the WebLogic Server Administration Console. The problem was caused by the way in which the Administration Console attempted to look-up library modules. In some circumstances, the library module deployments did not appear.

Workaround or Solution:

The code that queried for library modules was updated and modifications were made to the Targetting tabs in the Administration Console in an effort to consolidate targetting functions.

Note:

Although the Administration Console problem has been resolved, other problems related to merged descriptors still exist.

9.0

9.2

CR240006

The Chooser control in the Administration Console was not disabled in Mozilla if an Edit lock was not acquired. Some Web browsers do not treat the Disabled attribute in the same manner as Internet Explorer does.

Workaround or Solution:

The resolution was implemented in two parts:

Javascript is not emitted when the Edit lock is held by a Chooser control that needs to participate in single change. This change prevents items from being selected.
Items are explicitly greyed out when the Edit lock is not held for a Chooser that needs to participate in single change. This gives the intended appearance and behavior as in Internet Explorer, even though Internet Explorer is still using the “disabled” attribute. Also, no scrollbars are shown when the control is disabled for all browsers.

9.1

9.2

CR241794

The Administration Console did a -redeploy instead of an -update of an application regardless of whether dynamic property changes are supported or not. This means, for example, that changes to dynamic properties in resource adapters result in a full redeploy of the resource adapter/application instead of simply an update.

Workaround or Solution:

The resolution was implemented in two parts:

The redeploy action is no longer called on the Save action. Instead, the user now has the choice of explicitly invoking an update instead of redeploy for changes that are dynamic and redeploy for non-dynamic changes.
Icons have been added to the Administration Console. These icons indicate whether changing the value of an attribute requires a redeploy of the application.

Note:

The first time a configuration change is saved, a redeploy action is initiated. This redeploy is required to associate the deployment plan initially with the deployment in question. But subsequent changes follow the preceding rules.

9.0

9.2

CR247865

The deletion and recreation of a JDBC Data Source in the same edit session results in an exception, “Bean already exists.”

Workaround or Solution:

The configuration code was modified to handle deleted system resource files

9.1

9.2

CR248627

The Administration Console does not provide an option for displaying SAF Agent Log files.

Workaround or Solution:

This feature has been added to the Administration Console.

9.1

9.2

CR254085

The Administration Console does not honor the value specified for the Retire Timeout Text field when updating applications that have the version as Weblogic-Application-Version in the MANIFEST.MF file. In addition, the label for the Retire Timeout Text field is showing that the time specified is in minutes but it is actually honoring the retire timeout in seconds.

Workaround or Solution:

The label for the Retire Timeout Text field has been changed from Retire Timeout (minutes) to Retire Timeout (seconds.

Now the Administration Console honors Retire Timeout in seconds when updating applications that have the version as Weblogic-Application-Version in the MANIFEST.MF file.

9.0

9.2

CR255161

When the Administration Console is used to export a security realm's data to a directory and then import that data into another security realm, the two security realms need to have the exact same set of security providers (same type and same name).

If the second realm has a provider with the same name but a different default import format, the Administration Console should prevent the import. Instead, the Administration Console exported the data using the default format of the first provider and then imported the data using the default format of the second provider. For example, if the first security realm has a provider of type DefaultAuthorizer named DefaultAuthorizer, the Administration Console exported the data in the DefaultAtz format. If the second realm has a provider of type XAXMLAuthorizer named DefaultAuthorizer, the Administration Console imported the data in the XACML format. In this case, the XACMLAuthorizer silently dropped the data instead of reporting an error.

Workaround or Solution:

The Administration Console now records the format of the exported data and imports the data using those formats. Also, the Administration Console reports whether or not a provider has successfully imported the data.

When exporting and importing security data with WebLogic Server 9.2, the Administration Console prevents importing data from a security realm whose security providers support different formats.

If data is exported from a security realm created with a release prior to WebLogic Server 9.2 and then imported into a 9.2 domain, the formats from the original provider are not available and the Administration Console will try to import the data using the default format of the security providers in the new security realm. Security data can be dropped if the new security provider does not report an error stating it can't import the data using its default format.

9.1

9.2

CR255210

The Administration Console could not be used to configure security on Web Service callback methods.

This feature is now available in the Administration Console.

Note:

This feature only applies to callback methods on POJO-JWS and not EJB-JWS.

9.2

CR255481

If a security-enabled Web Service is invoked with an invalid username and password, the client does not get the expected 403 forbidden error. A 500 internal error occurs.

9.2

CR255582

If a security role or security policy definition has three or more conditions and the first condition is removed, the action fails with an exception. Similarly, if a security role or security policy definition has three or more conditions and all of them are removed, the action fails with an exception.

Workaround or Solution:

If you want to remove only the first condition, move the second condition up to the first position, and then remove the original first condition.

Similarly, if you want to remove all the conditions, remove all the conditions except for the first condition, then move the first condition last.

For example:

Go to a new domain
Select the Security->Policies tab.
Select the View Log tab.

Initially, the security policy is: Role Admin, Role Deployer, Role Operator, or Role Monitor.

If you want to remove only the Admin role, select Deployer and move it to the first position in the list on the View Log tab, select Admin, and click Remove.

If you want to remove all the conditions, select the Deployer, Operator, and Monitor roles, and click Remove. Then select Admin and click Remove.

9.1

9.2

CR256665

The 9.1 version of the Administration Console could not be used to create JMS messages for a queue because the Assistant page was read-only.

This problem has been resolved.

9.1

9.2

CR258855

The Administration Console does not support a way to define a log-watch-severity element. The Watch Notification configuration page does not include form fields for configuring the Enabled, Severity, and Log Watch Severity attributes of the Watch notification.

Workaround or Solution:

These features have been added to the Administration Console.

9.0

9.2

CR262410

When cloning a server using WebLogic Server 9.1, the custom keystore and SSL settings were not cloned.

This problem has been resolved.

9.1

9.2

CR269658

If a user of Weblogic Server 9.1 used the Administration Console to change the domain's user lockout security policy (on the Domain->Security->Policies-> User Lockout tab), the new security policy was ignored and the previous security policy (which defaults to the Admin security role) was used instead.

Workaround or Solution:

The Administration Console in WebLogic Server 9.2 correctly sets the domain's user lockout security policy. However, if the domain’s user lockout security policy was changed using WebLogic Server 9.1 and the domain was then upgraded to WebLogic Server 9.2, the domain will still use the previous user lockout security policy (which defaults to the Admin security role).

9.1

9.2

CR271405

When using the Administration Console in WebLogic Server 9.1, Managed Servers do not start and do not show up in the Administration Console after modifying the Root directory in server start.

This problem has been resolved.

9.1

9.2

CR273824

In previous releases of WebLogic Server, the Administration Console could not be used to expose or hide WSDL.

Workaround or Solution:

A new checkbox was added to the Web Service Configuration page, which allows the user to expose or hide the WSDL.

9.2

CR278615

SNMP trap data sent out by WebLogic Server Traps used to carry the local loopback address (127.0.0.1) of the SNMP agent machine, that is, the administration server machine - instead of its actual network IP address.

This problem has been resolved.

9.1

9.2 MP1

CR279620

Two distinct MIB Entries (safAgentRuntimeTable and safRemoteEndpointRuntimeTable) had the same OID in the MIB.

This problem has been resolved. Each entry now has a unique OID.

9.1

9.2 MP1

CR284857

In the Administration Console Online Help, the Search button always returns “0 documents found.”

Workaround or Solution:

Search the Administration Console Online Help that is published at


http://edocs.bea.com/wls/docs92/ConsoleHelp/

Enter your search query in the text box that is in the upper right corner of the document. To search for text that appears only in the Online Help, include the following string with your query: docs92/ConsoleHelp

For example, the following query finds all instances of “SNMP” in the Administration Console Online Help:

SNMP docs92/ConsoleHelp

9.2

CR284894

In the Administration Console Online Help, links to other WebLogic Server documents point to http://docs-stage/wls/docs92/, which is the wrong URL root.

Workaround or Solution:

After you click on a link to a WebLogic Server document, in your Web browser’s address field, change docs-stage to edocs.bea.com. For example, the following is the correct URL for the ServerMBean entry in the WebLogic Server MBean Reference:

http://edocs.bea.com/wls/docs92/wlsmbeanref/mbeans/ServerStartMBean.html

9.2

CR289950

In WebLogic Server Administration Console, if incorrect input was entered in the Edit Arguments page, the console displayed a Back button; when the Back button was clicked, a ServletException was raised.

This problem has been resolved. When the Back button is clicked, the Edit Arguments page is displayed, with the content that existed earlier.

9.2

9.2 MP1

CR290714

WebLogic Server Administration Console raises a ConcurrentModification exception when accessing a users list or a groups list, if there are too many matches of users or groups for the specified filter.

This problem has been resolved.

9.2

9.2 MP1

CR291050

WebLogic Server fails to reboot whenever an HTTP logging configuration for the server or the virtual host is changed using WebLogic Server Administration Console.

This problem has been resolved.

9.0

9.2 MP1

CR296087

When a new deployment plan was created or an existing deployment plan was updated for a deployed application through WebLogic Server Administration Console, the system did not provide users any information on how to bring that deployment plan into effect.

This problem has been resolved.

9.2

9.2 MP1

CR298767

The default Accept Backlog is set to 50. This may be insufficient for high-throughput applications.

Workaround

To increase the value of Accept Backlog, follow the instructions provided in http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/tuning/TuneConnectionBacklogBuffering.html

9.2

9.2 MP1

CR300839

WebLogic Server Administration Console does not display custom WS-Policy files (located in the .war under WEB-INF/policies) in the Available Endpoint Policies, Inbound Message Policies, and Outbound Message Policies list boxes.

This problem has been resolved.

9.2

9.2 MP1

CR304739

Links to “Read the documentation” and “Common Administration Task Descriptions” in the WebLogic Server 9.2 Administration console were taking users to WebLogic Server 9.1 documents.

This problem has been resolved.

9.2

9.2 MP1

CR282007

Administration Console used to fail to deploy Apache Maven-based applications, which have the following manifest, as normal applications and deployed them as libraries:

Manifest-Version: 1.0

Archiver-Version: Plexus Archiver

Created-By: Apache Maven

Built-By: xxxx

Build-Jdk: 1.5.0_06

Extension-Name: mdb

Implementation-Title: mdb

Implementation-Version: 1.0-SNAPSHOT

Workaround

Use weblogic.Deployer or WLST instead of Administration Console.

9.2

10.0

CR290849

It was not possible to set the WeblogicPluginEnabled attribute of ClusterMBean from Administration Console.

This problem has been resolved by providing a check box in Advanced Settings of the Cluster > Configuration > General tab that sets WeblogicPluginEnabled attribute of ClusterMBean.

9.1

9.2 MP2

CR295980

In the Administration Console Online Help published at http://e-docs.bea.com/wls/docs92/ConsoleHelp/pagehelp/Corecoreserverchannelconfiggeneraltitle.html, as per the description for the configuration option, Listen Port, a value of -1 indicates that the network channel should obtain this value from the server's configuration.

Workaround or Solution:

Setting no values to Listen Port indicates that the network channel obtain this value from the server’s configuration.

9.2

CR296702

CR324362

When you navigate the file structure to deploy an application and if some of the directories in the file structure does not have Read access, Administration Console used to raise NullPointerException instead of displaying a message that says no files are selectable.

This problem has been resolved.

9.1

9.2 MP2

CR301221

There was no option in Administration Console to monitor connection details for a Jolt Connection Pool.

Workaround or Solution:

You can now use the Administration Console to view details for each Jolt Connection Pool connection. Click on a connection pool entry in the monitoring table to display a page with details for each connection.

9.1

9.2 MP2

CR302636

Slow performance was observed for Administration Console when user accessed it for the first time.

This problem has been resolved.

9.2

9.2 MP2

CR308872

In Administration Console, tabs that were not selected used to display "-Selected" in their alternative text.

This problem has been resolved.

9.2

9.2 MP2

CR312603

In Administration Console, on the Configuration > Default Delivery page of a JMS connection factory, there was no GUI control to set the DefaultRedeliveryDelay attribute of the JMS connection factory.

This problem has been resolved by providing a text field named Default Redelivery Delay in the Default Delivery Configuration Parameter Settings page of the JMS connection factory.

9.2

9.2 MP2

CR313360

Entering invalid characters in a Console field used to cause full stack trace instead of rendering an error message.

This problem has been resolved.

9.2

9.2 MP2

CR302886

Japanese characters on the Performance page of the Server are garbled after clicking the Refresh button.

This problem has been resolved.

9.2

9.2 MP2

CR302363

When you deploy an application with a web module that has an empty string as the context root, the following error message was displayed on Administration Console:

Unable to access the selected application

This problem has been resolved.

9.2

9.2 MP2

CR305443

The value of Active Execute Threads displayed on the Server > Monitoring >Threads page was incorrect.

This problem has been resolved. The value of <Execute Thread total count> - <Standby Thread Count> is displayed now.

9.2

9.2 MP2

CR310332

If Tuxedo Server was down, WebLogic Tuxedo Connector (WTC) with ON_STARTUP connection policy was not able to stop retry connection.

This problem has been resolved.

9.2

9.2 MP2

CR311645

Clicking the Auto-Refresh icon in the Server > Monitoring > Performance or Deployment > Monitoring tab resulted ClassNotFoundException being logged in the server log.

This problem has been resolved.

9.2

9.2 MP2

CR316237

CR316078

The user was not able to stop the application if individual modules were targeted on two different Managed Servers in the cluster.

This problem has been resolved.

9.2 MP1

9.2 MP2

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

CR318869

Applications deployed using Administration Console Japanese edition could not be updated because the Active Changes button was missing on Administration Console.

This problem has been resolved.

9.2

9.2 MP2

CR280939

When you exported or imported a large JMS queue using the Administration Console, OutofMemory exception used to occur.

This problem has been resolved.

9.2

9.2 MP3

CR283037

The Administration Console was not showing the status of MessagingBridge run time instances.

This problem has been resolved.

9.2 MP2

9.2 MP3

CR315652

The Previous and Next links on the Deployments page of the Administration Console were disabled when the deployments were expanded.

This problem has been resolved.

9.2

9.2 MP3

CR315687

The Deployment page on the Administration Console used to display only ten deployments per page.

This problem has been resolved.

9.2 MP1

9.2 MP3

CR326877

CR330323

Users accessing the Administration Console using a proxy server were disconnected from the Administration Server as it redirects the URL to port 7001, which did not access the Administration Console from the client side.

This problem has been resolved.

9.2 MP1

9.2 MP3

CR343034

CR314207

CR346892

Modifying the Administration Console context path by changing the URL, the JNDI view for the JNDI tree of the Server did not use the new context path and it was not displayed correctly.

This problem has been resolved.

9.2 MP2

9.2 MP3

CR345559

When Managed Server was not running, NullPointerException used to occur in the Store-and-Forward Agent Monitoring page of the Server.

This problem has been resolved.

9.2 MP2

9.2 MP3

CR332702

On the Server > Configuration > General page, the icons which indicated that the server need to be restarted, for a change to take effect, were not displayed correctly.

This problem has been resolved.

9.2 MP2

9.2 MP3

CR333879

CR349850

An exception used to occur while accessing the Server > Monitoring > Performance page from the Administration Console.

This problem has been resolved.

9.2

9.2 MP3

CR334591

The content of a JMS text message was getting changed when exporting the JMS text message from the Administration Console.

This problem has been resolved.

9.2 MP1

9.2 MP3

CR334873

CR352224

WebLogic Administration Console was not allowing the user to create more than 100 WTC Import/Export services.

This problem has been resolved.

9.1

9.2 MP3

CR339402

The connection factory was displayed in the JNDI tree whenever the name is prefixed with 'W', otherwise it was not getting displayed though it was created in the config.xml file.

This problem has been resolved.

9.2 MP2

9.2 MP3

CR323919

You were not able to create a data source through the Administration Console when oracle.jdbc.pool.OracleDataSource was used as the driver class.

This problem has been resolved.

9.2

9.2 MP3

CR346498

The Administration Console failed to open the JMS Modules page with javax.servlet.ServletException if the page was customized to add some filter criteria.

This problem has been resolved.

9.2

9.2 MP3

CR347446

The administration port must accept only secure, SSL traffic, and all connections via the port require authentication. But you were able to select non-secure protocol as Administration Protocol from the Administration Console.

This problem has been resolved. Now non-secure protocols are not available on the Administration Console.

9.2 MP2

9.2 MP3

Known and Resolved Issues

WebLogic Server Known and Resolved Issues

Administration Console

Apache Beehive Support

Beangen

Connector

Core Server

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	9.2
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 WebLogic Server 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	9.2
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: Extract all files in `BEA_HOME/common/deployable-libraries/weblogic-beehive-1.0.ear` into a folder. Edit application.xml, removing the whitespace preceding `<?xml version=?1.0? encoding=?UTF-8??>` Make a new EAR file of the same name (weblogic-beehive-1.0.ear) containing all files extracted from the original EAR file. Replace the original EAR file with the new one.	9.0	9.2
CR237173	The build-control-module task referenced a CLASSPATH property that does not exist. If you used the `build-control-module` task, the following error message occurred 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` 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`. For 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	9.2
CR314023	Apache 2.2 plug-ins (64-bit) for SLES x86_64 are now available in WebLogic Server 9.2 MP2 installers.	9.2	9.2 MP2

Change Request Number	Description and Workaround or Solution	Found In	Fixed In
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
CR266092	The application descriptors `application.xml`, `weblogic-application.xml`, and `weblogic-extension.xml` were not validated. If an invalid application descriptor is used in WebLogic Server 9.2 it breaks even if it worked in WebLogic Server 9.0 and 9.1. The workaround was to modify the application code to use a valid descriptor.	9.2	9.2
CR269439	In DTD-based EJB deployment descriptors, the '/' character is permitted in the EJB name, but when these descriptors were upgraded to schema-based deployment descriptors, it used to cause failure. That is because schema-based EJB deployment descriptors were not permitting the '/' character in the EJB name. This problem has been resolved. The '/' character in an EJB name in schema-based EJB deployment descriptors.	9.2	9.2 MP1

Change Request Number	Description and Workaround or Solution	Found In	Fixed In
CR240414	The DDConverter fails to convert RAR deployment descriptors created with WebLogic Server 8.1 to deployment descriptors compatible with WebLogic Server 9.x. The symptom for the user showed up as an `inactive-connection-timeout-seconds` element in the descriptor. It should have been simply ignored because it no longer applies when a 1.0 adapter is converted to 1.5. Workaround or Solution: The `inactive-connection-timeout-seconds` element is now ignored.	9.0	9.2
CR270239	The `Debug` flag used for profiling RA connection pools was always set to true with no provision to turn it off. This caused a lot of clutter in the log & event files. Workaround or Solution: Profiling is disabled by default. To enable profiling, use the following system property: `-Dweblogic.connector.ConnectionPoolProfilingEnabled=true`	9.2	9.2
CR278335	The Resource Adapter container, to function correctly, used to track connection instances created to each of the managed connections for internal use. However, a few connection instances were leaking due to a timing issue between the `close()` and the finalization of these instances. This problem has been resolved.	9.1	9.2 MP1
CR286135	When J2EE deployment descriptors included <security-permission-spec> using custom SecurityPermission classes, which were packaged as part of the J2EE archive, WebLogic Server raises a ClassNotFoundException. This problem has been resolved.	9.2	9.2 MP1
CR271570	When multiple threads modified the data member of a WebLogic Connector ConnectionPool, `ConcurrentModificationException` was raised. This problem has been resolved.	9.1	9.2 MP2

Change Request Number	Description and Workaround or Solution	Found In	Fixed In
CR248404	Depending on the timing, during the service migration, the persistent store associated with the JMS server may get closed before a clean shutdown record is written. If this occurs, a PersistentStore exception is thrown during JMS Service migration. This problem has been resolved.	9.1	9.2
CR256208	Work Managers created from a domain’s configuration file (config.xml) did not have a reference to their application’s administrative mode trigger because the WorkManagers were created before the trigger. This problem has been resolved.	9.0	9.2
CR258827	Some global WorkManager Runtime MBeans and their associated components, such as MinimumThreads and RequestClass MBeans, did not show correct values because of a WorkManager deployment problem. This problem has been resolved.	9.0	9.2
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. This problem has been resolved.	9.0	9.2 MP1
CR262153	The appropriate application context and classloader were not being configured when creating a Work Manager for Message-Driven Beans (MDBs). This problem has been resolved. Work Manager is now configured appropriately for MDBs.	9.0	9.2 MP1
CR262848	Remote calls to a method in an updated EJB used to invoke the wrong method. This problem has been resolved.	9.0	9.2 MP1
CR266237	When the WebLogic Server replication manager sent a ByteArrayDiff object larger than 1016 bytes, only 1016 bytes were received; bytes in excess of 1016 were not received. This caused a CollocatedRemoteRefException in some cases; for example, when a replicated SFSB was used. This problem has been resolved.	9.0	9.2 MP1
CR269846	Sockets opened through an `HTTPUrlConnection` or sockets that were part of health checks were getting stuck in `CLOSE_WAIT` state. Those sockets also used to incur memory leaks in the Java heap of the Managed Servers. The impact of this memory leak varied depending on the socket implementation of the operating system and JVM. This problem has been resolved.	9.1	9.2
CR271744	WebLogic Server's IIOP/CORBA implementation was generating the wrong repository ID for java.lang.String[]. This problem has been resolved.	9.1	9.2 MP1
CR274989	A `ClassCastException` was being raised and connection used to fail from the WTC service to an EJB deployed as a different application, in a different EAR. This problem has been resolved.	9.1	9.2 MP1
CR279717	Defining a custom, global Work Manager, with the name '`default`', would not override the system-wide default Work Manager; it used to cause run-time MBean registration errors. This problem has been resolved. A custom, global Work Manager can now be defined, which overrides the predefined default Work Manager.	9.1	9.2 MP1
CR279846	A `NullPointerException` used to be raised by `javax.rmi.PortableRemoteObject.narrow()` when a thin client tried to access EJBs deployed with version information. This problem has been resolved. Version information is now encoded in such a manner that this problem does not occur.	9.1	9.2 MP1
CR284416	Sharing RootPOA was causing a problem because it is deactivated during application shutdown; the RootPOA cannot be reused because it is in INACTIVE state. This problem has been resolved.	9.1	9.2 MP1
CR295628	Router information in the client's RJVM was getting corrupted. Therefore, MS1 was unable to establish connection after restarting. This problem has been resolved. Router information in the client's RJVM is updated correctly.	9.2	9.2 MP1
CR296785	Using Sun's HTTP handler was causing a ClassCastException. This problem has been resolved. Using Sun's HTTP handler no longer causes a ClassCastException.	9.2	9.2 MP1
CR300944	Automatic migration of Singleton services from a WebLogic Server instance takes 30 seconds when the graceful (When work completes) shutdown option is selected. This problem has been resolved: automatic migration is now immediate.	9.2	9.2 MP1
CR301798	A ClassCastException was being raised when two EJB EARs were using common classes. This problem has been resolved.	9.2	9.2 MP1
CR302572	When there is a serialization error in a customer's code, an Unmarshall exception was raised, which was not caught. This resulted in Replication Manager trying to replicate to a secondary server infinitely. This problem has been resolved. Serialization errors in customers' code do not result in an infinite loop while replicating sessions to a secondary server.	9.2	9.2 MP1
CR284453	In a WebLogic domain if different UNIX machines were configured with different post-bind UID/GID definition, a Managed Server started in this domain used to bind to an invalid or non-existent UID/GID. The Managed Server did not bind to the machine configuration to which the server was mapped. This problem has been resolved.	9.1	9.2 MP2
CR279200	Scripts `installSvc.cmd` and `uninstallSvc.cmd` were not available with WebLogic Server 9.2 MP1 release. This problem has been resolved by adding these scripts to WebLogic Server 9.2 MP2 installation.	9.2 MP1	9.2 MP2
CR305383 CR293134 CR323476 CR313894 CR317693	The WebLogic JNI layer was not raising `OutofMemoryException` to the Java layer when it failed to allocate memory. This resulted in core dump. This problem has been resolved.	9.1	9.2 MP2
CR306851	When Administration Server’s Listen Address was left blank, WebLogic Server 9.2 used to listen only to the physical IP and it was unable to be accessed by other alias IP. This problem has been resolved.	9.2	9.2 MP2
CR310790	The cluster messaging receiver that receives and dispatches multicast messages was using the WebLogic Server thread pool. The receiver never released the thread and continued to use it forever. This is the expected behavior but the thread was reported as hogging.