> Known and Resolved Issues > WebLogic Server Known and Resolved Issues

Known and Resolved Issues

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

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.

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

 

Administration Console

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:
  1. 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.
  2. 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:
  1. 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.
  2. 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
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
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:
  1. Go to a new domain
  2. Select the Security->Policies tab.
  3. 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
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://download.oracle.com/docs/cd/E13222_01/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 http://download.oracle.com/docs/cd/E13222_01. For example, the following is the correct URL for the ServerMBean entry in the WebLogic Server MBean Reference:
http://download.oracle.com/docs/cd/E13222_01/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://download.oracle.com/docs/cd/E13222_01/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://download.oracle.com/docs/cd/E13222_01/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

 

Apache Beehive Support

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR210907
Netui databinding expression language fails when BeanInfo overrides JavaBean property names.
Evaluation of expressions in the Netui databinding expression language throws errors when BeanInfo netui databinding EL does not to work when java.beans.BeanInfo is used to override JavaBean property names.
Workaround or Solution:
Do not override JavaBean property names using BeanInfo if you use a JavaBean in Netui databinding. If you must databind to such a bean, wrap the bean in a UI version of the bean that follows the JavaBean property naming convention.
9.0
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:
  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
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

 

Beangen

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

 

Connector

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

 

Core Server

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.
Workaround or Solution:
The cluster messaging receiver has been moved to its own dedicated daemon thread outside of the thread pool to prevent the reporting of the hogging thread.
9.1
9.2 MP2
CR310540
JMSSession.execute()/onMessage threads were getting stuck and being logged.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR310986
Applying patches for CR310790 and CR279207 used to get conflicting results in MulticastManager.java.
This problem has been resolved by creating a combo patch for CR310790 and CR279207.
9.1
9.2 MP2
CR311983
Unsynchronized HashMap resulted in stuck threads and high CPU usage.
This problem has been resolved.
9.2
9.2 MP2
CR318013
An error used to occur while adding FD to Epoll.
This problem has been resolved.
9.2
9.2 MP2
CR316335
Calling a remote EJB by IIOP with transaction, weblogic.corba.cos.transactions.CoordinatorImpl used to result in a memory leak on the client-side server.
This problem has been resolved.
9.2
9.2 MP2
CR324729
CR333774
CR344111
NullPointerException used to occur during HTTP Session State Replication under load.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR325288
CR348655
When a startup class performed JNDI lookup for EJB in a deployed application, the AdminModeHandler.checkLookup() method used to fail.
This problem has been resolved.
9.1
9.2 MP3
CR346885
The SSL socket was not getting closed when SSL close the connection.
This problem has been resolved.
9.2
9.2 MP3
CR330427
CR349430
The Administration Console used to hang when a remote Managed Server was restarted.
This problem has been resolved.
9.2
9.2 MP3
CR346335
Cancelling I/O for EPollSocketMuxer resulted in OutOf Memory exception.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR351195
A memory leak used to occur in PermGen space after modules were undeployed.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR326720
A failure in heartbeat trigger for RJVM used to occur when outbound channel was configured with t3 protocol.
This problem has been resolved. Now outbound channels are preferred over the default channel.
9.2
9.2 MP3
CR353581
Trigger used to close the reused socket prematurely and this resulted in SocketException.
This problem has been resolved.
9.2
9.2 MP3
CR355278
While starting Managed Servers in a domain where domain wide administration port is enabled, NullPointerException is observed in the AdminServer log.
9.2 MP3
 

 

Deployment

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR067087
The security-permission element is available in the weblogic.xml and weblogic-ejb-jar.xml deployment descriptors, but is not available in the weblogic-application.xml descriptor. Therefore, in an Enterprise application, you can only apply security policies to JAR files that are EJBs or Web applications.
7.0
 
CR071138
The weblogic.Deployer tool interprets any extra string values between command-line arguments as a file specification. For example, if you enter the command:
java weblogic.Deployer -activate -nostage true -name myname -source c:\myapp\mymodule
the tool attempts to activate a file specification named “true”, because the -nostage option takes no arguments and “true” is an extraneous string value.
7.0
 
CR258450
When you use wlconfig Ant task for configuring a new application, the source path entry was incorrectly updated in the Admin server's configuration file. This used to cause failure in application deployment.
This problem has been resolved.
9.0
9.2
CR259777
WebLogic Server 9.1 was not backward compliant with WebLogic Server 8.1 weblogic.Deployer tool.
This problem has been resolved.
9.1
9.2
CR261299
Deployment service messages between servers in the same domain were authenticated every time when they were sent and hence it degrades server performance.
Workaround or Solution:
Servers in the same domain now use SALT authentication.
9.1
9.2
CR091020
If you deploy an application to a cluster and one or more clustered servers are unavailable (for example, servers partitioned from the cluster due to a network outage), the deployment operation may appear to hang. In addition, the partitioned servers may not deploy the application even after they successfully rejoin the cluster.
Workaround or Solution:
Reboot the partitioned servers after they rejoin the cluster.
8.1
 
CR262898
When two applications were deployed, the JNDI lookup on the first application failed during the context initialization of the second application even though the first application was already deployed.
Workaround or Solution:
  • The AdminMode on WorkContext for callbacks is now set in the BASIC_DEPLOYMENT_HANDLER.
  • The Web Application contains now fires the listener as the DeploymentInitiator user and not as Anonymous.
  • If a custom classloader is used, its parent classloader is checked to determine whether or not it is a generic classloader. If the parent class is a generic classloader, then the application name is extracted from the parent classloader.
9.0
9.2
CR278660
Applications can contain descriptor files that extend the descriptors supported by WebLogic Server. These descriptor extensions are defined by a weblogic-extensions.xml file, either in an application itself or by a library module that an application references. These descriptor extensions reference Java factory classes, providers, and schema urls that must be available to the Administration Console as a console user navigates through an application’s descriptors, deployment plan, and configuration. If these extension classes are not found in the server classpath, then assertion errors will be encountered by the console and displayed to the console user. More detailed exception information will be recorded in the server logs.
Workaround or Solution:
WebLogic Workshop and WebLogic Portal applications frequently make use of these descriptor extensions to support their configuration. These descriptor extensions are defined by libraries that are normally included in domains that support WebLogic Portal. Therefore, it is important that these libraries are also available on the administration server so that they are available to the console.
9.2
9.2
CR279281
Some OS and NFS combinations result in deployment failures or configuration updates. Example exception is:

weblogic.management.DeploymentException: Attempt to operate 'distribute' on null BasicDeploymentMBean

Workaround or Solution:
  • Run statd() and lockd() processes on every NFS client that accesses a remote NFS volume.
  • If multiple servers that share the same domain root are started with different user Ids of same group, set the correct “umask” for the server processes so that a file created by one server can be opened for read/write by other servers without security exceptions.
9.1
 
CR286936
WebLogic Server used to log a large number of redundant messages regarding config modules (for example, “Registering config module ...”) in the server log file.
This problem has been resolved. WebLogic Server does not log redundant messages regarding config modules.
9.2
9.2 MP1
CR291072
WebLogic Server was not able to find application modules if the application had 'Implementation-Version' specified in its MANIFEST.MF file.
This problem has been resolved.
9.2
9.2 MP1
CR295697
Plan.xml was not getting updated when Web service policies were changed using WebLogic Administration Console.
This problem has been resolved. WebLogic Server updates the plan.xml correctly.
9.2
9.2 MP1
CR302616
During WebLogic Server shutdown, PersistentStoreException was getting raised.
This problem has been resolved.
9.2
9.2 MP1
CR303287
CR310307
When deploying applications containing StAX classes, WebLogic Server used to raise ClassCastException.
This problem has been resolved.
9.2
9.2 MP2
CR302510
WebLogic Server would not stop an application if individual modules were targeted on different Managed Servers in the cluster.
This problem has been resolved.
9.2
9.2 MP2
CR310687
An application in which the web module mapped with different context roots used to fail to deploy.
This problem has been resolved.
9.2
9.2 MP2
CR298984
When starting with MSI mode, Managed Server used to fail to deploy libraries and DeploymentException was being raised.
This problem has been resolved.
9.2
9.2 MP2
CR312019
WebLogic Server used to create the plan.xml file in two different locations - in system temp folder and in a folder under $domain\config\deployments.
This problem has been resolved. WebLogic Server now creates plan.xml only in the $domain\config\deployments folder.
9.2
9.2 MP2
CR314586
WebLogic Server used to ignore the DeploymentOrder attribute specified for a startup class element in config.xml.
This problem has been resolved. If DeploymentOrder is specified, it is used to determine the execution order for startup classes.
9.2
9.2 MP2
CR301759
When the weblogic.deployer utility was used multiple times to redeploy static files in an application, the application state used to hang in the STATE_UPDATE_PENDING status.
This problem has been resolved.
9.1
9.2 MP3
CR313191
An application with a deployment plan was not getting deployed from a Windows machine remotely to a UNIX machine using the weblogic.deployer utility because the path was not resolved correctly.
This problem has been resolved.
9.2
9.2 MP3
CR317823
When an application which referred a J2EE library was updated, the J2EE Library Overview page of the Administration Console was not displaying the reference between the application and the library.
This problem has been resolved.
9.2
9.2 MP3
CR315383
Memory leak used to occur in ClassLoader when using side-by-side deployment.
This problem has been resolved.
9.2
9.2 MP3
CR321569
If there were multiple session-descriptor elements in the plan.xml file, the value of session-descriptor was overwritten with a new value after merging with the deployment plan.
This problem has been resolved.
9.2
9.2 MP3
CR321914
The sample worklist application exported from Weblogic Workshop could not be deployed using the Administration Console.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR322190
CR336860
When the weblogic.deployer utility was used to deploy an application, the temporary directory that cache the application was created in a different location other than /var/tmp.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR335631
The config_prev_bak directory was not deleted after the deployment. When WebLogic Server instances are rebooted without deleting config_prev_bak, some configurations used to get reverted or removed.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR347519
The weblogic.deployer utility was not using previous targets when redeploying a newer version of the application and the deployment used to fail.
This problem has been resolved.
9.2 MP1
9.2 MP3

 

EJBs

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR231076
Monitoring information is not always available for Message-Driven Beans.
9.0
9.2
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
9.2
CR232765
The primary key in an Oracle table is a CHAR but the query field in the SQL table is a VARCHAR2.
Change database schema from CHAR to VARCHAR2. Using CHAR as a primary key is not recommended for the Oracle database.
9.2
 
CR232765
The primary key in a Oracle table is CHAR while the query field in an SQL statement is a VARCHAR2.
Workaround or Solution:
Users with Oracle databases should not use CHAR as the primary key.
9.2
9.2
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
 
CR249231
Because of an issue in the EJB container, the Work Manager configured for a Message-Driven Bean was not used in some cases. As a result, specific settings on the configured WorkManager, such as a MaxThreadConstraint, did not take affect.
This problem has been resolved.
9.0
9.2
CR253747
During the deletion of an Entity EJB instance that participates in a relationship with another EJB instance and if Cascade Delete is set to True, a NullPointerException was raised.
The problem has been resolved.
9.0
9.2
CR255783
CR212624
A constraint violation occurred when creating one-to-one related beans in ejbPostCreate().
This problem has been resolved.
9.0
9.2
CR259377
The internal EJB deployment logic caused EJB timers to be removed when an application was redeployed.
Workaround or Solution:
EJB timers are only removed when an application is explicitly undeployed or removed.
9.2
9.2
CR260399
EJBGen does not support -noDDGen and -ddOnlyGen options.
Workaround or Solution:
Support was added for the -noDDGen and -ddOnlyGen options. You must specify the -ddOnlyGen option for EJBGen to generate deployment descriptor files.
9.2
9.2
CR260850
In a cluster environment, CMP/One-To-One CMR field returned a stale reference of the child bean when cache-between-transactions was set to true.
This problem has been resolved.
9.1
9.2
CR261342
WebLogic Server does not support an EJBGen annotation for the "entity-always-uses-transaction" element.
An EJBGen annotation"WeblogicCompatibility" which has only an'entityAlwaysUsesTransaction' attribute has been added. This attribute allows you to specify whether an entity bean must always use a transaction.
In previous releases of WebLogic Server, when an entity bean ran in an unspecified transaction, the EJB container would create a transaction for the entity bean. In WebLogic Server 9.2, the EJB container no longer creates a transaction when an entity bean runs in an unspecified transaction.
To disable the new behavior and cause the EJB container to create a transaction for entity beans that run in unspecified transaction, set the value of the 'entityAlwaysUsesTransaction' attribute to Constants.Bool.TRUE.
9.0
9.2
CR262956
In some scenarios, when deleting a child bean and when the tags <enable-batch-operations> and <order-database-operations> in the weblogic-cmp-jar.xml file are set to false, WebLogic Server used to raise OptimisticConcurrencyException.
This problem has been resolved.
9.1
9.2
CR265044
EJB entitlement policies set using the Administration Console on EJB methods with array parameters did not take effect because of the way the entitlement policies were registered with the underlying security code. This issue only affected policies set using the Administration Console, and did not affect standard EJB method permissions set using ejb-jar.xml.
This problem has been resolved.
9.2
9.2
CR265181
If a Message-Driven Bean (MDB) uses a distributed destination, the MDB uses a set of MessageDriven managers each of which targets a member of the distributed destination. When deploying an MDB, each manager invokes the MessageDrivenBeanInfoImpl#onUndeploy() method. Therefore, it is possible that an onUndeploy() method is executed several times. However, on the first onUndeploy() call all Message Driven managers are unregistered from a Migration Manager causing an assertion error.
Workaround or Solution:
Do not register a MessageDriven manager to a Migration manager if the MDB uses a distributed destination. In addition, make each MessageDriven manager unregister itself from a Migration manager instead of unregistering all managers at a time.
9.0
9.2
CR267000
When WebLogic Server has not loaded Entity Bean, it is possible for the home.remove(pk) call to fail. This failure is caused when the pk field of the bean, which is null, is used.
Workaround or Solution:
The pk value which is set in the EJBContext should be used instead.
9.2
9.2
CR271005
A ClassCastException used to occur when Message-Driven Beans (MDBs) were used with a non-WebLogic JMS provider during an upgrade from a WebLogic Server 8.1 Service Pack 3 application to a WebLogic Server 9.1 application.
This problem has been resolved.
The ClassCastException no longer occurs when MDBs are used with a non-WebLogic JMS provider.
9.1
9.2
CR271656
When EJB timers were deserialized from the WebLogic persistent store, in some cases the wrong classloader was used, which caused the deserialization to fail and an AssertionError to be thrown.
This problem has been resolved.
9.2
9.2
CR273555
Non-transactional Message-Driven Beans (MDBs) subscribing to WebLogic JMS topics now override the acknowledgement mode on a connection factory with an acknowledge mode of ack-prev. This is required to ensure no messages are lost in the event of a failure.
If such MDBs were incorrectly configured to use a custom connection factory with an acknowledge mode of ack-all, and the MDBs subscription type is configured as durable, the MDBs may experience a degradation in performance with this change. This note does not apply to MDBs that use the default MDB connection factory or that subscribe to non-WebLogic JMS topics.
9.2
9.2
CR274410
When integrating a non-WebLogic JMS server with WebLogic Server 9.1, Message-Driven Beans (MDBs) with transaction time-outs defined in the MDB descriptors used to fail and raise a ClassCastException.
This problem has been resolved.
9.1
9.2
CR283414
The SQL query 'select x,y from mytable where x = ?' was causing a nullPointerException if the run-time parameter value was null. A non-null value was expected in the query.
This has been resolved. A null value does not cause nullPointerException.
9.1
9.2 MP1
CR289838
The cached classinfo objects for the value objects were not getting garbage-collected during redeployment of applications, causing a ClassCastException.
This problem has been resolved.
9.2
9.2 MP1
CR293982
CR299012
Even with the start-mdbs-with-application flag set to false, Message-Driven Beans (MDBs) were starting before the application was in active status, causing WebLogic Integration in high availability mode to fail.
This problem has been resolved. MDBs start only when the application is in active status.
9.2
9.2 MP1
CR296232
WebLogic Server's EJB container was unable to handle WebLogic CMP deployment descriptors larger than 1 MB in size.
This problem has been resolved.
9.2
9.2 MP1
CR296824
An error in the code generation template used to cause the WebLogic Server to generate incorrect code.
The problem has been resolved.
9.2
9.2 MP1
CR302157
Single-object SQL-Finders were returning null value if the referenced object did not exist. This behavior is inconsistent with EJB 2.1 specification.
This problem has been resolved. In compliance with the EJB 2.1 specification, the ObjectNotFoundException is raised when the finder query does not find any results.
9.2
9.2 MP1
CR297376
Sybase JDBC driver and DataDirect driver are considered as expecting different SQL semantics, and for the driver that fails, the column definitions have an implied NULL unless specified otherwise, so defining a column as BIT used to fail because BIT columns cannot be NULL.
This problem has been resolved by changing the EJB DDL to be explicit about NOT NULL for BIT column type.
9.2 MP1
9.2 MP2
CR306737
Error used to occur while using -J options (ExtraEJBCOptions) with the weblogic.appc tool.
This problem has been resolved.
9.2
9.2 MP2
CR307754
Entity Bean from the pool was not being initialized before re-use in some scenarios and it used to cause unexpected Bean data.
This problem has been resolved.
9.2
9.2 MP2
CR289850
Class-level Generic EJBs were not supported in WebLogic
Server 9.2.
This problem has been resolved.
9.2
9.2 MP2
CR292371
WebLogic Server used to raise EndpointActivationException in scenarios where endpoint was activated as part of connect call.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR311712
A NullPointerException was being raised in EntityCache$MRUElement.remove().
This problem has been resolved.
9.1
9.2 MP2
CR312686
MDBs were not able to connect to JMS destination after the JMS server was migrated from one server to another.
This problem has been resolved.
9.2
9.2 MP2
CR264079
When an inner class was passed as an argument to an EJB method, such as ejbCreate, the generated code was not converting the inner class argument to a correct representation.
This problem has been resolved.
9.1
9.2 MP3
CR288669
Deadlock could happen on multiple entity beans and an exception used to raise in the ExclusiveEntityManager.afterCompletion() method.
This problem has been resolved.
9.2
9.2 MP3
CR299950
When an EJB had OracleClob as dbms-column-type in the weblogic-cmp-rdbms-jar.xml file and if you navigated to Deployments > MyEntityBean > Testing > Console, the Administration Console used to throw an error.
This problem has been resolved.
9.1
9.2 MP3
CR309523
The ejbHomeQuery method used to raise NullPointerException in the EJB container.
This problem has been resolved.
9.2
9.2 MP3
CR324676
Each time you stopped and started an MDB that has a durable subscription to a topic, the client ID string used to get longer.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR333809
The EJB-QL query that contained parenthesis was wrongly transformed in the appc-generated Java code.
This problem has been resolved.
9.2
9.2 MP3
CR339471
Invoking an EJB finder method twice used to cause an EagerLoadingException when Eager Caching was enabled.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR349645
JMSConnectionPoller failed to work for customized decorator pattern.
This problem has been resolved. A system property, weblogic.mdb.JMSProviders.NeedContinuousPolling, has been added. For customized JMS Provider or when another type of JMS Provider needs to turn on the NeedContinuousPolling flag, you can use this property as follows:
weblogic.mdb.JMSProviders.NeedContinuousPolling=provider1,provider2,provider3
Case is ignored for comparison.
9.2 MP1
9.2 MP3
CR347850
CR348791
While obtaining an EJB from the Session Bean pool, RemoteExceptions were raised and these exceptions were corrupting the Session Bean pool.
This problem has been resolved.
9.2
9.2 MP3

 

Examples

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR191354
Medical Records does not yet use deployment plans.
9.0 Beta
 
CR208965
The medrec.wls.config target in SAMPLES_HOME/server/medrec/setup/build.xml has a known issue with respect to security configuration.
9.0 Beta
 
CR234212
In the JMS Queue example instructions, the queue's corresponding connection factory instance is referred to as exampleQueue. However, the actual connection factory name in the Examples server is weblogic.examples.jms.QueueConnectionFactory, which is identical to the connection factory's JNDI name.
9.0
9.2
CR287762
The Web Services Reliable Messaging example has two known problems which cause the example to not work correctly. The example is located in WL_HOME/samples/server/examples/src/examples/webservices/reliable, where WL_HOME refers to the main WebLogic Server installations, such as /bea/weblogic92.
The two problems are as follows:
  • The example uses an incorrect WS-Policy file. In particular, the WS-Policy file includes an incorrect wsrm namespace and lists the assertions in an incorrect order.

    • To workaround this problem, update the example WS-Policy file (called ReliableHelloWorldPolicy.xml) to look like the default reliable messaging WS-Policy file included in WebLogic Server, described in Use of WS-Policy Files for Web Service Reliable Messaging Configuration. Pay particular attention to the namespaces and assertion order.

  • The JWS file that implements the client Web Service that invokes the reliable Web Service (ReliableClientImpl.java) incorrectly includes the wsdlLocation attribute of the @weblogic.jws.ServiceClient annotation. You should not specify this attribute in the client Web Service because it is possible that the runtime retrieval of the WSDL file might not succeed. To prevent this potential problem, it is best to not specify the attribute at all so that WebLogic Server always uses the local WSDL.

    • To workaround this problem, update the ReliableClientImpl.java JWS file and remove the wsdlLocation attribute of the @ServiceClient annotation.

After you have fixed these two problems, re-compile the example.
9.2
 

 

Installation

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

 

J2EE

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR246511
The context-param element was not declared as configurable, which prevented it from being updated from the deployment plan.
Workaround or Solution:
The context-param element is now marked configurable in the Descriptor Bean.
9.2
9.2
CR247470
There was no easy way to access the subdeployments of a library (defined in the configuration). Thus, a referencing app could not find any subdeployments already registered by one of its libraries.
Workaround or Solution:
  • An internal API for Containers (JMS/JDBC) was created for the purpose of accessing the subdeployments of a library.
  • The JMS module was enhanced to look at library subdeployments if no matched subdeployments are found in the application.
9.1
9.2
CR254593
The alternate descriptor specified in the weblogic.deployer tool is not picked up.
This problem has been resolved.
9.1
9.2
CR254940
The principal-name of security role assignment in the weblogic.xml file does not allow strings with spaces in them.
Workaround or Solution:
The schema has been modified to allow blank spaces.
9.0
9.2
CR259122
In Weblogic Server 9.1, spaces are not allowed for principal-name.
This problem has been resolved.
9.1
9.2
CR261887
If a customer application uses its own classloader and WebLogic Server cannot extract the application name, WebLogic Server returns a null.
Workaround or Solution:
WebLogic Server now checks whether the parent class loaded is GCL. If it is, WebLogic Server extracts the application name from the parent’s classloader.
9.0
9.2
CR273929
Web descriptors are generated in the META-INF directory instead of the WEB-INF directory.
This problem has been resolved.
9.1
9.2
CR250717
Because of differences in the handling of the module-uri (ending in WAR) and the module-name, the classloader structure was not honored.
Workaround or Solution:
WebLogic Server now allows both module-name and the context-root in the classloader structure.
9.0
9.2
CR279171
In releases prior to WebLogic Server 9.2, the start-mdbs-with-application element of weblogic-application.xml accepted strings in any case. For example, “true”,”True“, and “TRUE” were all accepted. However, only the “true” form was expected.
Workaround or Solution:
The value of the start-mdbs-with-application descriptor for previous releases is converted into lower case.
9.2
9.2
CR282341
During an update of an existing J2EE application, the configuration changes were not updated in the J2EE container, which caused a mismatch between the configuration view of the J2EE container and the domain configuration file (config.xml).
This problem has been resolved.
9.2
9.2
CR293111
The weblogic.appmerge tool used to fail to execute when there were temporary directories created by a different UNIX users.
This problem has been resolved by moving the temporary directories to a different folder, user.home. In addition, now existing directories can be deleted before proceeding and displays an error message if the user does not have write permission.
9.2
9.2 MP2
CR303331
The user was not able to re-deploy EJBs individually without re-deploying the entire application.
This problem has been resolved.
9.2
9.2 MP2
CR313232
The startup/shutdown classes registered in weblogic-application.xml descriptor file were required to extend from a WebLogic-specific class, weblogic.application.ApplicationLifecycleListener.
This problem has been resolved.
9.2
9.2 MP2
CR295670
CR359373
A NullPointerException used to occur when deploying an application which was using shared libraries and had Specification-Version or Implementation-Version in its manifest.
This problem has been resolved.
9.2
9.2 MP3
CR308581
When running the appc tool using the command line against a very large EAR application and if the memory specified was less than 3.5 GB, an OutOfMemoryException would occur.
This problem has been resolved.
9.2
9.2 MP3
CR315008
The service control handler annotation used to result in DuplicateKey exception during a publish to WebLogic Server 9.2.
This problem has been resolved.
9.2
9.2 MP3
CR344144
ClassCastException used to occur during cluster synchronization when custom objects were bound to JNDI.
This problem has been resolved.
9.2 MP1
9.2 MP3

 

JDBC

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR188442
The Oracle Thin JDBC driver has not been certified with JDK 5.0. In internal testing, BEA has noted test failures with the DECIMAL data type (TAR 4019650.995).
9.0 Beta
9.2
CR246663
It is invalid to assign a JDBC module scope of Global when the module is packaged with an application. JDBC deployment currently does not perform validation on the module descriptor scope element.
Deployment of an application-packaged JDBC module will fail if the module descriptor's scope element is set to Global.
9.0
9.2
CR252601
If the initial capacity and the max capacity are changed in the same edit session and the new value for the initial capacity is larger than the value for the max capacity, the update will fail. This failure occurs because WebLogic Server checks the new value for the initial capacity against the value for the max capacity.
This problem has been resolved.
9.0
9.2
CR259803
EJB batch-enabling for Oracle uses some Oracle-specific, non-standard JDBC methods when creating prepared statements. If these statements are cached in the pool, the non-standard behavior of these statement remains for any subsequent user. One chief symptom is that a subsequent standard update call that should succeed will return 0, meaning no row was updated. In fact the call is never sent to the DBMS but is batched in the statement, waiting for a special batch call, or many more executeUpdate() calls until the non-standard set batch number is reached.
Workaround or Solution:
Oracle-specific code was added in the pool to reset standard behavior when caching any Oracle driver statement.
9.1
9.2
CR261026
WebLogic Server does not create a cache structure if the cache is defined to be zero-sized, but one internal routine refers to the structure without checking for null first.
9.1
9.2
CR280439
There is a performance degradation in the WebLogic Type 4 JDBC Driver for Oracle getAsciiStream() method call caused by fixes and enhancements to character set support in the driver. In general, the updated driver outperforms the previous version of the driver.
Workaround or Solution:
Use the getCharacterStream() method instead of getAsciiStream().
9.1
 
CR283816
The 3.5 version of the BEA-branded driver from DataDirect has failed in long-running tests when JDBC connection pools have the ShrinkingEnabled attribute set to true.
Workaround or Solution:
For optimal JDBC pool performance and stability, BEA recommends that you set the ShrinkingEnabled attribute to false.
8.1
 
CR269058
The 3.5 version of the BEA-branded driver from DataDirect had a issue in its date conversion code.
This problem has been resolved.
9.2
9.2
CR229551
In prior releases of WebLogic Server 9.2, member data sources of a multi data source could not be changed dynamically at runtime without requiring the shutdown/redeployment of the multi-data source causing potential application service interruption.
Workaround or Solution:
Administrative changes to a multi data source member list now take effect immediately, without requiring you to restart the multi- data source or WebLogic Server.
8.1
9.2
CR259715
WebLogic Server 9.2 supports additional databases for the Singleton Server feature. In addition to Oracle, which was the only previously supported DB, release 9.2 now also supports Sybase, MsSQL, Informix, DB2, and MySQL. BEA supports any version that is supported by WebLogic Server in general. DDLs to create the tables are provided for all of the vendors.
Workaround or Solution:
BEA continues to recommend that the DB be highly available, as the availability of the Singleton Servers directly depends on the availability of the database.
9.1
9.2
CR264732
The 3.5 version of the BEA-branded driver from DataDirect was updated from version 3.5.0013 to version 3.5.0038.
9.2
9.2
CR300757
Overloaded state missing from the JDBC Data Sources Monitoring: Statistics Console Help page and the JDBCDataSourceRuntimeMBean of the WebLogic Server MBean Reference.
Overloaded - all resources in pool are in use.
9.0
10.0
CR304978
The DB2 driver used to return an error when a callable statement execute stored procedure to retrieve BLOB images.
This problem has been resolved.
8.1 SP5
9.2 MP2
CR308330
If the user of the operating system that runs WebLogic did not have permission to write to the default temporary directory defined by JVM, the JDBC driver used to raise EmptyStackException.
This problem has been resolved.
9.2
9.2 MP2
CR312353
MultiDataSources were all being treated as participating in transactions even if individual DataSources they contained were not.
This problem has been resolved.
9.2
9.2 MP2
CR315851
The manifest in weblogic.jar used to fail to list Sybase jConnect 6.0 (jconn3.jar) JDBC driver.
This problem has been resolved.
9.2
9.2 MP2
CR317577
In WebLogic Console, the value of Waiting For Connection Success Total for JDBC connection pool monitoring is incorrect. Even if there were no connections waiting, Waiting For Connection Success Total count used to be increased.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR314547
JDBC connection leak was not detected if all statements were closed but the connection was not released.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR319100
The BEA-branded driver from DataDirect was updated to version 3.6.
9.2 MP2
9.2 MP2
CR341919
The BEA-branded driver from DataDirect was updated to version 3.7.
9.2 MP3
9.2 MP3
CR328324
When Initial Capacity and Maximum Capacity was not equal, JDBC pool used to shrink after 900 seconds even when ShrinkFrequencySeconds is set to 0.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR332434
CR346563
CR352171
The state of a JDBC data source was changed from Suspended to Running in a multi data source environment even if the database server was down. This behavior was caused if the CountOfTestFailuresTillFlush attribute is automatically configured by WebLogic Server.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR336538
The JTA JDBC objects lacked the pre-check that detected whether the underlying data source was disabled. This resulted in java.sql.SQLException when reusing a suspended database connection of an XA DataSource.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR342025
When setting a large value to JTA timeout and if the available connection did not exist in the ConnectionPool, java.lang.IllegalArgumentException used to occur when you tried to get the connection from the ConnectionPool.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR337679
When you shutdown a DataSource from the Administration Console, the operation used to fail with javax.transaction.SystemException. This behavior used to occur when using an XA driver.
Workaround or Solution:
Use untarget/target instead of shutdown/start operation.
This problem has been resolved.
9.2 MP1
9.2 MP3

 

JMS

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR249896
The Persistent Store Connection runtime statistics was incorrectly reporting a negative object count after recovery.
This problem has been resolved.
9.1
9.2
CR250886
The JMS wrappers do not correctly handle cases in which the caller is using the JMS 1.1 MessageProducer.send() methods.
Workaround or Solution:
The JMS wrappers were changed to check the values of qSender or tPublisher in the send() method and then call whichever one is not null.
9.0
9.2
CR251017
The persistent store in WebLogic Server 9.1 can encounter a thread-safety problem in some timing scenarios. The symptom can (but not necessarily) involve an Exception stack trace that includes the following:
"weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next()".
9.1
9.2
CR252956
The validation of the targeting of a Uniform Distributed Destination, as well as the validation of the list of members of a Weighted Distributed Destination, is not sufficient to prevent a user from mistakenly targeting a Distributed Destination to more than one cluster (or two non-clustered servers). A Distributed Destinations created in this way may seem to function but would have problems.
This problem has been resolved.
9.1
9.2
CR255152
When a subdeployment containing a SAF Imported Destination was targeted to a JMS server, an incorrect exception message was displayed.
Workaround or solution:
The exception message was corrected to display the appropriate error: “One of the targets XXX of SubDeployment YYY for SAF Imported Destinations ZZZ is not a legal target type.”
9.1
9.2
CR256300
Deploying JMS connection factory on a cluster in which the managed servers use both local and global JNDI names showed inconsistency in removing JNDI names from the JNDI tree. Both local and global JNDI names were removed completely by restarting the server that has the local JNDI name.
This problem has been resolved.
9.1
9.2
CR259365
A client JMS application using either transacted sessions or user transactions could sometimes hang on TransactionRolledBackException during a blocking synchronous receive call when the JMSServer was not located on the same server in a cluster as the client's JMS connection host, and the blocking receive timeout was greater than or equal to the transaction timeout.
This problem has been resolved.
9.1
9.2
CR260045
The persistent store administration tool used to delete unconsumed JMS messages.
This problem has been resolved.
9.0
9.2
CR260294
Configuring a connection factory on a Foreign JMS server residing on WebLogic Server 9.0 or WebLogic Server 9.1 that references a WebLogic Server version prior to 8.1 used to result in UnmarshalException during connection creation.
This problem has been resolved.
9.1
9.2
CR261947
In WebLogic Server 9.0, Uniform Distributed Destination members were not migrating properly when their parent JMS Server was migrated from one server to another server.
This problem has been resolved.
9.0
9.2
CR267433
WebLogic Server 9.x Message-Driven Beans (MDBs) used to be unable to listen to JMS messages on a distributed destination running on WebLogic Server 8.1.
This problem has been resolved.
The Configuration Directory Service (CDS) is modified to enable MDBs to listen to JMS messages on a distributed destination running on WebLogic Server 8.1.
9.1
9.2
CR267651
A NullPointerException used to occur when sending JMS messages in a queue because of a null dispatcherId.
This problem has been resolved.
9.1
9.2
CR27057
Using the JMS WLMessageProducer forward() API on a newly created message causes a JMSClientException.
The JMS WLMessageProducer forward() API can only be used on unmodified received messages.
9.2
 
CR272415
When the path service is associated with a single WebLogic Server instance in a cluster and that server is down during the upgrade process, the JMS client cannot send unit-of-order (UOO) messages to a uniform distributed destination (UDD) deployed on the cluster. However, in the case of existing JMS clients whose messages are sent to another server in the cluster, the clients continue sending the messages in the same UOO by using the cached path service.
Workaround or Solution:
Instead of using the path service, use the hash approach to route the UOO messages. In fact, the hash approach is the default approach used for UOO routing within UOO members. However, even in this case, existing producers cannot always send UOO messages to the UDD if the server is down because there is a change in membership.
9.2
 
CR272776
CR306041
When using the WebLogic Scripting Tool (WLST) offline to generate a JMS module descriptor, for certain JMS Connection Factory Boolean parameters you cannot set the value to false.
The following JMS Connection Factory attributes do not have their default value specified in the corresponding JMS Module descriptor schema definition.
<allow-close-in-onMessage>
<xa-connection-factory-enabled>
<flow-control-enabled>
<load-balancing-enabled>
<server-affinity-enabled>
<attach-jmsx-user-id>
Therefore, the Java default of false for these Booleans is used by WLST offline. So when they are manually set to false, WLST does not persist the values to the JMS module descriptor assuming that setting is redundant.
Workaround or solution:
After the JMS module descriptor is created using WLST offline, these boolean attribute values can be edited either manually or modified using the Administration Console.
9.2
9.2 MP3
CR274706
Deployment descriptor validation fails when descriptor validation is enabled, and an EAR file contains only JMS modules.
Workaround or Solution:
Make sure that there is at least one J2EE specification-compliant module in the EAR.
9.2
 
CR277464
A deadlock on weblogic.jms.client.JMSConnection used to occur occasionally when JMS clients reconnected.
This problem has been resolved.
The client connection no longer causes a deadlock on weblogic.jms.client.JMSConnection.
9.1
9.2
CR277493
When multiple JMS producers use the same JMS Client SAF instance (within a single JVM), depending on the timing of the JMS SAF client creation, you might receive the following exception:
Error getting GXA resource [Root exception is weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error getting GXA resource]
Workaround or solution:
When using multiple JMS SAF client producers, try introducing a small delay between the creation of each new client.
9.2
 
CR278644
Reconnecting transactedSession.commit() or transactedSession.rollback() calls may throw exceptions more than once when reconnecting.
When a transacted session allows reconnect -- that is, when a WLConnection.getReconnectPolicy() is not none -- the first call to session.commit() or session.rollback() will throw an exception after the server WLConnection has reconnected after a failure. This is expected behavior. Unfortunately, the second call to.commit() or.rollback() may also throw an exception.
Afterwards the reconnected transacted session will work normally.
9.2
 
CR278960
There is no support for multi-byte characters in WebLogic Store file and directory names. For instance, when the WebLogic Server name has multi-byte characters, the default store cannot be created, and the WebLogic Server will not boot.
Workaround or solution:
Create WebLogic Servers without multi-byte characters in the path name and use that path name rather than the default store. Do not use multi-byte characters in the Weblogic Server name.
9.2
 
CR279916
JMSSessionPoolTester requires temporary destinations to test and validate pooled connections used by JMS wrappers. The exception listener on the pooled connections is created by the JMSSessionPoolTester: it was not getting created if temporary destinations were disabled.
This problem has been resolved. JMS wrapper pooled connections utilize a connection exception listener even when temporary destinations on the JMS
Server hosting the connections have been disabled. This allows proper clean-up of pooled connections even when the session pool tester has been disabled.
Note that this resolution works only for JMS providers that trigger onException on a connection failure even when an asynchronous receiver is not running. If the onException is not triggered on connection failure then the pooled connections will not be properly closed unless the JMS Session
Pool Tester for wrapped connections is active. The JMS Session Pool Tester is automatically created on wrapped connections as long as temporary destinations have not been disabled on the JMS server.
9.1
9.2 MP1
CR280041
When the WLConnection.getReconnectPolicy() method is set to all, JMS CLIENT_ACKNOWLEDGE sessions may sometimes throw an extra LostServerException when session.acknowledge() is called. This occurs after the JMS session has been reconnected to the server.
9.2
 
CR280064
Deploying JMS standalone application modules to a cluster using the Administration Console succeed, but no subdeployments are targeted.
Workaround or solution:
For WebLogic Server 9.2, you must either:
  • Use the Administration Console to target the JMS standalone application module at a single server instance, then reopen the module and configure the targetting for individual subdeployments.
  • Use the weblogic.Deployer tool to target the JMS standalone application module.
9.2
9.2
CR280150
When the WLConnection.getReconnectPolicy() method is set to all, JMS CLIENT_ACKNOWLEDGE sessions do not always throw a LostServerException when session.acknowledge() is called and there are unacknowledged, non-persistent topic messages.
9.2
 
CR282721
Message-Driven Beans and asynchronous bridges listening on secure WebLogic Server queues were encountering the “security has lapsed for this consumer” errors.
This problem has been resolved.
9.1
9.2 MP1
CR284142
Message-sorting in JMS Queue is slow.
This problem has been resolved. Message-sorting performance has been enhanced. However, memory requirements for sorted messages might increase.
9.1
9.2 MP1
CR286386
A java.lang.NullPointerException used to be raised at weblogic.deployment.jms.JMSSessionHolder.toString(JMSSessionHolder.java:411)
This problem has been resolved.
9.2
9.2 MP1
CR286749
Message-driven beans (MDBs) configured to use the connection factory and destinations from a locally configured ForeignJMSServer were not successfully connecting if an MDB descriptor did not include the local provider-url.
This problem has been resolved. MDBs can successfully connect to a local ForeignJMSServer without specifying the provider-url in the MDB descriptor.
9.1
9.2 MP1
CR293497
When using the 8.1 thin JMS client, a weblogic.rmi.extensions.DisconnectMonitorUnavailableException is raised on WebLogic Server 9.1 every time the client disconnects.
This problem has been resolved.
9.1
9.2 MP1
CR297623
The CDSLocalProxy.registerListener() method used to cause a NullPointerException.
This problem has been resolved.
9.2
9.2 MP1
CR303077
CR303729
Deadlock between weblogic.jms.common.CDSLocalProxy and weblogic.jms.common.CDS used to occur with reference to SAF destinations.
This problem has been resolved.
9.2
9.2 MP1
CR291356
CR318634
The functional behavior of the setJMSReplyTo() method in WebLogic Server 9.x was inconsistent with WebLogic Server 8.1 release.
This problem has been resolved.
9.2
9.2 MP2
CR296874
If there was a delay on the request completion between client and server due to an unexpected peerGone or network latency, a temporary halt used to happen when receiving messages even though the topic property -Dweblogic.jms.DisableMultiSender is set to true.
This problem has been resolved.
9.1
9.2 MP2
CR297838
Any failure detected by a distributed topic used to stop the forwarder and would not resume until the JMSServer was restarted.
This problem has been resolved.
9.1
9.2 MP2
CR304094
While the compact command in WebLogic Store administration tool was run all non-store files were removed from the file store directory.
This problem has been resolved.
9.1
9.2 MP2
CR305370
In a Solaris environment, an MDB deployed to a cluster was unable to connect to a non-distributed topic on a different cluster in the same domain.
This problem has been resolved.
9.2
9.2 MP2
CR308085
If any of the servers in the receiver domain went down, the store-and-forward (SAF) queue experienced a hung state due to NullPointerException in weblogic.jms.common.CDS.unregisterDDMembershipChangeListener and weblogic.jms.forwarder.Forwarder.connectTarget.
This problem has been resolved.
9.2
9.2 MP2
CR308685
When sending messages from a WebLogic JMS source queue to a third-party JMS provider such as SonicMQ, the following exception was raised:
javax.jms.JMSException: Message Property cannot be set by a JMS client
This problem has been resolved.
9.2
9.2 MP2
CR309663
When messages are sent to a destination, which was configured with a JMS quota and if that quota was met then messages were inadvertently getting added to the list of Pageable messages. This used to result in a memory leakage because the messages were retained on the list of Pageable messages until the server was restarted.
This problem has been resolved.
9.1
9.2 MP2
CR309927
A failure used to occur while performing Paging I/O if many threads were waiting for Paging I/O to complete and these threads were blocked.
This problem has been resolved.
9.1
9.2 MP2
CR310125
When the JMS producer was repeatedly created and closed during a session, it used to cause a memory leak.
This problem has been resolved.
9.2
9.2 MP2
CR310403
The store-and-forward (SAF) agent in one domain was not forwarding messages to the dynamically created and imported uniform distributed topic (UDT) destination in a remote domain.
This problem has been resolved.
9.2
9.2 MP2
CR312768
Frequent connection and disconnection to the WLS JMS distributed queue by a client application used to result in OutOfMemory exception.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR312184
MDB thread used to deadlock at weblogic.messaging.util.DeliveryList.waitUntilIdle() when using WebLogic Server 8.1 Threading Model -Dweblogic.Use81StyleExecuteQueues=true.
This problem has been resolved.
9.1
9.2 MP2
CR290133
Creating and closing JMS producer or JMS consumer on temporary destinations was resulting in a memory leak.
This problem has been resolved.
9.0
9.2 MP2
CR308023
An error was being raised when MDB deployed on WebLogic Server attempted to connect to a foreign JMS provider using JMS 1.1 Connection Factory.
This problem has been resolved.
9.2
9.2 MP2
CR292132
JMS JDBC store was not getting recovered after database failure and re-connection.
This problem has been resolved.
9.2
9.2 MP2
CR306244
NullPointerException was being raised during CDS debugging from weblogic.jms.common.CDS.getDestinationName() if destination name was absent in the Foreign JMS server JNDI registry.
This problem has been resolved.
9.2
9.2 MP2
CR315390
BMT and non-transacted CMT MDBs used to stop processing messages and messages were left in a pending state when RunTimeException was raised from the onMessage method.
This problem has been resolved.
9.2
9.2 MP2
CR317434
MDB used to stop processing the message after RuntimeException was raised in the onMessage() method.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR331784
Message headers of messages in the server were getting altered after you restarted the server. This was happening because the Name field of the JMSReplyTo property was nullified when the server was restarted.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR340715
MDB was not getting connected to a remote WebLogic Server distributed queue through ForeignJMSServer.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR325933
Deadlocks were detected in JMS when using JRockit JVM build 1.5.0_06-b05.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR314581
There was no option to prevent the delivery counts from being reset when forwarding messages to a new queue.
This problem has been resolved by providing a check box named Reset Delivery Count On Forward in the Configuration > General page for the Distributed and Uniform Distributed queues.
9.2 MP1
9.2 MP3
CR314621
Automatic reconnect for asynchronous consumers was not resetting the message listener and this resulted in the failure of automatic reconnect on consumers and an increase in the connection counters on continued retries.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR321241
The SAF agent sometimes used to stop forwarding messages when any of the receiving servers was restarted.
This problem has been resolved.
9.2
9.2 MP3
CR328936
Memory leak used to occur in CDS code after continuous redeployment of an MDB in a two-domain environment.
This problem has been resolved.
9.1
9.2 MP3
CR329607
CR326535
Memory leak used to occur in CDS code after connection failure between an MDB and a DistributedQueue.
This problem has been resolved.
9.1
9.2 MP3
CR337282
The JMS wrapper code was not using the supplied initial context factory from a ForeignJMSServer and it was always defaulting to weblogic initial context.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR333921
ClassCastException used to raise from the compare() method of BEMessageComparator and this resulted in stuck messages.
This problem has been resolved.
9.2
9.2 MP3
CR343433
The JMS client was hanging in a JMSSession/JMSConnection deadlock on asynchronous consumer disconnect due to a peerGoneException.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR343580
It was not possible to deploy an MDB while connecting to a foreign JMS provider through WebLogic Server foreign server resources configured in a JMS module.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR344517
The messaging bridge used to throw ClassCastException when JMS 1.1 API was used by foreign JMS providers whose QueueConnectionFactory object did not implement ConnectionFactory.
This problem has been resolved.
9.2
9.2 MP3

 

JNDI

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR266862
When a Foreign JNDI connection between two Weblogic Server domains in a cluster is attempted, the server in the calling domain fails to start because the Foreign JNDI Manager service is started prior to cluster services starting.
Workaround or Solution:
The Foreign JNDI Manager service is separated from the other JNDI remote naming services, and a new Foreign JNDI Manager service is started after the cluster is started.
9.1
9.2
CR264754
JMS message consumers will not always reconnect after a service migration when an application’s WLConnection.getReconnectPolicy() attribute is set to all. If the consumers do not get migrated, either an exception is thrown or onException will occur to inform the application that the consumer is no longer valid.
Workaround or Solution:
The application can refresh the consumer either in the exception handler or through onException.
9.2
 
CR285764
Foreign JNDI provider links were being replicated over the cluster. This caused JNDI links to clash on clustered servers.
This problem has been resolved.
9.1
9.2 MP1

 

JSP and Servlet

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR198249
WebLogic Server needs a way for users to pass in custom objects when doing strong authentication.
Workaround or Solution:
A new method assertIdentity was added to weblogic.servlet.security.
ServletAuthentication so that users can pass in a custom object via the AppContext argument for this method. The AppContext is passed onto the security providers.Its the responsibility of the caller to add the request and response objects to the AppContext if required.
9.0
9.1
CR218580
The weblogic.servlet.proxy.GenericProxyServlet class uses the SSL identity WebLogic Server establishes for its SSL connections. Because the application programming interfaces (APIs) are public, applications can use them to impersonate the server (for example by directly using ProxyConnection class).
Workaround or Solution:
Define the following servlet init parameters for the configuration of proxy servlets in the deployment descriptors:
  • KeyStore
  • KeyStoreType
  • PrivateKeyAlias
  • KeyStorePasswordProperties
With this fix, the proxy servlets assume one-way SSL if no KeyStore parameter is specified in the deployment descriptor file.
9.0
9.2
CR246126
The WebLogic Server EL parser did not accept the following EL expressions:
booleanValue ? identifier1 : subexpression
Workaround or Solution:
WebLogic Server has imported new productions for the EL parser to support these expressions.
However, the following EL expression is not accepted:
${true ? true ? identifier1 : identifier2 : identifier3}
If this expression is encountered, then parentheses can be used as a workaround, as follows:
${true ? (true ? identifier1 : identifier2) : identifier3}
9.1
9.2
CR246825
When using ISO-2022-JP, encoding characters written via ServletResponse.getOutputStream().print() are not properly encoded.
Workaround or Solution:
The encoder for ISO-2022-JP maintains internal state which is not getting flushed. Doing an explicit flush on the encoder resolves the issue.
9.1
9.2
CR257620
If a Web application's context-root is /, redeployment in a production environment does not work as expected.
This problem has been resolved.
9.0
9.2
CR257664
Some headers are skipped during processing of proxy headers. After removing an entry from the array list, the counter is not decremented and WebLogic Server skips the entry following the removed entry.
9.0
9.2
CR257711
When in-memory session replication is used during failover there is a possibility for a session loss.This session loss happens because when the primary server goes down, the secondary server detects this event and attempts to promote the session to become primary. However the thread does not have the correct context classloader and therefore the session is lost.
Workaround or Solution:
Set the proper context classloader on the thread.
9.1
9.2
CR258073
The Extended Log Format log file is rotated on server startup even when the <rotate-log-on-startup> element in config.xml is not set.
9.0
9.2
CR258258
When reading sessions from the WL_SERVLET_SESSIONS table, if WebLogic Server gets a deserialization exception due to the version conflict, the old session object is not removed and continues to exist in the database.
9.0
9.2
CR260430
If the NCR characters &#10 and &#13 are present in the Expression Language (EL), the EL parsing fails.
Workaround or Solution:
The EL parser has been fixed to treat carriage-return and line-feed as valid characters.
9.0
9.2
CR262398
Because of the method size limit of 64K imposed by the JVM specification, large JSPs with many tag handler calls (custom actions) can not be loaded at runtime. (The class loading produces a ClassFormat error).
Workaround or Solution:
To resolve this issue, the WebLogic JSP compiler now generates independent private methods for each valid tag handler call, thus ensuring that the size of the main _jspService remains as concise as possible.
9.0
9.2
CR262668
When Host header is missing in the incoming request, the error page was served on the socket muxer thread instead of serving on a separate thread. Moreover, the custom error page, which was mapped in the web.xml file, was not getting displayed.
This problem has been resolved.
9.1
9.2
CR271084
You cannot turn on Servlet class reloading for a domain. The Servlet class reloading can only be turned on in the weblogic.xml file for each web module.
Workaround or Solution:
The ServletReloadCheckSecs attribute was added to the WebAppContainer MBean. The <servlet-reload-check-secs> attribute can be specified in the config.xml files as follows:
<domain ...>
...
<web-app-container> <servlet-reload-check-secs>-1</servlet-reload-check-secs> </web-app-container>
...
</domain>
The value of the <servlet-reload-check-secs> attribute set in the weblogic.xml file for a Web module overrides the value of the attribute set in the config.xml file.
9.2
9.2
CR271953
A bug in SUN JDK1.5.0_04 causes the java.text.ParseException. JDK BugIDs are:6247963,6231602. WebLogic Server 9.2 uses JDK1.5.0_04 by default.
Workaround or Solution:
The bug has been fixed in Sun JDK1.5.0_06.
9.2
9.2
CR274229
When the access.log file was rotated, header information was missing if HTTP logging was set to Extended.
This problem has been resolved. Header information is now added to the access.log during log-file rotation if HTTP logging is set to Extended.
9.1
9.2 MP1
CR275498
“404 Not Found” error used to occur after deploying and starting a new version of an application (replacing an old version that was in Administration mode).
This problem has been resolved.
9.1
9.2 MP1
CR276199
The <jsp:useBean> body gets executed even if the named JavaBean already exists in the scope.
This problem has been resolved.
9.1
9.2 MP1
CR276285
WebLogic Server's HTTP handlers did not support proxying individual URL connections.
This problem has been resolved. Each URL connection can now be proxied separately.
9.1
9.2 MP1
CR276761
While using JRE instead of JDK, WebLogic Server used to raise NoClassDefFoundException.
This problem has been resolved. WebLogic Server can run using JRE instead of JDK with precompiled web applications.
9.1
9.2 MP1
CR278182
SocketExceptions raised during the execution of HTTP requests were being logged in the server log file.
This problem has been resolved. SocketExceptions are no longer logged in the server log file.
9.1
9.2 MP1
CR280017
PathPrepend and PathTrim were not properly getting applied in some cases on the backend server when request is forwarded through plug-ins while using response.redirectURL() or response.encodeRedirectURL() in JSP.
This problem has been resolved. PathTrim is applied only if PathPrepend is undefined or PathPrepend has been applied to the URL on the backend server while calling response.encodeRedirectURL(url) or response.redirectURL(url).
9.1
9.2 MP1
CR280731
JSP compiler does not find boolean accessor methods prefixed with “is” when parsing the <jsp:getProperty> tag.
This problem has been resolved. If a JavaBean class contains boolean accessor methods prefixed with “is”, the JSP gets compiled successfully when calling the <jsp:getProperty> tag for this boolean property.
9.1
9.2 MP1
CR281772
Disabling resource-reload-check-secs was resulting in IOException.
This problem has been resolved. If the static resource file is renamed or moved to another location and resource-reload-check-secs is set to -1 in the deployment descriptor, the browser displays the 404 - Page Not Found error when users attempt to access this page.
9.1
9.2 MP1
CR282101
JSP would fail to compile if a scriptlet included two consecutive percent characters (%%).
This problem has been resolved. JSP compiles successfully even if a scriptlet includes two consecutive percent characters (%%).
9.1
9.2 MP1
CR282865
When a web application was configured in its deployment descriptor to use JDBC session persistence, then while accessing an HTTP session concurrently, WebLogic Server used to raise the “java.sql.SQLException: ORA-00001: unique constraint violated” error.
This problem has been resolved.
9.1
9.2 MP1
CR283060
<jsp-property-groups> did not allow use of a wild card (/*), in the <url-pattern> tag.
This problem has been resolved. <jsp-property-group> allows use of a wild card; for example: <url-pattern>/*</url-pattern>
Note that <jsp-property-group> takes precedence over <servlet-mapping>.
9.1
9.2 MP1
CR283924
Expression language variables exposed by the TAGX caused JSPX compilation to fail.
This problem has been resolved.
9.1
9.2 MP1
CR285842
JSP tag file directive, the name-from-attribute variable was not working with the alias attribute.
This problem has been resolved.
9.1
9.2 MP1
CR286471
Even when url-rewriting-enabled was set to false in weblogic.xml, URL Rewriting was not getting disabled.
This problem has been resolved. If url-rewriting-enabled is set to false in weblogic.xml, it is disabled.
9.1
9.2 MP1
CR287029
WebLogic Server start-up used to fail and raise an exception when a custom HTTP log file (.jar) was used.
This problem has been resolved. If an Extended Log File (ELF) field is specified for Extended HTTP Log and a .jar file is copied to $DOMAIN/lib folder, WebLogic Server starts up successfully; and the ELF field value is written to the log file.
9.2
9.2 MP1
CR287462
When c-ip or s-ip in Extended Logging Format was used with HTTPS, and the HTTP port was disabled, it resulted in a NullPointerException.
This problem has been resolved. c-ip and s-ip in Extended Logging Format work with HTTPS even when the HTTP port is disabled.
9.1
9.2 MP1
CR287986
According to the JSP 2.0 specification, <jsp:output doctype-root-element="books" doctype-system="books.dtd" /> in a JSP 2.0 document (JSPX) results in the output:
<!DOCTYPE books SYSTEM "books.dtd">
In WebLogic 9.2, no DOCTYPE declaration appears in the JSP (Go to View > View Source) despite including the jsp:output tag.
This problem has been resolved. The DOCTYPE declaration appears according to the JSP specification.
9.2
9.2 MP1
CR289254
Attempting to access JSP pages located in a directory caused ClassNotFoundException - if the directory name included included space(s).
This problem has been resolved. JSP pages located in a directory whose name includes spaces can now be accessed.
9.1
9.2 MP1
CR289258
The <jsp:include> directive containing a param value which includes special characters used to ignore the value after the special characters.
This problem has been resolved. If <jsp:include> directive contains a param value which includes special characters, it will pass the correct value of the parameter.
9.1
9.2 MP1
CR290340
JSP Expression Language would cause a NullPointerException while evaluating the expression ${cookie} if the request did not include any cookies.
This problem has been resolved. JSP Expression Language returns an empty list while evaluating expression ${cookie} if the request does not contain any cookies.
9.2
9.2 MP1
CR290433
The JSP parser incorrectly escapes template characters if a JSPX document included text or html content [that is, content-type=text/html].
This problem has been resolved. The JSP parser correctly escapes template characters if a JSPX document includes text or html content.
9.2
9.2 MP1
CR291899
WebLogic Server persistence implementation included JDBC code, and some JDBC drivers have limitations on the amount of data retrieved - given that implementation.
This problem has been resolved. There is no limitation on the amount of data retrieved.
9.1
9.2 MP1
CR292098
Struts used to raise a ClassCastException after changes were made to any servlet in a web application.
This problem has been resolved.
9.2
9.2 MP1
CR292610
WSDL validation used to fail when the WSDL imported a schema which referred to another schema using the redefine mechanism.
This problem has been resolved.
9.2
9.2 MP1
CR293756
WebLogic Server JSP compiler used to recompile a JSP file's antidependent files, leading to an infinite loop.
This problem has been resolved.
9.2
9.2 MP1
CR294343
WebLogic Server JSP compiler was looking at the function name, rather than the actual method in the function-signature call. When the method and function name did not match, the compiler failed to find the method.
This problem has been resolved. JSP compiler now looks for the method, rather than the function name.
9.2
9.2 MP1
CR294519
Session ID was lost when a servlet/JSP included a page that spanned different contexts.
This problem has been resolved. Session ID is not lost across different contexts.
9.2
9.2 MP1
CR294824
When the weblogic.security.Security.getCurrentSubject() method was used to retrieve the authenticated subject from WebLogic Server, an anonymous subject was being returned, and not the authenticated subject.
This problem has been resolved.
9.1
9.2 MP1
CR296954
JSP Compiler was not using Java Beans introspection mechanism to find set methods in Tag Handler class if it implemented a BeanInfo class.
This problem has been resolved.
9.2
9.2 MP1
CR298702
WebLogic Server response was slow when concurrent requests were sent using a .NET client.
This problem has been resolved. WebLogic Server sends “100-continue response” code immediately on receiving Expect Header if auth-method has been defined as FORM-based or undefined in the web application's deployment descriptor.
9.2
9.2 MP1
CR298908
If the connection had been closed by a backend server, an IOException was getting raised while redirecting a request through a proxy server configured on Microsoft IIS.
This problem has been resolved. The request is cached and is retried later when the connection is available.
9.2
9.2 MP1
CR299086
When using client-side content handlers with Message Transmission Optimization Mechanism (MTOM) in JAX-WS RI 2.0, an OutOfMemory error was getting raised.
This problem has been resolved.
9.2
9.2 MP1
CR299589
Inactive sessions are not getting garbage collected when the secondary is invisible to the primary in a cluster: this results in OutOfMemory Error and wrong session count on console.
This problem has been resolved.
9.2
9.2 MP1
CR300154
When auth cookie was enabled with SSL, single sign-on would fail with multiple web applications deployed on the same server.
This problem has been resolved. Single sign-on works with multiple web applications deployed on the same server with SSL and auth cookie enabled, by defining different CookieName values for each application in weblogic.xml. The CookieName will be appended to the secure cookie name. The default value is _WL_AUTHCOOKIE_JSESSIONID (if no CookieName has been defined in weblogic.xml).
9.2
9.2 MP1
CR301784
Incorrect order of locking (object lock, then class lock, and then object lock) was causing thread deadlock when compiling JSP files.
This problem has been resolved.
9.2
9.2 MP1
CR302319
Classloader leak used to occur when deploying multiple versions concurrently.
This problem has been resolved.
9.1
9.2 MP1
CR302520
WebLogic Server's JSP compiler used to raise a ClassCastException when weblogic-application.xml defines both javax.xml.parsers.* and org.apache.* and it is used in conjunction with FilteringClassLoader.
This problem has been resolved.
9.2
9.2 MP1
CR300671
CR311505
Expression Language (EL) was not getting substituted with values while using Struts-EL HTML tag.
This problem has been resolved.
9.2
9.2 MP2
CR309495
If a JSP page contained large HTML static data with unicode strings, java.lang.ClassFormatError used to be raised at run time.
This problem has been resolved.
9.2
9.2 MP2
CR315776
When using weblogic.net.HttpURLConnection to connect to an external system, POST requests to the system used to fail on retry.
This problem has been resolved bye introducing a new flag called http.retryPost. When this flag is set to true, POST requests that fail will be retried successfully, by maintaining post data in an internal buffer.
9.1
9.2 MP2
CR312765
Error used to occur when weblogic.rootDirectory was specified as a UNC path.
This problem has been resolved.
9.2
9.2 MP2
CR310889
CR319845
The request.getContextPath() method used to return incorrect context path when using a Dispatcher to forward the request to a different context.
This problem has been resolved.
9.2
9.2 MP2
CR312007
When JSP used static include of an html file in which document root has been mapped using <virtual-directory-mapping> in the deployment descriptor file, JSP used to fail to compile and raised an error stating that the html file cannot be found.
This problem has been resolved.
9.1
9.2 MP2
CR295174
CR316202
Configuring fallback for authentication methods in web.xml was not working as per the specifications and used to raise an exception.
This problem has been resolved.
9.2
9.2 MP2
CR306727
WebLogic session ID with url-rewriting-enabled parameter enabled in weblogic.xml was not getting logged with URI in access.log file.
This problem has been resolved.
9.1
9.2 MP2
CR307893
CR314119
UnavailableException did not comply with Servlet 2.4 Specifications for permanent and temporary unavailability of the Servlet.
This problem has been resolved.
9.1
9.2 MP2
CR310570
Multiple calls to response.addHeader() with same standard header name used to return only the last header value set to the client.
This problem has been resolved for the standard headers CACHE_CONTROL, ACCEPT-RANGES and PRAGMA.
9.2
9.2 MP2
CR311825
HttpURLConnection was not closing the sockets that goes to CLOSE_WAIT state and resulted in a socket leak.
This problem has been resolved.
9.2
9.2 MP2
CR313210
In a cluster, when the servers were under load while using in-memory session replication, the following exception used to occur:
java.lang.IllegalStateException: HttpSession is invalid
This problem has been resolved.
9.1
9.2 MP2
CR313212
Servlet used to fail with the following exception when HEAD request was used to ping an application.
javax.servlet.ServletException: Original response not available
This problem has been resolved.
9.2
9.2 MP2
CR292238
If a web application did not read the POST data when KeepAlive was disabled, RST packets were sent to the client.
This problem has been resolved.
9.1
9.2 MP3
CR312139
Muxer threads were stuck on remote call processing and this resulted in cluster hang-up under load.
This problem has been resolved.
9.2
9.2 MP3
CR307707
Only those JSP files which have extensions as defined in the <url-pattern> element of the deployment descriptor file were precompiled. JSP pages with extensions other than .jsp and .jspx were not precompiled.
This problem has been resolved.
9.1
9.2 MP3
CR317054
The <jsp:setProperty> tag was not working as expected if the name attribute of this tag was defined in upper case.
This problem has been resolved.
9.2
9.2 MP3
CR328002
SAML Inter-site Transfer Service (ITS) was not accepting requests over user channel if Admin port was enabled.
This problem has been resolved.
9.2
9.2 MP3
CR332253
When making an outbound POST request from WebLogic Server, the value for Transfer-Encoding used to be 'Chunked' instead of 'chunked'. This violated the RFC specification.
This problem has been resolved.
9.2
9.2 MP3
CR322654
ClassNotFoundException used to occur when HTTP Request for replicated WebApp, which has been deployed with versioning, was sent to a server which is neither Primary nor Secondary.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR330240
The auth-filter chain was always being invoked for Certificate Security, leading to an infinite loop in a SAML scenario.
This problem has been resolved. The auth-filter chain is now invoked conditionally only after checking whether the resource is not forbidden and the subject is null. The relogin-enabled flag has been introduced for Certificate Security. If this flag is set to true, the auth-filter chain will be invoked if the resource is not forbidden even if subject is not null.
9.2 MP1
9.2 MP3
CR347152
As per the J2EE specification, the web container must detect and abort any transaction that has not been completed before service method of a servlet returns. WebLogic Server was not detecting the error and the active transaction was not getting aborted.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR349123
Race conditions used to occur while using the jsp compiler, weblogic.jspc, in offline mode, and this resulted in thread deadlock.
This problem has been resolved. An environment variable called BEA_COMPILER_NUM_THREADS has been added. This variable controls the number of threads used, and it must be set to 1 in case of a hang/race condition.
9.2 MP1
9.2 MP3
CR350430
PermGen space was not released between deployments if authentication filters were used.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR352600
When deploying a large webapp that has a large number of servlet mappings, the deployment used to hang while trying to add the servlet mappings.
This problem has been resolved.
9.1
9.2 MP3
CR354048
When you edit a JSP Tag file, the complete webapp used to redeploy.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR355182
If the response code was a 403 error and if the user did not have permissions to the error page, a default 403 page used to return, and an 'infinite loop' error was getting logged.
This problem has been resolved.
9.2 MP2
9.2 MP3

 

JTA

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR186768
In releases prior to WebLogic Server 9.2, when migrating the transaction recovery service from a backup server to the primary server, transaction Synchronization registrations could be lost for transactions that were coordinated by the recovery service being migrated, which included the backup server as a participant in the transaction, when the recovery service was migrated back to the primary server before completing recovery for the migrated transactions.
Workaround or Solution:
Synchronization.afterCompletion callbacks are now invoked for a transaction on a subordinate server when the coordinating server’s transaction recovery service is migrated to the subordinate and back before the transaction completes.
7.0
9.2
CR244381
Last Logging resources cannot be migrated to a new server.
9.0
9.2
CR306499
The remote-client-timeout setting was being ignored for transactional methods.
Workaround or Solution:
RemoteClientTimeout is now supported for transactional methods as well as non-transactional methods. The RMI client timeout is the greater of tx timeout and RemoteClientTimeout if the method is transactional and tx timeout is set. If the method is non-transactional then the RemoteClientTimeout directly applies. The tx timeout is picked from the EJB deployment descriptor (TransactionTimeoutMS) or from JTAMBean.TimeoutSeconds.
9.2
9.2 MP2

 

Java Virtual Machine (JVM)

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR231522
After an upgrade of MedRec from WebLogic Server 8.1 to 9.0 on Solaris, the server crashes with a JVM error.
Workaround or Solution:
To start the upgraded server without crashing it, remove -Xverify:none from the server start command by setting JAVA_OPTIONS="" in the setDomainEnv.sh file after the following line:
. ${WL_HOME}/common/bin/commEnv.sh
9.0
9.2
CR232043
Due to a know Sun Microsystems VM bug (513552), a 1.4 Thin Client Applet cannot contact WebLogic Server 9.0 or later. This is because the VM does not distinguish correctly between a client and a server connection. The VM creates a server-type connection and caches it. It then attempts to make a client-type connection, finds the cached connection and tries to use that, but then encounters an error because clients are not allowed to use server connections.
Workaround or Solution:
None. This issue must be resolved by Sun Microsystems.
9.0
 
CR305677
In an HP-UX environment, large applications containing Beehive and WebLogic controls may run out of memory.
The following workarounds are recommended:
  • Build applications with 25% more memory.
  • Build applications in 64-bit mode of the Virtual Machine (using -d64 switch).
  • Build applications after doubling the value of the MAXDSIZ kernel parameter.
9.2 MP1
 

 

Monitoring

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR230861
Large number of rotated log files result in a slower log file rotation process. For example: if there are 1000 rotated files, the log file rotation would take a couple of seconds.
Workaround or Solution:
Log file rotation has been optimized to reduce the time for the log rotation to half its old value. Even so, the rotation time is still proportional to the number of rotated files. Therefore, it is recommended to limit the number of rotated files in one of the following ways:
  • Configure the Log MBean to delete files on rotation, keeping a fixed number on disk
  • Manually backup the log files to another location
9.0
9.2
CR242802
When a view deletion is initiated, the user does not have an opportunity to cancel the operation nor a way to restore such a view. Therefore, it is possible to accidentally delete a view.
Workaround or Solution:
An Undelete View option is now provided, which restores the view which was last deleted last. Note that if multiple views are deleted, only the last one can be restored. Similarly, when custom metrics are deleted, the Undelete Custom Metric option restores the custom metric which was last deleted. If multiple custom metrics are deleted, only the last one can be restored.
This functionality allows deleted custom views and custom metrics to be restored in a limited manner.
9.0
9.2
CR248745
If custom class attributes are found in an input class, the libraries used by the WebLogic Diagnostic Framework (WLDF) Instrumentation engine assume that they may have hidden dependencies on class contents. Modifications to such classes may render them invalid. Therefore, the WLDF Instrumentation engine avoids modifying this type of class
Any attempt to instrument this type of class results in a log message (MSGID: 320136), of the form:
Class class-name could not be instrumented, due to reason: reason
9.1
9.2
CR256294
In releases prior to WebLogic Server 9.1, the XML output exported by WLST commands exportDiagnosticDataFromServer() and exportDiagnosticData() specified encoding=utf-8. However, the data was actually written with the default JVM encoding.
 
9.2
CR261367
When pop-up windows are created for context menus or tool tips and they cross the Applet frame boundary, JFX/Swing uses heavy weight windows. It is a Java security requirement that such windows are clearly identified. In this case, Swing shows the caption Java Applet Window at the bottom of the pop-up window.
This function works as expected, as per security requirements.
9.2
9.2
CR262591
The instrumentAll and instrumentApps switches in the startup scripts generated by the Domain Wizard are obsolete and do nothing. However, the new switch to turn on hot-swap is not incorporated.
Workaround or Solution:
The startup scripts include a new switch enableHotswap that enables code hot-swap.
Code hot-swap can be enabled using switches provided by generated startup scripts. When used along with an enabled instrumentation system in the configuration, application classes can be reinstrumented with updated instrumentation configuration without requiring application redeployment.
9.2
9.2
CR263366
When execute queues are used in the style defined in WebLogic Server 8.1, the ThreadPool runtime in WebLogic Server 9.1 does not exist. The Diagnostic Dashboard assumes the ThreadPool runtime always exists and throws a NullPointer exception.
Workaround or Solution:
WebLogic Server checks for the existences of the Thread Pool runtime, JMS, and the Work Manager before creating a custom view in the Diagnostics Dashboard.
9.1
9.2
CR263953
The @operation tag was deleted from the WLDFWatchJMXNotificationRuntimeMBean. This change is intentional, but it could break existing JMX code.
Workaround or Solution:
Remove all occurrences of the @operation tag from your JMX code.
9.2
9.2
CR306143
CR316357
Due to log file rotation, there were occurrences of blocked lock chains and rapid increase in the number of threads.
This problem has been resolved.
9.2
9.2 MP2
CR323470
Memory leak of instrumentation scope was observed due to failed deployments that used embedded instrumentation scopes. This resulted in failure of further attempts to deploy the application.
This problem has been resolved.
9.2
9.2 MP3
CR341710
CR352295
A java.lang.NullPointerException used to occur if an application tried to log a message using weblogic.logging.ConsolFormatter, which was instantiated using the default constructor.
This problem has been resolved.
9.2 MP1
9.2 MP3

 

Node Manager

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR263442
Managed Server was unable to start from Console when NodeManager is started by the root user and Managed Server uses post-bind-UID attribute.
This problem has been resolved.
9.1
9.2
CR269421
The Managed Server becomes defunct if it is shut down abruptly through Node Manager on Red Hat Enterprise Linux 3.0-1 because Node Manager ignores the SIGCHLD command, which is not POSIX-compliant.
Workaround or Solution:
The code has been made POSIX-compliant for Linux OS i686 only because the problem did not occur on any other UNIX operating systems. As a result, the Managed Server processes now exit cleanly and do not become zombie processes in Linux.
9.1
9.2
CR278571
The ownership of stdout/stderr files assigned by command line arguments -Dweblogic.Stdout and -Dweblogic.Stderr remained as root even when a managed server was started from NodeManager, using the post-bind-UID/Post-bind-GID attributes.
This problem has been resolved.
9.1
9.2 MP1
CR286336
When a WebLogic Server domain is re-created, a new domain salt file is created and the NodeManager password is encrypted using the new domain salt. However, NodeManager used to cache the domain salt and the NodeManager password and failed to authenticate requests for starting managed servers for the re-created domain.
This problem has been resolved. NodeManager stores the timestamp of the respective domain salt files for comparison and re-loads them in case it has been modified.
9.2
9.2 MP1
CR305722
Managed Server was unable to start from Console due to an error in the wlscontrol.sh script file. Using grep argument with commands in wlscontrol.sh returned incorrect domain entry from nodemanger.domains file.
This problem has been resolved.
9.2
9.2 MP2
CR330869
CR334235
When a $CLASSPATH variable was specified in the remote-start arguments when starting a WebLogic Server instance using Node Manager, the variable was not being replaced with the actual value.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR343866
When Node Manager was restarted, the timestamp was getting added to the beginning of the nodemanager.properties file on every restart. This caused the file to grow very large in size.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR347774
Node Manager did not use a socket timeout value on the connection to the WebLogic Server and the socket used to hang for a period specified by the OS TCP timeout. As a result, the Administration Console used to hang when managed servers were partitioned from the network on platforms such as Linux.
This problem has been resolved.
9.2
9.2 MP3
CR355437
Upgrade installer used to fail with IOException due to an error in lock implementation.
This problem has been resolved.
9.2 MP2
9.2 MP3

 

Operations, Administration, and Management

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR235233
The WebLogic Scripting tool (WLST) deploy command has no option to upload an application.
Workaround or Solution:
WLST can now upload application as part of the deploy, distribute, redeploy, or update commands.
   
CR243767
WLST does not have syntax that allows a partial redeploy of an application.
Workaround or Solution:
A delta option was added to the WLST redeploy command. For example:
redeploy("MyApp", block='true', delta=files)
The delta key/value pair can be used to specify the files that should be redeployed.
9.1
9.2
CR254835
Managed Servers perform schema validation of the configuration files (config.xml and system resource files) at startup. This validation prevents the Managed Server from being at an earlier version and from participating in a rolling upgrade.
Workaround or Solution:
Managed Servers no longer perform schema validation on the configuration files. The configuration files are always validated on the Administration Server before download to the Managed Servers.
Managed Servers ignore schema validation errors from the configuration files. When running a Managed Server in MSI mode and using manually edited configuration files, ensure that the config.xml and system resource files are valid.
9.2
9.2
CR255545
On Windows, WebLogic Server fails with an IO exception when a -Dweblogic.RootDirectory property containing an / character is specified.
9.0
9.2
CR256308
If the name of the Configuration MBean contain non-ascii characters, the WLST configToScript command creates a py file that fails with syntax errors in the create and set attribute methods.
Workaround or Solution:
This problem has been resolved. Ascii names should look the same. Non-ascii character names will be hex, but the comments should have the non-ascii name.
9.1
9.2
CR257112
System resource files for JMS, JDBC, and diagnostics are written with an invalid schema location. The schema location is set to that of the domain (config.xml) instead of one specific to the system resource definitions.
Workaround or Solution:
System resource files now contain the correct schema location.
9.1
9.2
CR257774
A Managed Server is booted in MSI mode if the Administration port specified does not have HTTP enabled or HTTP Tunnelling Enabled. The getAdminHttpURL() API constructs the URL based on one port. Therefore, the Managed Server can return an HTTP URL with a port on which HTTP is turned off.
Workaround or Solution:
A fix was added to the getAdminHttpURL() method that constructs a URL based on an algorithm that looks at all network channels, in the sequence ADMIN-Http-Https, in order to find a port that has Http Enabled. This algorithm ensures that a Manager Server can connect to an Administration Server using the URL returned by the API.
9.0
9.2
CR258089
The WLConfig utility nested creates are creating nested MBeans at the domain level.
Workaround or Solution:
A nested create in WLConfig now creates new MBean at the nested level instead of at the domain level.
9.2
9.2
CR260785
The weblogic.Deployer command failed with the following security error:
user anonymous does not have access to administrator port
On the server side, the check for administration port was made before the identity for this request was set.
This problem has been resolved. The weblogic.Deployer command can now be used when the administration port is enabled.
9.2
9.2
CR262101
ClassNotFound exceptions for MBean implementation classes can occur if you are querying Jolt or JRockitRuntime MBeans by using the MBeanTypeService.
Workaround or Solution:
The MBeanTypeService can be used to query MBeans when the implementation class can not be found.
9.2
9.2
CR262187
The SSL Listen Port attribute can not be changed to 7001 even if the non-SSL Listen port is not defined as 7001.
Workaround or Solution:
The validation of the SSL Listen port occurs after a save or validate occurs.
9.1
9.2
CR262787
When executing a cd command to a non-existent directory, WLST throws an exception and incorrectly resets the current directory to the root of the tree.
Workaround or Solution:
When an error occurs in the cd command, the current directory remains unchanged and is not reset to root.
9.1
9.2
CR262853
If run multiple times, clients can create duplicate instance of security MBeans. This action results in the following exception:
IllegalArgumentExceptions - "Registered more than once instance with the same objectnName"
Workaround or Solution:
When creating duplicate MBeans, clients receive failures as expected.
9.1
9.2
CR263323
The WLConfig utility does not fail when creating a duplicate MBean.
Workaround or Solution:
The Ant builds fails as expected when creating a duplicate MBean.
9.1
9.2
CR265447
The WLST activate command times out and never completes if a JDBC module exception is thrown. In addition, the underlying JDBC module exception is not returned to the caller due to the activation timeout.
Workaround or Solution:
The WLST activate command fails as expected. The underlying exception is returned and displayed correctly to the user.
9.1
9.2
CR266452
After calling Helper.getAdminMBeanHome, a JMX client fails with a NoAccessRuntimeException exception when creating a JDBC Connection Pool. The detailed exception message indicates that access is not allowed for the anoymous user (a Subject with no Principals).
Workaround or Solution:
JMX clients now run with the correct user instead of the anoymous user.
9.1
9.2
CR270856
When called by an QueryCacheRuntime MBean, getWebLogicObjectName fails with a java.lang.AssertionError error. The detailed exception message is as follows:
A valid parent for type QueryCacheRuntime does not exist
9.2
9.2
CR272763
The ConfigToScript command generates a script that does not contain deployment information. When executed, the generated script does not encrypt sensitive attributes.
Workaround or Solution:
Encrypted attributes are no longer in clear text in the config.xml file. Applications should be deployed as part of running the generated script.
9.1
9.2
CR274714
A serial version uid mismatch error occurs when running WebLogicMBeanMaker or weblogic.Upgrade on the AIX operating system. The detailed exception is as follows:
java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
Workaround or Solution:
WebLogicMBeanMaker and weblogic.Upgrade can now be used on the AIX operating system.
9.1
9.2
CR275912
If non-dynamic changes are made to a domain configuration, then an application is added (e.g., MyApp), and then the non-dynamic changes are activated, a Management Exception is thrown: [Deployer:149001] No application named 'MyApp' exists for operation start.
Workaround or Solution:
The error message occurs because when an edit is made to a non-dynamic configuration setting, no edits to dynamic configuration settings will take effect until after a server restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated. Since the application has not been added to the configuration, the application cannot be activated and the activate fails with the Management Exception.
For more information on dynamic versus non-dynamic changes, see Managing Configuration Changes in Understanding Domain Configuration.
9.2
 
CR279247
WebLogic Scripting Tool's configToScript() command was not encrypting the values of some encrypted attributes such as the domain security credential in the generated script.
This problem has been resolved.
9.1
9.2 MP1
CR286778
When constructing MBean names for some types of run-time MBeans (NonXAResourceRuntime, TransactionNameRuntime, and TransactionResourceRuntime), ObjectName creation used to fail because the parent MBean type could not be determined from the tree.
This problem has been resolved.
9.1
9.2 MP1
CR292988
If the URL's used in WebLogic Scripting Tool (WLST) commands contained protocol names such as T3S or HTTPS in machine- or listen-addresses, WLST would misinterpret these URLs and incorrectly substitute the protocol with these machine names.
This problem has been resolved.
9.1
9.2 MP1
CR293298
ForeignJMSServerMBean.JNDIProperties should not include the value of the “JNDIPropertiesCredentialEncrypted” attribute, because it is confidential. It should not be stored on disk in clear text: it should be accessible only to privileged WebLogic users.
This product change has been implemented. The value of the “JNDIPropertiesCredentialEncrypted” attribute is stored in encrypted form; user credentials (with appropriate privileges) are required to retrieve the value from WebLogic Server.
9.2
9.2 MP1
CR298371
When deploying applications, the system was raising a weblogic.utils.jars.JarFileUtils$PathLengthException because the string specifying the path of the file (which was being extracted) was too long.
This problem has been resolved.
9.2
9.2 MP1
CR273310
If Administration Server went down and restarted at a different URL, Managed Servers connected to the Administration Server were getting disconnected.
This problem has been resolved.
9.1
9.2 MP2
CR280268
LogFileRotation was not working properly when rotated by time and if the rotation interval was 24 hours. Formatted files were always being rotated to the directory where the log file was stored instead of being rotated to the specified rotation directory.
This problem has been resolved.
9.1
9.2 MP2
CR285163
CR311254
Users in the Operators group were not able to start or stop Managed Servers.
This problem has been resolved.
9.2
9.2 MP2
CR288501
The Python file generated after using the configToScript() command used to include invalid methods.
This problem has been resolved.
9.1
9.2 MP2
CR289255
Using the WebLogic MBeanMaker utility to build MBean Jar File (MJF) without WebLogic installation resulted in compilation errors.
This problem has been resolved.
9.2
9.2 MP2
CR294424
Default JMX policies on weblogic.management.runtime.JMSDestinationRuntimeMBean cannot be modified using Administration Console.
This problem has been resolved.
9.2
9.2 MP2
CR297149
CR313555
When you click on a deployed library in Weblogic Administration Console, javax.management.RuntimeOperationsException was being raised if that library was referenced by any deployed application.
This problem has been resolved.
9.2
9.2 MP2
CR302689
CR316746
When multiple threads call WebLogic Timer’s addNotification() or removeNotification() methods, ConcurrentModificationException was being raised.
This problem has been resolved.
9.2
9.2 MP2
CR305094
The command line server startup option -Dweblogic.management.startupMode was not being handled properly, preventing startup in ADMIN mode.
This problem has been resolved.
9.2
9.2 MP2
CR313958
The weblogic.management.scripting.utils.WLSTInterpreter tool used to raise NullPointerException when the relative path was provided for weblogic.jar file.
This problem has been resolved.
9.2
9.2 MP2
CR322252
CR359054
Timer MBean continued to emit notifications to all its registered listeners even if all notification entries for the Timer MBean were updated or removed.
This problem has been resolved.
9.2
9.2 MP3
CR326834
NullPointerException used to raise with the java.io.ObjectOutputStream$BlockDataOutputStream.getUTFLength()method when serializing a WLLogRecord object to publish the log entries to the domain log.
This problem has been resolved.
9.1
9.2 MP3
CR328281
When using WLST’s configToScript()command to generate the WLST script config.py, the script did not contain any deployed library related content.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR342653
The RemoteJNDIName and LocalJNDIName attributes of ForeignDestinationMBean were not being displayed by WLST.
This problem has been resolved.
9.2
9.2 MP3
CR347048
CR351408
WebLogic Server bootup used to delay when using a JDBC data store to record WLDF data. This delay occurred due to the time taken for the execution of a JDBC query when a large amount of data existed in the JDBC data store.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR317408
CR348913
WLST deploy()command ignores the stageMode argument when any options other than the arguments appName, path, targets, stageMode, or planPath were specified in the command.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR330537
CR355612
Garbage collection used to occur continuously because too many secondary sessions were created on certain instances.
This problem has been resolved. Now preferred secondary groups specified in theconfig.xml file are honored while selecting the secondary servers for session replication.
9.2
9.2 MP3
CR348647
When an ALSB domain was created from an ALSB template, you were not able to navigate within the project browser and the following error used to occur:
Message: The current login role is not authorized to use the console action: "/ViewProject"
Type: com.bea.wli.common.base.SBConsoleAccessException
This problem has been resolved.
9.2 MP1
9.2 MP3
CR351430
Memory leak of javax.management.ObjectName objects on the Administration Server used to cause OutOfMemory exception on the Administration Server.
This problem has been resolved.
9.2 MP2
9.2 MP3
CR357968
After downgrading WebLogic Server 9.2 MP3 to previous releases such as 9.2 MP2, 9.2 MP1, and 9.2, the Summary of Servers table on the Administration Console used to display wrong status for Managed Servers. The status used to be displayed as ‘Shutdown’ when they were actually running.
This problem has been resolved.
9.2 MP3
9.2 MP3

 

Plug-Ins

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR322950
HttpProxyServlet used to read response from the backend even after client closes the connection.
This problem has been resolved.
9.2
9.2 MP2
CR329740
There was an edge case in reading the response from WebLogic Server when using SSL between plug-in and WebLogic Server, which was leading to a mismatch in the bytes expected by the plug-in and the bytes already read by Certicom's SSL implementation.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR330414
The plug-in was adding Content-Length = 0 to headers of requests that has no content. This resulted in a performance degradation since WebLogic Server would send back a header with Connection = Close and connections would not be recycled.
This problem has been resolved.
9.2
9.2 MP3
CR338887
A potential crash scenario existed for long URLs in the ISAPI plug-in.
This problem has been resolved.
9.2 MP2
9.2 MP3

 

Protocols

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR257895
The T3 maximum message size could not be changed on clients.
Workaround or Solution:
The T3 message size can be changed on clients using the -Dweblogic.MaxMessageSize flag.
9.1
9.2
CR288771
Memory leak with JMS thin client when running load tests: Objects were not being released, causing “OutOfMemory” errors on both the client and server.
This problem has been resolved.
9.2
9.2 MP1
CR298435
CORBA strings encoded in extended UTF-8 character set, wherein a high bit was set, were not correctly parsed by the output stream handler.
This problem has been resolved.
9.2
9.2 MP1
CR301140
Newly added runtime attributes in WebLogic Server 9.0 releases were incorrectly added to the SNMP MIB resulting in the values not being available through SNMP APIs.
This problem has been resolved.
9.1
9.2 MP2
CR336185
The flag, http.retryPost, introduced in WebLogic 9.2 for CR315776 has been renamed to http.bufferPostForRetry. When the flag http.bufferPostForRetry is set to true, post requests will use a buffered output stream ensuring that the data is available for retry on failed requests.
9.2 MP1
9.2 MP3

 

RMI

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR316637
A ClassCastException was being raised from RMI during engine startup after the server was shutdown.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR333686
Memory leak used to occur with the distributed garbage collection service.
The java.rmi.server.Unreferenced.unreferenced method in the client code on the server side was not being invoked as expected once all RMI clients were disconnected and the remote object was unbound from the RMI service.
This problem has been resolved.
9.2
9.2 MP3

 

Samples

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR226622
The ../xml/stax example contains two files with the same root but different extension: StreamParser.java and StreamParser.jsp. The samples viewer build, however, creates just one corresponding HTML file, rather than two for each type of file. In this case only the StreamParser.jsp file has an equivalent HTML file; the StreamParser.java file does not.
The problem occurs because of a setting in the build.xml file that controls the behavior of java2html to generate the files for the documentation.
When using java2html, the useShortFileName="true" parameter crops off the file extensions for the source files to create the file names for the HTML output files. If two files have the same name and different file extensions, whichever html file is generated last will overwrite previous ones.
Workaround or Solution:
Set the useShortFileName parameter to "false". This setting generates HTML files with the file extensions included in the name. The drawback to this solution is that every link that points to the HTML output file needs to be revised, regardless of whether the files in question were affected by the bug.
9.0
 
CR255774
The ant target for WebLogic Server tries to open the default browser which may not be configured.
Workaround or Solution:
The user needs to make sure the default browser is configured and can be opened.
9.1
9.2

 

Security

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR182523
Information on how to configure domains to enable inter-domain transactions (that is, all participating domains run on WebLogic Server 9.x, 8.x, 7.x, and 6.x domains or a combination of 9.x, 8.x, 7.x and 6.x) is incorrect in the Administration Console Help.
Workaround or Solution:
The information required to configure domains to enable inter-domain transactions is located online. See Configuring Domains for Inter-Domain Transactions in Programming WebLogic JTA.
9.0 Beta
9.2
CR231321
The option, -Dweblogic.system.StoreBootIdentity, only works if the appropriate server security directory exists. This directory is usually created by the Configuration Wizard or upgrade tool.
However, the appropriate server security directory could be absent in domains checked into source-control systems.
9.0
 
CR255590
The XACML providers convert passed-in default Entitlement expressions into XACML documents. For the Access occurs after and Access occurs before conditions, the conversion is not working properly.
This problem has been resolved.
9.1
9.2
CR261054
WebLogic Server's LDAP directory was not being backed up according to the back-up schedule configured on the server.
This problem has been resolved.
9.0
9.2 MP1
CR270529
If a boot.properties file was in the WebLogic Server domain root directory, WebLogic Server would copy it to the security directory and then delete it from the domain root directory.
This problem has been resolved. WebLogic Server checks whether the weblogic.system.BootIdentityFile property indicates that the boot.properties file is in the domain root directory. If the file exists in that directory, it is not copied to the security directory and not deleted from the domain root directory.
9.1
9.2
CR274400
Help text for time/date format is based on en/en-us locale while parsing logic is based on currently specified locale.
Workaround or Solution:
The Help text is updated to show time/date formats based on current locale.
9.2
9.2
CR291067
In WebLogic Server 9.0, the security framework was modified to write AuditAtnEventV2 authentication events. However, audit providers implemented on WebLogic Server releases prior to WebLogic Server 9.0 sometimes used to encounter binary compatibility issues because they were not implemented to process AuditAtnEventV2 events.
This problem has been resolved. Custom audit providers written to pre-WebLogic Server 9.0 interfaces can be configured and executed on WebLogic Server 9.2 installations.
Further, two new interfaces, AuditProviderV2 and AuditChannelV2, are added to WebLogic Server 9.2 and must be implemented (by modifying the pre-WebLogic Server 9.0 custom audit providers) in order to receive AuditAtnEventV2 events.
Pre-WebLogic Server 9.0 custom audit providers who implement the already existing AuditProvider and AuditChannel interfaces can continue to receive AuditAtnEvent events from the security framework, even if the new interfaces are not implemented.
9.0
9.2 MP1
CR294340
In some cases, WebLogic Server would raise a weblogic.management.utils.CreateException and a netscape.ldap.LDAPException: error result (68) exception - to WebLogic Portal running on a managed server. This used to occur because of a timing issue between the managed server and its administration server regarding a security policy change: in this case, the creation of a new role. When this situation occurred, the managed server would attempt to create the new role in the WebLogic Server-embedded LDAP even though it already existed.
This problem has been resolved. WebLogic Server detects that the role exists and does not try to create it again in the embedded LDAP.
9.2
9.2 MP1
CR294793
In some cases, the authentication of a web application user would not audit the context of the authentication call.
This problem has been resolved. The audit log contains the context of the web application authentication.
9.2
9.2 MP1
CR298006
In some cases, a JAAS login module might not receive context as documented.
This problem has been resolved. JAAS login module will now receive any context available at the time the login module is called.
9.2
9.2 MP1
CR300742
Changes made to LDAP policy on a managed server were being saved locally if the administration server was not available. But the changes could not be updated to the administration server or distributed to other managed servers, after restarting the administration server.
This problem has been resolved. An AdminServerListener checks the availability of the administration server before the policy modification operations are saved on a managed server. When the administration server is not available, an error is displayed and the policy modification operation fails. This ensures that the managed servers have synchronized LDAP policy data.
9.2
9.2 MP1
CR296197
If a large number of roles are involved in the domain, the WebLogic Server policy cache may grow to a size greater than the JVM configured maximum size and result in an OutOfMemory exception.
Workaround or Solution:
To avoid the exception, you can increase the JVM maximum heap setting or decrease the WebLogic Server policy cache maximum size default of 5000 entries. To adjust the WebLogic Server policy cache, set the weblogic.security.ldapPolicyStoreCacheCapacity property to the desired size.

Note: For versions greater than WebLogic Server 9.2, set weblogic.security.policyStoreCacheCapacity property.
9.1
9.2 MP2
CR296354
User was unable to set the property java.security.auth.login.config programmatically.
This problem has been resolved.
9.2
9.2 MP2
CR302748
Replication from Managed Servers to Administration Servers used to fail when using the administrative channel.
This problem has been resolved.
9.2
9.2 MP2
CR305399
During automatic migration if Managed Server started when Administration Server was down, there was a delay in Managed Server startup. The timeout duration on successive attempts to contact the Administration Server used to result in the delay of the Managed Server startup.
Workaround or Solution:
To minimize the delay of Managed Server startup set the -Dweblogic.security.embeddedLDAPConnectTimeout property on Managed Server to specify an appropriate duration for the connection timeout in seconds.
9.2
9.2 MP2
CR318549
WebLogic client was unable to connect to the server using userConfigFile and userKeyFile, if these files contained any non-ascii characters.
This problem has been resolved.
9.2
9.2 MP2
CR319378
The following note is missing in WebLogic Server 9.2 javadocs for ActiveDirectoryAuthenticatorMBean interface.

Note: You cannot use changeUserPassword method in ActiveDirectoryAuthenticatorMBean interface to change the password for Active Directory users.
9.2
 
CR262469
Under certain circumstances, the use of a proxy server was not being detected by the default SSL hostname verifier and the SSL connection trough proxy used to fail with an error.
This problem has been resolved.
9.1
9.2 MP3
CR297664
CR335068
WebLogic Server 9.2 failed to start after rebuilding and installing a custom authentication provider that had deployed successfully on WebLogic Server 8.1.
In WebLogic Server 9.2 if you had two or more PrincipalValidators configured in a security realm which validated the same base Principal type or any derivations of a common base Principal type, the server would abort starting.
This problem has been resolved. Though a one-to-one relationship between PrincipalValidators and direct base principal types is enforced, as it was in prior releases of WebLogic Server, a realm can have a PrincipalValidator which validates a type that is a sub type of the Principal type associated with another PrincipalValidator.
9.2
9.2 MP3
CR336942
There used to be a large memory usage during XACML policy caching.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR326106
The PrincipalValidator service used to drop custom PrincipalValidator with different base principal class type and failed to start WebLogic Server.
This problem has been resolved.
9.2
9.2 MP3
CR325523
When the Use Retrieved User Name as Principal attribute was set to true for the Open LDAP Authenticator Provider and if the User Name attribute could not be obtained from the user DN, the subsequent attempt to search LDAP for the user entry for obtaining the User Name attribute would fail.
This problem has been resolved.
9.2
9.2 MP3
CR324370
Group Membership Lookup Hierarchy Caching provided by the SQL Authenticator was not working properly. A problem with detection of cyclical group membership definitions for DBMS authentication providers was preventing all groups of a member's membership hierarchy from being placed in the membership cache and in the Subject.
This problem has been resolved.
9.2
9.2 MP3
CR340025
Under certain circumstances, the server would select a ciphersuite from the SSL client supported ciphersuite list that uses a null cipher for SSL communications.
This problem has been resolved. Administrators can now disable the use of null ciphers during SSL communications with SSL clients.
9.2 MP1
9.2 MP3

 

Spring Framework on WebLogic Server

Two versions of the Spring Framework are certified for this release of WebLogic Server: 1.2.8 and 2.0. The following two tables list the known and resolved issues for the two versions separately.

Spring 1.2.8

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR242675
A NullPointerException occurs in the RMI classloader.
This problem has been resolved.
9.0
9.1
CR236708
An Antlr conflict exists between Hibernate 3 and WebLogic Server.
Workaround or Solution:
Place Antlr2.7.5.jar before weblogic.jar in your CLASSPATH.
8.1SP05, 9.0
9.2
CR242923
The T3 runtime cannot decode class descriptors that contain primitive types.
This problem has been resolved.
9.0
9.1
CR242883
The IIOP runtime cannot decode class descriptors that contain primitive types.
This problem has been resolved.
9.0
9.1
CR237532
A WebApp classloading problem exists with the Spring Framework.
This problem has been resolved.
8.1SP05, 9.0
9.1
CR241195
Updating a record in the Spring Pet Clinic sample application can result in the following error:

java.lang.IllegalStateException: Cannot access session scope since the

requested page does not participate in a session. at

weblogic.servlet.jsp.PageContextImpl.getAttribute(PageContextImpl.java:273)

at javax.servlet.jsp.jstl.core.Config.get(Config.java:145) at

javax.servlet.jsp.jstl.core.Config.find(Config.java:393) at

org.apache.taglibs.standard.tag.common.fmt.TimeZoneSupport.getTimeZone(TimeZoneSupport.java:140)

Workaround or Solution:
Comment out the first line in the includes.jsp file.
9.0
9.2
CR244683
HP-UX requires jdk150_01, not jdk150_03.
Workaround or Solution:
In the medrec-spring directory, replace jdk150_03 with jdk150_01.
9.0
9.2
CR244693
MedRec-Spring logout functionality does not work when you access MedRec-Spring from a remote machine.
Workaround or Solution:
Do not access the MedRec-Spring application from a remote machine and do not use localhost for request redirection.
9.0
9.2
CR244691
The Spring extension to the WebLogic Administration Console only supports Web applications (.war) files and cannot be used to monitor Spring Beans in non-.war files (such as in MedRec-Spring).
9.0
9.2
CR243957
When using CTRL-C to shut down WebLogic Server, a shutdown exception may occur when destroying the bean domainMBeanServerConnection.
Workaround or Solution:
Use the flag -Dweblogic.slc=true in order to determine when domainRuntimeServerService is started and stopped.
9.0
9.2
CR280985
You cannot autodeploy the countries_mbeans.war application by copying it to the autodeploy directory of the WebLogic Server domain directory. The countries_mbeans.war Web application is a Spring test extension application.
Workaround or Solution:
Deploy the countries_mbeans.war Web application using the WebLogic Server Administration console rather than autodeploying it.
9.2
 
CR301115
Running the unit tests in the Spring Pet Clinic sample application can result in the following error:

Could not find a valid processor version implementation from weblogic.xml.jaxp.RegistrySAXTransformerFactory

Workaround or Solution:
Define the XML parser class by adding the following entries to the $java.home/lib/jaxp.properties file:
  • javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
  • javax.xml.xpath.XPathFactory=org.apache.xpath.jaxp.XPathFactoryImpl
  • javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
  • javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
9.2
 
CR300748
An exception occurred while accessing tiles-samples deployed to WebLogic Server 92.
9.2
 

Spring 2.0

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR280985
You cannot autodeploy the countries_mbeans.war application by copying it to the autodeploy directory of the WebLogic Server domain directory. The countries_mbeans.war Web application is a Spring test extension application.
Workaround or Solution:
Deploy the countries_mbeans.war Web application using the WebLogic Server Administration console rather than autodeploying it.
9.2
 
CR301115
Running the unit tests in the Spring Pet Clinic sample application can result in the following error:

Could not find a valid processor version implementation from weblogic.xml.jaxp.RegistrySAXTransformerFactory

Workaround or Solution:
Define the XML parser class by adding the following entries to the $java.home/lib/jaxp.properties file:
  • javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
  • javax.xml.xpath.XPathFactory=org.apache.xpath.jaxp.XPathFactoryImpl
  • javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
  • javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
9.2
 
CR308954
After deploying the Spring MedRec application to WebLogic Server, and then using Control-C in the command window from which you started WebLogic Server to shut it down, you might see the following exception in the server log:

java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.

9.2
 

 

Upgrade

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR252571
EJBException occurs when you upgrade the petstore domain from WebLogic Server 7.0.x to 9.x.
Workaround or Solution:
Prior to upgrading the domain, edit the config.xml file to ensure that the xa-connection-factory-enabled element is set to true for the MyTopicConnectionFactory.
9.1
 
CR256082
The JWS in WebLogic Server 9.2 does not support the callback protocol in WebLogic Workshop 8.1. Therefore, a 9.2 JWS cannot callback to an 8.1 WebLogic Workshop application or an 8.1 WLI JPD. Also, a 9.2 JWS client cannot receive callbacks from an 8.1 WLW application or an 8.1 WLI JPD.
Workaround or Solution:
Front-end the client side call with a 9.2 Service Control.
9.2
 
CR262360
A Service Control callback to JWS from JPD not supported. JWS only understands 9.x-style callbacks. The JPD or 8.1 services only support 8.1-style callbacks.
Workaround or Solution:
Front end a JPD with a JWS and PC (only valid for JPD 9.x endpoints) or make your endpoint service synchronous and use polling (valid for 8.1 services and JPD 9.x endpoints).
9.2
 
CR265099, CR268712
Weblogic Workshop 8.1 supported returning the java.util.Map type from Web Service operations. The runtime provided a Workshop specific serialization of the Map to and from XML. The schema for that serialization was included in the WSDL for the Web Service.
In WebLogic Server 9.2, the java.util.Map type can no longer be returned from Web Service operations.
Workaround or Solution:
Provide an application-defined type that supports the key/value features provided by java.util.Map. That type must conform to JAX/RPC Java<->XML Serialization rules. If the application-type is going to contain subclasses of type key or value type, then the weblogic.jws.Types annotation must be used to specify the types that could be contained at runtime. WebLogic Web Services (and their clients) that previously returned a java.util.Map will have to be manually updated to use this new application-defined type.
   

 

Web Applications

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

 

Web Services and XML

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR082116
Require a mechanism to validate incoming SOAP requests from an untrusted client. WebLogic Server now provides a mechanism to validate the incoming request to WebLogic Server Web service.
Note that validation is a performance-intensive task and should be used with care. Incoming SOAP requests can be validated in one of the following ways:
  1. Command-line parameter at the time of starting up the server, to enable validation for all services on an server:

    2. -Dweblogic.wsee.validate_request=true

  2. Add <validate-request>true</validate-request> to weblogic-webservice.xml to enable validation for a particular Web service. For example:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/90";;;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;;>
<webservice-description> <webservice-description-name>HelloWorld</webservice-description-name>
    <port-component>
     <port-component-name>HelloWorldServiceImplSoapPort</port-component-name>
      <service-endpoint-address>        <webservice-contextpath>hello</webservice-contextpath>        <webservice-serviceuri>/test</webservice-serviceuri>
      </service-endpoint-address>
     <!-- Note this validate request tag -->
     <validate-request>true</validate-request>
    </port-component>
</webservice-description>
</weblogic-webservices>
9.1
9.2 MP1
CR189158
WebLogic Server does not support Sparse Arrays and Partially Transmitted Arrays as required by the JAX-RPC 1.1 Spec.
9.0
 
CR200359
Web Services of type document-literal wrapped are not supported with XMLBeans data types as input parameters or return values.
9.0 Beta
9.2
CR214405
WebLogic Server 9.0 client was not able to send cookies sent by the server.
This problem has been resolved. Cookies are handled correctly now and client session is maintained.
9.0
9.2
CR218519
Applicable to jwsc, wsdlc, and clientgen:
Web Service interfaces, implementations and parameter types with upper case package names may have problems building and running in some operating systems.
Workaround or Solution:
BEA strongly recommends that you use lowercase letters for the package names.
9.0
9.2
CR223291
When a client sends an instance of complex type to a service, the service echoes back the received instance. If the complex type contains the any element and the any content contained data, the data is not passed to the service.
This problem has been resolved.
9.0
9.2
CR228385
The Web Service Description Language (WSDL) compiler does not generate serializable data types, so data cannot be passed to remote EJBs or stored in a JMS destination.
9.0
 
CR230549
The WLHttpsTransport causes the following error:
AsyncReponseService returned a 404
This problem has been resolved.
9.0
9.2
CR230549
The asynchronous response service did not support the https protocol transport. As a result, asynchronous responses that came back through the https transport encountered a 404 error because no service was deployed to handle the response.
Workaround or Solution:
Support for https protocol transport was added to the asynchronous response service.
9.0
9.2
CR231508
When a Web Service uses an XMLObject as a parameter, a java.lang.IncompatibleClassChangeError exception is thrown at runtime when the client tries to access the service.
This problem has been resolved.
9.0
9.2
CR234178
The jwsc Ant task generates a WSDL of document-literal-wrapped Web Service that misses an input part, resulting in a request envelope with an empty body.
This problem has been resolved.
9.0
9.1
CR234181
When using a security policy with abstract Identity assertion like the default Auth.xml, the X509 token is included as the supported identity token regardless of whether or not the UseX509ForIdentity attribute was enabled on the WebServiceSecurity MBean.
Workaround or Solution:
An X509 token is inserted as a supported token for identity and only if the UseX509ForIdentity attribute is set to true.
9.0
9.2
CR234262
The javax.xml.transform.Source attachment does not work when the source xml has non-ascii characters.
9.0
 
CR234316
Signature reference validation fails if encrypted data contains special characters like the '&'.
This problem has been resolved.
9.0
9.1
CR240079
Non-ASIIC data in a request or attachments may change when you invoke a Web Service through JMS transport.
Workaround or Solution:
Allow applications to send a request as a JMS BytesMessage. The default will still be TextMessage, which is the message type that is used in the previous releases. Applications that need to send non-ASIIC data or binary attachments can use BytesMessage. There is a property on the JAX RPC stub to set the JMS Message type. Once you get a port, you can do one of the following to set JMS message type to BytesMessage:
  1. ((Stub)port)._setProperty(WLStub.JMS_TRANSPORT_MESSAGE_TYPE, WLStub.JMS_BYTESMESSAGE)
  2. weblogic.wsee.util.JmsUtil.setJmsTransportBytesMessage((Stub)port)
The response (sync or async) will be sent in the same message type as the request.
In order to send a callback back as BytesMessage, the application has to set the JMS_TRANSPORT_MESSAGE_TYPE property on the callback stub.
9.1
9.2
CR240408
A WebLogic Server 8.1 style (version one) conversation service requires that the client explicitly know about and echo the conversation ID. The conversation ID is assigned either by the application, or the client side server, and it is not aware where the service is actually provided. A version two conversational service, started in 9.0 release, relies on WS-Addressing to automatically cause the conversation ID to be echoed back to the service. The conversation ID is assigned on the server side, and it embeds the routing information in it. When an 8.1 style conversation client talks to a 9.x server in a clustered environment, the cluster will not have enough information to route the request to the right server.
The solution is to use the cluster-wide singleton service -- the Path Service -- to record the routing information for 8.1 style conversations.
Additional configuration is required for this to work -- The Path Service has to be configured and deployed on one of the servers in the cluster. It is known that the solution is a scalability and single point of failure regression from 8.1. With the cache capability built-in the Path Service, and server migration solution we have in WLS, the regression is somewhat alleviated.
9.0
9.2
CR241793
The canned, library, and user-defined policies are loaded in the wrong order if all the policies have the same name. The user-defined policy should have preference, but the library policy is loaded first.
This problem has been resolved.
9.1
9.2
CR241922
In releases prior to WebLogic Server 9.2, clientgen could not process arrays that were defined in the WSDL description as a one-dimensional array of another array, as in:
 <s:complexType name="ArrayOfArrayOfString">
  <s:complexContent>
   <s:restriction base="enc:Array">
    <s:sequence>
     <s:element name="ArrayOfString"
                type="enc2:ArrayOfString"
                minOccurs="0"
                maxOccurs="unbounded" />
    </s:sequence>
     <s:attribute ref="enc:arrayType"
       wsdl:arrayType="enc2:ArrayOfString[]" />
   </s:restriction>
  </s:complexContent>
 </s:complexType>
or:
 <s:complexType
    name="ArrayOfArrayOfArrayOfArrayOfString">
  <s:complexContent>
   <s:restriction base="enc:Array">
    <s:sequence>
     <s:element
       name="ArrayOfArrayOfArrayOfString"
       type="enc2:ArrayOfArrayOfArrayOfString"
                    minOccurs="0"
                    maxOccurs="unbounded" />
    </s:sequence>
     <s:attribute ref="enc:arrayType"
        wsdl:arrayType=
        "enc2:ArrayOfArrayOfArrayOfString[]"/>
   </s:restriction>
  </s:complexContent>
 </s:complexType>
This problem has been resolved.
9.2
9.2
CR244175
JWSC did not clean up temp files created during the build process.
This problem has been resolved.
9.1
9.2
CR244334
An Invalid/unknown SSL header was received error occurs when a Web Service client tries to use HTTPs to access a Web Service that only supports the HTTP transport.
Workaround or Solution:
To build a Web Service that supports HTTPs, use the @WLHttpsTransport annotation in the JWS instead of the @WLHttpTransport annotation.
9.1
9.2
CR248371
In releases prior to WebLogic Server 9.2, clientgen could not handle multi-dimensional arrays whose types were expressed in the form:
 <complexType name="ArrayOfString2D">
  <complexContent>
   <restriction base="soapenc:Array">
    <attribute ref="soapenc:arrayType"
           wsdl:arrayType="string[][]"/>
   </restriction>
  </complexContent>
 </complexType>
where the wsdl:arrayType is expressed in the form:
"string[][]"
as opposed to:
"string [,]"
This problem has been resolved.
9.2
9.2
CR249356
In 9.1, WebLogic Server only supports attaching WS-Policy to WSDL at the following location: wsdlPort, wsdlBindingOperation, the input or output message of wsdlBindingOperation with a wsp:PolicyReference WSDL extension.
Workaround or Solution:
WebLogic Server now supports attaching WS-Policy to the following according to the WSDL 1.1 specification and WS-PolicyAttachment specification: wsdl:portType, wsdl:binding, wsdl:operation, wsdl:operation/wsdl:input, and wsdl:operation/wsdl:output.
9.1
9.2
CR250608
No error is reported when a WSDL file is read that contains a non-existent ws-policy reference.
This problem has been resolved.
9.1
9.2
CR251516
In releases prior to WebLogic Server 9.2, if the system clock on a client was slightly ahead of the system clock on a server, the following timestamp error message was issued intermittently for small synchronization differences (differences less than the clock precision):
Message Created time in the future
For example, if the clockPrecision setting was set to one minute (default), and the client clock happened to be 40 seconds ahead of the server clock, then this message was thrown 40/60 or 2/3 of the time.
Workaround or Solution:
The clockPrecision property was deprecated and replaced by the more intuitive clockSkew property. ClockSkew will not exhibit any of the probabilistic properties (as shown by the 2/3 in the explanation above) of the clockPrecision, but it does represent a similar concept: the allowable difference between clocks of the server and the client.
9.2
9.2
CR253013
If you change timestamp settings using the Administration Console or WLST your application needs to be redeployed.
This problem has been resolved.
9.1
9.2
CR253092
In WebLogic Server 9.0, the server fails to process an encrypted SOAP message generated by clients created with WebLogic Server 8.1 with the following exception:
weblogic.xml.dom.marshal.MarshalException: Unrecognized child element in SecurityTokenReference
Workaround or Solution:
WebLogic Server now allows the usage of X509IssuerSerial without X509Data in the SecurityTokenReference node.
9.2
9.2
CR253305
The SSL port in the WSDL address location is not correctly set when retrieving dynamic through a proxy.
Workaround or Solution:
Correctly set the address to be the host and HTTPS port set in the Cluster MBean or the Web Server MBean instead of the internal server address behind the proxy.
9.1
9.2
CR254035
If a Web Service is deployed that uses the @RolesAllowed, @RolesReferenced, or @RunAs annotations (at the class-level) to specify the roles that are allowed to invoke the Web Service, anyone accessing the Web Service, including its dynamic WSDL, needs to authenticate themselves as a user mapped to that role.
A client application could use HttpTransportInfo to authenticate. However, clientgen had no way to authenticate itself.
This problem has been resolved.
9.1
9.2
CR254039
If a Web Service is deployed that uses the @UserDataConstraint annotation to force use of HTTPS, anyone accessing the Web Service, including its dynamic WSDL, needs to specify the trust store that contains the list of trusted certificates, including the trusted certificates of the server.
A client application that invokes the Web Service can list the trusted certificates by defining a Trust Manager in the stub; however, there is currently no way to do this for clientgen.
Workaround or Solution:
Set the trusted related properties as the follows:
<clientgen
    wsdl="https://${wls-ssl-server}/HttpsWeb/
    HttpsWebService?WSDL"     destDir="${clientclasses.dir}"     packageName="ssl.web.client">
    <sysproperty key="javax.net.ssl.trustStore" value="${stage.dir}/DemoTrust.jks"/>     <sysproperty key=
    "weblogic.wsee.client.ssl.
    stricthostchecking"
    value="false"/> </clientgen>
9.1
9.2
CR254123
The @UserDataConstraint annotation is not supported for EJB-Implemented Web services prior to WebLogic Server 9.2.
Workaround or Solution:
The @UserDataConstraint annotation can now be set as follows:
@WLHttpsTransport
              (portName="HttpsEjbPort",
               contextPath="HttpsEjb",
                serviceUri="HttpsEjbService") @UserDataConstraint(transport=UserDataConstraint.Transport.CONFIDENTIAL)
public class HttpsEjbService implements SessionBean {
This syntax restricts access to the HttpsEjbService to the HTTPs protocol only.
9.2
9.2
CR255496
The MS Windows-style line break ‘\r\n’ in a CDATA DOM node was canonicalized to ‘&#xD;’, but was written out to the SOAP message as ‘\n’. This lead to a different canonicalization result on the receiving side, resulting in a signature validation failure.
This problem has been resolved.
9.2
9.2
CR256515
CR255973
In releases prior to WebLogic Server 9.2, when any complex features (e.g., conversations) were used in a Web Service, it was packaged as an EJB-based Web Service. In WebLogic Server 9.2, complex Web Services are packaged as Servlet-based Web Services.
Workaround or Solution:
Change your build scripts that expect the 9.2 Web Service to be packaged as an EJB module, so that they now expect the Web Service to be packaged as a Servlet module (i.e., a WAR file).
9.2
9.2
CR257137
In WebLogic Server 9.1, the link attribute is required when configuring the RolesReferenced annotation. For example:
@RolesReferenced(@SecurityRoleRef
(role = "admin", link = "Admin" ))
This problem has been resolved.
9.1
9.2
CR257139
In WebLogic Server 9.1, the mapToPrincipal attribute must be set in the RunAs annotation. For example:
@RunAs(role="user", mapToPrincipals="foo")
Workaround or Solution:
The mapToPrincipals attribute is now optional and defaults to the default security role if not specified.
9.1
9.2
CR257557
CR257472
On a proxy server, if the asynchronous response service was automatically deployed on server startup, then subsequent traffic was not getting routed to the asynchronous response service on the servers that the proxy server was fronting. Instead, the traffic was consumed by the proxy server itself.
Workaround or Solution:
In order to not deploy the asynchronous response service, set the weblogic.wsee.skip.async.response property to true.
9.2
9.2
CR258535
The JAX-RPC 1.1 specification specifies that the Java to XML mapping for byte arrays should be xsd:base64Binary. However, in releases prior to WebLogic Server 9.2 the generated schema type for byte[] was not compliant with JAX-RPC 1.1.
When using JWSC to start a Java Web Service from a class that contains a method that uses a byte[] parameter or return type, the generated WSDL types that correspond to the byte[] argument were incorrectly generated, as follows:
 <xs:complexType name="ArrayOfbyte_literal">
  <xs:sequence>
   <xs:element maxOccurs="unbounded"
            minOccurs="0"
            name="byte"
            nillable="false" type="xs:byte"/>
  </xs:sequence>
 </xs:complexType>
The type ArrayOfbyte_literal was then used as a type in a Document Literal Wrapped operation wrapper element as:
 <xs:element
     name="echoPrimitiveByteArray2Response">
  <xs:complexType>
   <xs:sequence>
    <xs:element name="return"
         type="arrayOfbyte_literal"/>
   </xs:sequence>
  </xs:complexType>
 </xs:element>
9.2
9.2
CR258535
(Contd.)
Workaround or Solution:
JWSC was changed to generate the xsd:base64Binary type for byte[] that JAX-RPC 1.1 requires, as in:
 <xs:element
     name="echoPrimitiveByteArray2Response">
   <xs:complexType>
    <xs:sequence>
     <xs:element name="return"
          type="xs:base64Binary"/>
    </xs:sequence>
   </xs:complexType>
 </xs:element>
Therefore, any JWS clients using these regenerated services will need to be regenerated with the new WSDLs from JWS.
   
CR260810
WebLogic Server 9.2 does not support using a custom exception on a callback that has a package that does not match that target namespace of the parent Web Service.
Workaround or Solution:
Make sure that any custom exceptions that are used in callbacks are in a package that matches the target namespace of the parent Web Service.
9.2
 
CR261078
WebLogic Server does not handle SOAP12 properly when the encoding is RPC LITERAL.
This problem has been resolved.
9.2
9.2
CR261383
When cluster address is used in sending SOAP messages over JMS server, WebLogic Server used to raise an exception.
This problem has been resolved.
9.1
9.2
CR262036
You cannot use JMS transport in an environment that also uses a proxy server. This is because, in the case of JMS transport, the Web Service client always uses the t3 protocol to connect to the Web Service, and proxy servers accept only HTTP/HTTPS.
9.2
 
CR263049
A WSSecurityException used to occur when a Workshop for WebLogic 8.1 application called a WebLogic Server 9.1 Web Service with RPC SOAP binding.
This problem has been resolved.
9.1
9.2
CR263309
The handler response chain used to reach the service endpoint whenever a handleRequest returned false.
This problem has been resolved.
The handler response chain starts from the current handler and does not reach the service endpoint.
9.1
9.2
CR263972
Deployment of a Web Service used to fail and raise a ClassNotFoundException due to a mismatch between the existing holder class name, FooArrayHolder, and the expected holder class name, ArrayOfFoosHolder.
This problem has been resolved.
The existing holder class name is changed to the expected holder class name, namely, ArrayOfFoosHolder.
9.1
9.2
CR264354
While trying to create a SAX parser instance using the ParserFactory, a NullPointerException was being raised.
This problem has been resolved.
9.0
9.2 MP1
CR265278
A RemoteException used to be raised when a Web Service client called a JBoss Web Service using a user-defined class return, and the user-defined class had a field that was an array of user-defined classes.
This problem has been resolved.
9.1
9.2
CR265983
Clientgen fails when processing a WSDL that uses the complex type http://www.w3.org/2001/XMLSchema{schema} as a Web Service parameter.
Workaround or Solution:
There is no known workaround.
9.2
 
CR266759
Web Services that define a Callback interface with a mixed-case package name will fail to compile with jwsc.
Workaround or Solution:
Create the Callback interface in a lower-case- package.
9.2
 
CR267027
In WebLogic Server 9.0 and 9.1, the jwsc task failed to handle XmlObject as an input parameter.
This problem has been resolved.
9.0
9.2
CR268100
When making a reliable one-way Web Service call, the anonymous callback was not providing synchronous acknowledgements of reliable messages.
This problem has been resolved.
The WSRM SequenceAcknowledgement message now enables synchronous acknowledgements of reliable messages.
9.1
9.2
CR268768
JWSC used to generate http://localhost:7001 as the default URL in the WSDL.
This problem has been resolved. If the value of UserDataConstraint is specified as INTEGRAL or CONFIDENTIAL, JWSC generates https://localhost:7002 as the default URL in the WSDL. (Note that this is a secure URL.)
9.1
9.2 MP1
CR269696
WebLogic Server 9.2 does not support JAX RPC handlers in callback Web Services.
Workaround or Solution:
If JAX RPC handlers were used with Web Services created with WebLogic Workshop 8.1, then such applications must be redesigned so that they do not use callback handler functionality.
9.2
 
CR270499
Editing wsrp-wsdl-template.wsdl requires the following supporting files to be copied from wlp-wsrp-producer-web-lib.war to your web-app:
  • wlp_wsrp_v11_types.xsd
  • wlp_wsrp_v1_types.xsd
  • wsrp_v1_full.wsdl
  • wsrp_v1_types.xsd
  • wsrp-wsdl-template.wsdl
  • wlp_wsrp_v1_bindings.wsdl
  • wsrp_v1_bindings.wsdl
  • wsrp_v1_interfaces.wsdl
  • wsrp-wsdl-full.wsdl
  • xml.xsd
9.2
 
CR271229
The jwsc ANT task used to fail and raise a ClassNotFoundException during the build process, if weblogic.jar was not added to the ANT classpath.
This problem has been resolved.
9.1
9.2
CR271996
WebLogic Server 9.2 does not support chunked-transfer encoding when streaming SOAP messages with attachments.
Workaround or Solution:
There is no known workaround.
9.2
 
CR272102
The WSDLC WebLogic Web Services ANT task used to fail and raise a FactoryConfigurationError during the build process, if weblogic.jar was not added to the ANT classpath.
This problem has been resolved.
9.1
9.2
CR272700
Using @WLHttpsTransport in JWS does not generate WS-I conformance wsdl.
Workaround or Solution:
@WLHttpsTransport is now deprecated. Use both @WLHttpTransport and @UserDataConstraint if the JWS endpoint needs to be restricted to accept the HTTPS transport only.
9.2
9.2
CR273307
WebLogic Server 9.2 does not support message-level security in callback Web Services.
Workaround or Solution:
Web Services created with WebLogic Workshop 8.1 that used WS-Security must be redesigned to not use message-level security in callbacks.
9.2
 
CR273446
WebLogic Server 9.2 does not support handling of Java method arguments or return parameters that are JAX-RPC-style JavaBeans that contain an XmlBean property. For example, applications cannot have a method with a signature like this:
void myMethod(myJavaBean bean);
where myJavaBean class is like:
 public class MyJavaBean {
   private String stringProperty;
   private XmlObject xmlObjectProperty;
   public MyJavaBean() {}
   String getStringProperty() {
     return stringProperty;
   }
   void setStringProperty(String s) {
     stringProperty = s;
   }
   XmlObject getXmlObjectProperty() {
     return xmlObjectProperty;
   }
   void getXmlObjectProperty(XmlObject x) {
     xmlObjectProperty = x;
   }
 }
Workaround or Solution:
There is no known workaround.
9.2
 
CR274028
JWSC and clientgen create temporary directories with the names schemacom_bea_xml and META-INF in the /tmp directory and did not remove those directories after the execution of the Web service.
This problem has been resolved.
9.1
9.2
CR275139
In WebLogic Server 9.1, the mapToPrincipals attribute must be set in the RunAs annotation. For example:
@RunAs(role="user", mapToPrincipals="foo")
Workaround or Solution:
In WebLogic Server 9.2, the mapToPrincipals attribute is optional and will default to the default role if not specified. Existing applications should continue to work as before.
9.2
9.2
CR277039
WebLogic Server did not support java2schema for the JAX-RPC-style enumeration class.
This problem has been resolved. WebLogic Server generates the schema type for the JAX-RPC-style enumeration class correctly.
9.1
9.2 MP1
CR278150
When using a browser to request the base URL of a Web Service, (for example, http://localhost:7001/myservice/foo), clicking on the WSDL Page option gives a 404 error instead of displaying the wsdl file.
This problem has been resolved.
9.2
9.2
CR280155
WebLogic Server 9.2 does not support the use of double-byte characters in URLs in Web Services.
Workaround or Solution:
Web Services created with WebLogic Workshop 8.1 that used double-byte characters in URLs must be redesigned to remove all double-byte characters from URLs.
9.2
 
CR282449
Using a 2D XmlObject parameter in a JWS callback produces an IllegalArgumentException.
Workaround or Solution:
There is no known workaround.
9.2
 
CR286602
According to the JAXRPC specification, byte[] and Byte[] should be mapped to the xsd:base64Binary type. This mapping was incorrect for RPC-encoded Web Service.
This problem has been resolved. Weblogic Server maps byte[] and Byte[] for RPC-encoded Web Services according to the JAXRPC specification. See jaxRPCWrappedArrayStyle attribute definition in Ant Task Reference.
9.2
9.2 MP1
CR282728
Using SoapElement[] as a Web Service parameter with @WildcardBinding(className="javax.xml.soap.SOAPElement[]", binding=WildcardParticle.ANYTYPE) will always result in an empty array on the client.
Workaround or Solution:
Do not use the @WildcardBinding annotation to change the default binding of SOAPElement[] to WildcardParticle.ANYTYPE. The SOAPElement[] default binding is set to WildcardParticle.ANY.
9.2
 
CR286793
Provide a mechanism for API for Web Service clients to set keystore per service for two-way SSL implementation.
To implement SSL with certificate for each connection, use the API as follows:
WlsSSLAdapter adapter = new WlsSSLAdapter();
adapter.setKeystore("./DemoIdentity.jks",
"DemoIdentityKeyStorePassPhrase".toCharArray(), "JKS" );
adapter.setClientCert("DemoIdentity","DemoIdentityPassPhrase".toCharArray());
adapter.setTrustManager( new TrustManager(){
             public boolean certificateCallback(X509Certificate[] chain, int
validateErr){
             return true;
             }
       }); weblogic.wsee.connection.transport.https.HttpsTransportInfo info = new
weblogic.wsee.connection.transport.https.HttpsTransportInfo(adapter);
SimpleImplService service = new SimpleImplService_Impl(args[0] +
"?WSDL",info);
Simple port = service.getSimpleSoapPort();
Stub stub = (Stub)port;
stub._setProperty('weblogic.wsee.client.ssladapter', adapter);
9.2
9.2 MP1
CR289365
Socket ReadTimeout was not occurring when a WebLogic Server 8.1 client tried to invoke a WebLogic Server 8.1 web Service deployed on WebLogic Server 9.2.
This problem has been resolved.
9.2
9.2 MP1
CR289504
WSDL validation used to fail when the type belongs to a different Namespace.
This problem has been resolved.
9.2
9.2 MP1
CR289609
When the Message Handler threw a SoapFaultException, an EJB was being assigned but was not getting released later, causing an EJB leak.
This problem has been resolved.
9.1
9.2 MP1
CR291357
WebLogic Server used to generate SOAP responses which were chunked by default.
This problem has been resolved. Users can disable chunking of SOAP responses.
Once chunking is disabled, responses are cached in the memory buffer. Beyond a specified buffer size, SOAP message chunking is resumed.
To disable chunking, set the property weblogic.wsee.NoFlush in the WebLogic Server startup script or while starting up WebLogic Server. For example, -Dweblogic.wsee.NoFlush=true
To control buffer size, set the command line parameter weblogic.wsee.http.response.BufferSize. For example, -Dweblogic.wsee.http.response.BufferSize=<buffer size in Bytes>
Note that the buffer size should be a multiple of the chunk size, so the actual buffer size is automatically assigned a value that is a multiple of the chunk size, and it can be slightly higher than the user-specified value.
9.2
9.2 MP1
CR291549
Incorrect dynamic WSDL location address was being generated when a service was deployed on a cluster with multiple front-end hosts and ports.
This problem has been resolved.
9.2
9.2 MP1
CR293764
WebLogic Server Administration Console did not allow users to add multiple policies (for example, sign.xml and auth.xml) to a single Web service operation.
This problem has been resolved.
9.2
9.2 MP1
CR294076
After upgrading to JDK 1.5.0_08 from JDK1.5.0_4 in WebLogic Server 9.2 domain, there is a problem with JWSC ANT.
Workaround or Solution:
  1. Add -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 to setDomainENV.cmd file on Windows (or setDomainENV.sh on UNIX).
  2. For running ant task, set ANT_OPTS as follows: set ANT_OPTS=-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
  3. For all instance of java or javac tasks in an ANT file, set jvmarg for the same. For example, in the case of build.xml:
 <target name="run">
    <java classname="examples.webservices.jws_basic.simple.Client"
    fork="true"
    failonerror="true" >
      <!--Note the jvmarg tag -->
      <jvmarg line="-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0" />
      <classpath refid="client.class.path"/>
      <arg line="http://${wls.hostname}:7001/jws_basic_simple/SimpleService" />
    </java>
 </target>
9.2 MP1
 
CR294127
According to the SOAP 1.2 specification, the content type in SOAP messages should Content-Type: application/soap+xml; charset="utf-8". It was being set to Content-Type: text/xml; charset="utf-8".
This problem has been resolved. The content type is correctly set.
9.2
9.2 MP1
CR295067
Global JAX-RPC handlers were getting called before codec handler.
This problem has been resolved. Global JAX-RPC handlers are called after codec handler for a Web Service, so that the SOAPMessage is visible to them.
9.2
9.2 MP1
CR297710
Conversation with database persistent store in a clustered environment was unable to find the store with logical name.
This problem has been resolved.
9.2
9.2 MP1
CR304920
CR305731
Invalid or unsupported policies are not validated at run time. Therefore, users who are not configured on WebLogic Server get mapped as anonymous users and the Web Service is considered unprotected. This leads to access being granted to a secure Web Service to unauthorized users.
9.2 MP1
9.2 MP1
CR289578
Using javax.xml.soap.Text.isComment() of SAAJ 1.1 used to result in UnsupportedOperationException.
This problem has been resolved.
9.2
9.2 MP2
CR298324
CR312171
When a user did not have PKI credential mapping, but the user belonged to a group which has PKI credential mapping, WebLogic Server used to fail to retrieve PKI credentials for the user.
This problem has been resolved.
9.2
9.2 MP2
CR303512
WebService used to fail to honor elementFormDefault="unqualified" when XMLBean was used.
This problem has been resolved.
9.2
9.2 MP2
CR305700
For doc-literal wrapped convention, the wrapped array was not being considered as a valid wrapped element.
Workaround or Solution:
Added support for wrapped array to be recognized as a wrapped element using the flag allowWrappedArrayForDocLiteral, which can be set for clientgen or wsdlc Ant tasks.
9.2
9.2 MP2
CR307758
WebService used to fail to honor the optional element minOccurs="0". When invoking a WebService with this optional element in the request message following issues were faced.
  • Deleting this optional element from the request message failed to invoke WebService.
  • When the WebService client invoked the WebService with a null value for this optional element, the optional element was added to the SOAP body with empty value in the SOAP response. The resulting XML would not validate against the schema if it has nillable=false for this optional element.
These problems have been resolved.
9.2
9.2 MP2
CR312652
DuplicateElement exception was being raised when a ObjectHolder parameter was set to a specific schema type.
Workaround or Solution:
Added support for using XMLBean as a SOAP header.
For using XMLBean as a SOAP header, you need to create a holder class for the XMLBean and package it in the generated xml bean jar file. This holder must be in the same root package as XMLBean, and in a holders subpackage, and named <XMLBean Class>Holder, where <XMLBean Class> is the name of the XMLBean class to be passed as the header IN/OUT param. Use the holder org.t1M1.tml.tMLTransport.holders.TMLHeaderDocumentHolder for holding org.t1M1.tml.tMLTransport.TMLHeaderDocument. In the jws file, use this holder for the header parameter. The holder class is in the format of JAX-RPC holder.
9.2 MP1
9.2 MP2
CR313282
WebLogic was not supporting the following schema type:
 <s:complexType>
    <s:sequence>
      <s:element ref="s:schema" />
      <s:any />
    </s:sequence>
 </s:complexType>
This problem has been resolved.
9.2
9.2 MP2
CR316028
The jwsc Ant task was not detecting non-unique serviceUri element for multiple transports in one jws file and an error was being raised.
Workaround or Solution:
Now jwsc raises the following error:
[jwsc] [ERROR] - Multiple ports may not share the same contextPath and
serviceUri "/stock//StockQuote".
9.2
9.2 MP2
CR299988
CR312472
WSDL validation used to fail when the XMLBean type belongs to a different namespace.
This problem has been resolved.
9.2
9.2 MP2
CR306364
NullPointerException was being raised during WebService deployment.
This problem has been resolved.
9.2
9.2 MP2
CR308925
When an error occurred during SoapFault processing, a null was being sent back to the client instead of raising an exception.
This problem has been resolved.
9.2
9.2 MP2
CR287220
CR356570
Duplicate Global Type error was being raised in a Web Service when <xs:include> was used in XSDs.
This problem has been resolved.
9.2
9.2 MP2
CR304907
The jwsc Ant task did not support JavaBean which has multidimensional array property for parameter and result of Web Services.
This problem has been resolved.
9.2
9.2 MP2
CR305378
The format of SOAP message with attachment was not standard. The Content-Type header of the SOAP message did not contain Type field.
This problem has been resolved.
9.2
9.2 MP2
CR309328
WebLogic Server client used to get a NullPointerException in SoapCodec.java when receiving a custom exception from WebService.
This problem has been resolved.
9.2
9.2 MP2
CR309427
When using WebLogic Server 9.2 jwsc-generated WSDL in WebLogic Server 8.1, the following two issues used to happen.
  1. The XML namespaces used for the complex types for the input parameter type and the return type were not imported first using xs:import. WebLogic Server 8.1 clientgen required these namespaces to be imported; otherwise WebLogic 8.1 clientgen used to fail.
  2. The foo property on both the input parameter type and the return type creates message parts that are named the same across both the request message and the response message for the same operation. WebLogic Server 8.1 clientgen used to fail if a message part is named the same across the request message and the response message for the same operation.
These problems have been resolved.
9.2
9.2 MP2
CR311812
If an array argument of Java Bean was included in Java Web Service, the generated WSDL used to fail to validate in Eclipse.
This problem has been resolved.
9.2
9.2 MP2
CR312041
ServiceControlexception.hasSoapFault() was not returning true in some cases where the SOAP fault was wrapped in a RemoteException.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR314532
WSDL generated for a Web Service used to include transient fields of the Java classes.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR316620
The generated COW file from wsdlc would not contain all of the imported schemas when referenced schema has an import/include that is relative and has a "../.." segment in it.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR316632
When running jwsc on a COW file created from a WSDL with many imported XSDs using “/../” in the import/include paths, the imported/included path lengths increased and paths were filled with many “..” segments and this resulted in FileNotFoundException.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR317164
If @WebMethod annotation was specified for the webservice method in the jws interface and @RolesAllowed annotation was specified for the same method in the jws implementation, @RolesAllowed was not being honored.
This problem has been resolved.
9.2 MP1
9.2 MP2
CR320607
WebLogic Server 9.2 jwsc ant task used to create WSDL that would not work with WebLogic Server 8.1 clientgen because of missing imports.
This problem has been resolved.
9.2
9.2 MP2
CR314565
While using UDDI feature with server_only kit (not platform kit) installations you may get UDDIException with the following error:
Error in initializing pluggable tModels.
Workaround or Solution:
Comment the entry, pluggableTModel.file.list, in <WEBLOGIC_HOME>/server/lib/uddi.properties file.
9.2 MP2
 
CR280052
The wsdl2service task used to add multiple entries for namespace in the webservice.xml descriptor file.
This problem has been resolved.
9.1
9.2 MP3
CR320756
The Web Service client used to fail after migration from WebLogic Server 8.1 SP5 to WebLogic Server 9.2 MP1.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR328450
NullPointerException used to raise during SoapResponse deserialization at runtime.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR330048
CR352162
In WebLogic Server 9.x, the Web Service client used to make connect()call multiple times before throwing SoapFaultException.
This problem has been resolved.
9.2
9.2 MP3
CR331542
Exported WSDLs of a proxy service found to be invalid when they were imported into ALSB.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR336820
JMS WebServiceControl was not returning a JMS connection back to the connection pool.
This problem has been resolved.
9.2
9.2 MP3
CR287220
Duplicate schema entries were getting added to the WSDL which resulted in Duplicate Global Type error during deployment.
This problem has been resolved.
9.2
9.2 MP3
CR283072
CR331142
When the <Timestamp> header was added in the SOAP message and both <Created> and <Expires> headers were not present, the Web Service used to fail.
This problem has been resolved.
9.1
9.2 MP3
CR294202
Verification of SAML signature used to fail with an error in certificate parsing.
This problem has been resolved.
9.2
9.2 MP3
CR301615
When XMLBean was used, the jwsc Ant task used to generate invalid WSDL if primary schema has included schema and referred the types in the included schema. The jwsc task generated a schema section for each of the schema and the types in the included schema were not resolvable from the primary schema.
This problem has been resolved.
9.2
9.2 MP3
CR314731
Web services with a single dimension SOAP array and variable length were not handled properly. The Web Services would fail when processing for empty arrays.
This problem has been resolved.
9.2
9.2 MP3
CR315764
The ServiceControl assembly performance used to degrade when referencing types in a large XMLBean jar file.
This problem has been resolved. Introduced the system property, -Dweblogic.wsee.bind.useExistingXBeans. The default value is false. When this property is set to true, the compiling will not be performed if the referenced XMLBean already exists in the classpath.
9.2
9.2 MP3
CR315984
When a Web Service was running from WebLogic Workshop, the Workshop Service Control created using XSDs with elementFormDefault='unqualified' used to fail in certain scenarios while parsing the generated SOAP messages.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR316863
Incorrect Java mapping used to be generated for schema type that contained the <xs:extension> element.
This problem has been resolved.
9.2
9.2 MP3
CR316385
An IOException used to occur when invoking a Web Service method through JMS that use the default charset.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR316286
In weblogic.wsee.workarea.WorkAreaClientHandler class, the handleRequest() method used to print the log messages all the time.
This problem has been resolved. Verbose has been disabled by default.
9.2 MP1
9.2 MP3
CR322355
The generated service control used to have incorrect signature for XMLBean type when the element has maxOccurs='unbounded'.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR324105
An exception used to raise while sending JMS ByteMessage more than once using JMS Transport.
This problem has been resolved.
9.2
9.2 MP3
CR325505
The following issues that are not compliant with the WSRM standard used to occur in WebLogic Server:
  • As per WSRM specification, there will be a single acknowledgement for the entire range of messages sent in a sequence, but WebLogic Server used to send an acknowledge message for each received message.
  • WebLogic Server did not acknowledge empty last message.
9.2
9.2 MP3
CR325721
When invoking a Web Service method on which policy was applied and if this method also used the WorkContext API to propagate data across the Web Service call, the Web Service used to fail with duplicate header fault.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR325776
CR301621
CR331147
When SAML assertion was used to sign a message, the verification of signature used to fail with NullPointerException.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR328469
The SOAPConnectionImpl class used hardcoded SOAP11 binding type when creating a client connection.
This problem has been resolved. SOAP message now use SOAP11 or SOAP12 dynamically.
9.2 MP2
9.2 MP3
CR345256
When there was an authentication failure for an EJB-based SOAP 1.2 JAXRPC service, the generated SOAP fault used to contain incorrect content type.
This problem has been resolved.
9.2
9.2 MP3
CR346773
If the parameter of JWS contained nested multi-dimensional arrays, the JWS failed to compile.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR349988
When xsd:anyType and xsd:restrictions are used together in a WSDL, the container would throw a NullPointerException while processing xsd:anyType bindings.
This problem has been resolved.
9.2 MP1
9.2 MP3
CR351046
When you build a web service implementation from WSDL using the wsdlc Ant task, the generated JWS used to have the wrong holder class for base64Binary or hexBinary.
This problem has been resolved.
9.2
9.2 MP3
CR336762
The web services created using xbeans were not able to handle schemas with common global element name, even when the schema were in a different namespace.
This problem has been resolved.
9.2 MP2
9.2 MP3

 

WebLogic Tuxedo Connector

Change Request Number
Description and Workaround or Solution
Found In
Fixed In
CR127660
View classes are not set on a per connection basis.
A shared WebLogic Tuxedo Connector hash table can cause unexpected behavior in the server if two applications point to the same VIEW name with different definitions. There should be a hash table for the view classes on the connection as well as for the Resource section.
Workaround or Solution:
Ensure that all VIEW classes defined across all your WebLogic Workshop applications are consistent, meaning that you have the same VIEW name representing the same VIEW class.
8.1 SP2
WNF
CR246385
You cannot create more than three Remote Access Points using the WLS Administration Console.
Workaround or Solution:
You can now use the WLS Administration Console to create multiple Remote Access Points rather than manually editing the config.xml file.
8.1 sp03
9.2
CR253111
WebLogic Tuxedo Connector cannot re-establish the connection to the second remote domain if there is a network problem between the local domain and the first remote domain.
This problem disappears once the remote Tuxedo GWTDOMAIN gateway starts responding to the session negotiation protocol exchange.
Workaround or Solution:
Establish a connection explicitly. The connection can be established using the “connect” command of dmadmin utility from the Tuxedo side.
9.0
9.2
CR263425
When a user implements a Tuxedo service on WebLogic Server using the WTC TuxedoService interface, calls a transactional context, and the transaction is marked ROLLBACK_ONLY during service processing, the call never returns and the corresponding Tuxedo client blocks and eventually times out.
Workaround or Solution:
Instead of blocking, a TPESVCERR error is now returned whenever an exception occurs at xa.end() time.
9.0
9.2
CR279512
WTC viewj/viewj32 compiler does not generate correct class file.
Prior to WLS 9.2, viewj and viewj32 compilers will not handle any view definition file with missing NULL value; instead they will issue a warning message and stop processing. However, in WLS 9.2 this behavior changed, it will continue generating java file for the view, but the view class will not have field data and access methods for them. The result is that viewj/viewj32 will generate an incorrect java view class.
Workaround or Solution:
Add NULL value for every field in the view definition file.
9.2
 
CR264067
The implementation of the FML-to-XML and XML-to-FML conversion in WTC only converted a byte array into a string. This could result in a non well-formed document, depending on the original CARRAY field.
Workaround or Solution:
CARRAY fields in an FML buffer are now encoded to a base64 string before being converted to XML. Conversely, elements identified as CARRAY fields in an XML document are assumed to be encoded in base64 and are accordingly decoded.

Note: Users should be aware that this change will cause CARRAY typed fields to be encoded/decoded to/from base64, as opposed to simply being converted to/from a string from/to a byte array (java String(byte[] constructor and String.getBytes() function, respectively).
9.1
9.2
CR301123
The definition of the WTC Export ResourceName attributes in the WebLogic MBean Reference and Console Help is not accurate.
The correct definition for ResourceName is:
“The combination of ResourceName and LocalAccessPoint must be unique within defined Exports. This allows you to define unique configurations having the same ResourceName.”
9.2
10.0


  Back to Top       Previous  Next