Known and Resolved Issues

WebLogic Server Known and Resolved Issues

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

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

• Administration Console Issues
• Apache Beehive Support Issues
• Core Server Issues
• Deployment Issues
• Diagnostics Issues
• Documentation Issues
• EJB Issues
• Examples Issues
• Installation Issues
• J2EE Issues
• JDBC Issues
• JMS Issues
• JMX Issues
• Jolt Issues
• JSP and Servlet Issues
• JTA Issues
• Java Virtual Machine (JVM) Issues
• Monitoring Issues
• Node Manager Issues
• Online Help Issues
• Operations, Administration, and Management Issues
• Plug-ins Issues
• RMI-IIOP Issues
• Security Issues
• Spring Framework on WebLogic Server Issues
• Start Script Issues
• Tools Issues
• Upgrade Wizard Issues
• Utilities Issues
• Web Services and XML Issues
• WebLogic Tuxedo Connector Issues

 

---

Administration Console Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR043645	The Administration Console does not work properly if you make it the default Web application in a Managed Server environment. Note: The Administration Console was redesigned and no longer exhibits this issue.	6.0	No Longer Applicable
CR063594	Information about cached JDBC statements is not displayed on the JDBC Monitoring pages.	9.0 Beta
CR075845	Deploying an application requires multiple steps. With the exception of the start and stop operations, which can be invoked outside of an edit session, only a single deployment operation (install, upgrade, or delete) can be performed on a single deployment in an edit session. Workaround: Re-activate the edit session after each of these operations on each deployment.	7.0	Works As Designed
CR080476	You cannot specify a default Web application for a server from the Administration Console. Note: The Administration Console was redesigned and no longer exhibits this issue.	8.1	No Longer Applicable
CR082949	When you use the FullSecurityDelegation setting, an empty <auth-constraint> or an unchecked method in a deployment descriptor does not delegate security to the Administration Console. Note: The Administration Console was redesigned and no longer exhibits this issue.	7.0 SP1	No Longer Applicable
CR087951	The Administration Console does not create a new ldift file when you create a new security realm. If a new security realm is created and then set as the default security realm, the server may not reboot because there are no Admin accounts for the new security realm. Note: The Administration Console was redesigned and no longer exhibits this issue.	7.0	No Longer Applicable
CR089480	Modifications to the Monitoring tables are not available. Note: The Administration Console was redesigned and no longer exhibits this issue.	8.1	No Longer Applicable
CR186966	The Administration Console uses the JMX management interfaces to interact with WebLogic Server. WebLogic Server supports several MBean servers that provide access to management features from different perspectives. Although these MBean Servers may be disabled in the WebLogic Server configuration files, the Administration Console requires these MBean Servers during operation and will not run successfully without them.	9.0
CR190443	The initial start of the Administration Console on an individual server instance is slow.	9.0 Beta	9.0
CR194454	The DefaultWebAppContextRoot option for Web servers is not yet implemented.	9.0 Beta
CR198678	The Administration Console still shows the default table size even after the preferred table size is set to something other than the default size.	9.0
CR200229	You can not change the order of security providers using the Administration Console.	9.0 Beta	9.0
CR200627	After a pageflow completes in the Administration Console, it forwards to a different page, typically a table. Pressing the browser back button at this point results in an attempt to load the last JSP file in the completed assistant. At this point, all of the context for this assistant is discarded. Workaround: BEA recommends that you do not use the browser back button to step back into an assistant once changes are cancelled or finished, and that you do not go back to a previous step in an assistant. Instead, use the navigation links and buttons in the Administration Console.	9.0
CR202076	Refreshing the page while using the Start/Stop option in the Web application assistant produces a page flow error.	9.0 Beta	9.0
CR202168	If you deploy an 8.1 Web Service, the Administration Console's deployment table displays the Web Application that the Web Service is packaged in and the Web Service. If you click the Web Application name, the Administration Console displays Security Roles and Policies tabs. However, there are no Security Roles and Policies tabs for the Web Service itself. Workaround: Create a new Web Service for 9.0. The Roles and Policies tabs will be displayed for it in the Administration Console.	9.0
CR202364	On the Domain Logging page, if the limit of 100 logs is reached, additional logs are not visible.	9.0 Beta
CR202430	A predicate for a security policy cannot be edited through the Administration Console.	9.0 Beta	9.0
CR202565	You can use the Administration Console to shut down the Administration Server, but as the Administration Console attempts to refresh itself, it often encounters a problem displaying the page because the Administration Server is no longer available to service requests. This failure manifests itself in different ways, depending on the timing, machine load, and other deployments.	9.0
CR203422	A JMS Bridge destination requires a Connection Factory JNDI Name and a Destination JNDI Name. If the Destination JNDI Name field is not specified, all bridge destinations are considered one single physical destination, and the following message is displayed: "Caused by: weblogic.descriptor.DescriptorValidateException: The following failures occurred: -- Messaging Bridge "Bridge-2": source and target destinations cannot be the same physical destination."	9.0 Beta	9.0
CR204630	An EJB-style Web service can not be tested through the Administration Console. The EJB Module-->Testing tab cannot be used to test the deployment of an EJB Module (JAR file).	9.0 Beta
CR204751	Starting or restarting a Web application does not appear in the Change List in the Change Center.	9.0 Beta	Works As Designed
CR204886	Currently, no more than 50 users or groups from an external LDAP server or database can be displayed in the Administration Console.	9.0 Beta
CR204887	Currently, you can not use wildcards in the Administration Console to restrict the search of users and groups.	9.0 Beta	9.0
CR207640	After adding security providers to a security realm, the new security providers appear in the Change list and the Change list will indicate which servers need to be rebooted to add the providers to the realm.	9.0 Beta
CR207995	When you upgrade a 7.x config.xml file with SSL enabled to this release of WebLogic Server, the Administration Console must be accessed over the non-secure port (for example, http://localhost:7001). If you try to use the secure port (for example, http://localhost:7002), errors are recorded in the server log; a page flow error occurs when accessing the home.jsp for the Administration Console; and the following message is displayed: server is currently making changes.	9.0 Beta	9.0
CR208120	The Dump Thread Stacks feature in the Administration Console (Server page --> Monitoring --> Performance --> Lock&Edit --> Dump Thread Stacks) only works if the server is running on JRockit. Workaround: Thread dumps work on all Virtual Machines if you use the WebLogic Scripting Tool.	9.0
CR208141	The Administration Console can not be used to delete a certificate from the certificate registry.	9.0 Beta	9.0
CR208157	Using the Copy button when copying a registered certificate to a file causes an error message to be displayed in the Administration Console.	9.0 Beta	9.0
CR208168	The information displayed in the Change Center after a deployment action (install, start, stop, delete) is confusing.	9.0 Beta	9.0
CR208258	Applications deployed on a cluster do not appear in the list of deployments for each server belonging to the cluster in the Deployments tab for the Settings of the server.	9.0
CR208373	Message-Driven Beans (MDB) may specify adapter-jndi-name in the deployment descriptor to indicate that the MDB is receiving messages from a resource adapter rather than from JMS. Such a binding entails configuring an ActivationSpec object which is passed to the RA during deployment. The Administration Console does not currently provide a way to view or configure the Resource Adapter that an MDB is bound to. The Administration Console does not currently provide a way to view or configure the ActivationSpec properties on the MDB.	9.0
CR208388	In resource adapters, JNDI names are used for the following three types of objects: The Resource Adapter bean Each outbound connection pool Each Administered object The Administration Console should display them all, but does not display the Resource Adapter bean JNDI name.	9.0
CR208653	On the Cluster -> Configuration -> Migration page, you must select the Candidate Machines that you want to use for Migratable Servers at the same time that you specify a cluster-wide data source in the Data Source for Automatic Migration field.	9.0 Beta
CR208683	The Deployment Plan and Dependencies pages are incomplete. As a result, you cannot view or edit bindables in a deployment plan through the Administration Console.	9.0 Beta	9.0
CR209073	JMS service migration does not work using the Administration Console. Workaround: A JMS server can be successfully migrated using the weblogic.Admin command-line utility. Otherwise, you can configure a migratable server in place of migrating a JMS server, as described in "Server Migration".	9.0 Beta
CR209110	The Administration Console sends log messages to the Administration Server log, but there is no way to filter the messages or use the log configuration pages to reconfigure Console logging. Workaround: Use -Dlog4j.configuration=path-to-config.	9.0
CR209139	JMS servers cannot be targeted to a migratable target server using the JMS Server -> Target & Deploy page of the Administration Console. Workaround: Create a persistent file store and target it to a migratable server. Create a JMS server without selecting a persistent store, and target it to a non-migratable server. Reopen the JMS server and modify it to use the persistent file store created in step 1. Target the JMS Server to the same Migratable server that the persistent file store is targeted to.	9.0 Beta
CR210869	When a role or policy condition is created or modified in the Administration Console, you must click the. Save button before leaving the role/policy editor page. Otherwise, all the changes made during the creation or modification of the condition(s) that are displayed get lost when you return to the same page. No warning pop-up or message appears to tell you that leaving the page without clicking Save results in losing all changes made.	9.0
CR213392	The ability to configure and monitor durable subscribers was available through the WebLogic Server 8.1 Administration Console, but is not currently available through the WebLogic Server 9.0 Administration Console.	9.0
CR215865	The Administration Console does not provide a way to set control security when custom roles and policies are set.	9.0 Beta	9.0
CR217569	The Administration Console presents JMS configuration values even if an Message-Driven Bean (MDB) is sourced by a resource adapter. The Administration Console does not provide a way to configure (read and/or write) the adapter-jndi-name for an RA-MDB.	9.0
CR221062	After you enable the administration port from the Administration Console and click the Activate button, the Administration Console is not reachable until the URL used to communicate with the Administration Console is changed to HTTPS and the administration port number. Because the administration port setting is dynamic, the Administration Console should redirect after activating any changes regarding the use of the administration port.	9.0
CR223221	As part of the JMS Modules > [module] > [topic] > Monitoring > Durable Subscribers > Monitoring tab, the table of durable subscribers should, but does not currently, provide a link to browse the messages queued for the subscriber. The New, Move and Delete operations should be, but are not currently, available for selected messages.	9.0
CR223643	If you upload a non-ascii name application in the Administration Console, the file name appears garbled.	9.0
CR226270	After you specify the location for the new plan for a resource adapter, the Administration Console takes you back to the "Settings for <adapter name>" screen where it says that no Deployment Plan is selected. Workaround: You must have separate directories for the application and the plan instead of placing both files in the same directory.	9.0
CR226301	As administrators configure applications in the Administration Console, some of those configuration changes are saved as deployment plan variables. The Deployment Plan pages allow you to view the variables that have been set in the deployment plan and to delete one or more variables from that plan. The Deployment Plan pages used to view and edit variables are only available for an application, but should also be available for stand-alone deployments. Workaround: Administrators should navigate to the individual configuration pages for a deployment, module, or component, viewing and editing configuration settings that are specific to that deployment. Deployment plans may also be edited outside of the Administration Console environment by using an XML or text editor.	9.0
CR228589	The Jolt Connection Pool monitoring pages in the Administration Console cannot access the Jolt Runtime MBeans, and therefore Jolt connection pools cannot be monitored or reset using the Administration Console. Workaround: Use WebLogic Scripting Tool (WLST) access the Jolt Runtime MBean.	9.0
CR230275	The following attributes are currently missing from the Domain > Configuration > JTA page under Advanced: MaxXACallMillis weblogic.management.configuration.JTAMBean Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain. Default: 120000 MaxResourceUnavailableMillis weblogic.management.configuration.JTAMBean The maximum duration (in milliseconds) that an XA resource is marked as unhealthy. After this duration, the XA resource is declared available again, even if the resource is not explicitly re-registered with the transaction manager. This setting applies to the entire domain. Default: 1800000 MaxResourceRequestOnServer weblogic.management.configuration.JTAMBean Maximum number of concurrent requests to resources allowed for each server in the domain. Default: 50 Minimum: 10 Maximum: java.lang.Integer.MAX_VALUE	9.0
CR230611	The Administration Console can be used to attach a policy to a Web Service. However, if you attach more than one policy to a Web Service operation, you receive a BeanAlreadyExists exception when you click Activate to redeploy the application with the new policies. Workaround: Manually redeploy the application.	9.0
CR231700	The Diagnostics/ Log Files pages in the Administration Console default to show only the last ten log file entries recorded in the last five minutes. These defaults may be changed by customizing the individual log tables to reflect your preferences. If you do not set preferences and no entries have been recorded in the past five minutes, you may see empty tables because no log entries match this default filtering criteria. Workaround: Because log files can grow quite large, we limit the size of the log tables in the Administration Console viewer to the most recent 1000 entries that match the filtering criteria. Selecting "ALL" for the maximum results returned on the log table customization pages includes the most recent 1000 entries.	9.0
CR231734	The chooser control is used in several pages in the Administration Console and presents a list of available items, chosen items, and controls to move items from one list to the other. This control does not support moving more than one item at a time using a CTRL+mouse click interaction. Workaround: Select and move one item at a time.	9.0
CR233421	The Web Services Description Language Compiler hangs when non-ascii characters are used in complexType.	9.0
CR233862	If an installed JDBC module has a password-encrypted field encrypted with the wrong key, an exception occurs in the Administration Console. This can occur when you copy a JDBC module from one domain to another. Workaround: To re-set the password correctly, use java weblogic.security.Encrypt <password> in the domain home directory and modify the module file to change the password value.	9.0
CR234112	When using the Summary of Asynchronous Tasks function in the Administration Console, invoking Cancel on a running task results in a UIControlException.	9.0
CR234156	If the Administration Console has been modified through a console extension, images and CSS pages get cached by the browser. You may notice the caching when using the MedRec Console. Workaround: Close all the browser windows and then re-open the browser.	9.0
CR234373	The Administration Console demands an Administration port for the Suspend and Force Suspend buttons, even though the suspend and force suspend operations do not strictly require it.	9.0
CR234411	When you create a security provider (any provider such as PKI credential mapper, auditing provider, authentication provider, etc.), the creation assistant takes the name of the provider and then returns to that provider's configuration summary page showing the newly added entry. However, the creation is not yet complete. The provider-specific details must be entered for it to be a valid provider configuration. Assistants should result in a complete configuration of a provider, but they currently do not.	9.0
CR234938	The JMX MBean server only allows security management operations on the runtime bean tree. The Administration Console also prevents security management operations while a pending configuration change is in progress. For example, if an authentication provider configuration is changed, the Administration Console prevents creating a new user for that authentication provider until the configuration change is complete, which typically requires a server re-boot.	9.0
CR235930	Mail encoding is currently not configurable on the SMTP configuration page in the diagnostic module. Upon SMTP notification, the mail body and subject are encoded in JVM default encoding. On Japanese Windows and UNIX, JVM default encoding is not mail-safe, which causes various problems such as character garbling, delivery failure, etc.	9.0
CR236585	Using the Administration Console search pain results in a 404 error when it is run on other than the original locale. For example, the 404 error occurs if a French user uses the English version on the French locale. Workaround: Switch the browser's locale to en-us.	9.0

 

---

Apache Beehive Support Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR210907	Netui databinding expression language fails when BeanInfo overrides JavaBean property names. Evaluation of expressions in the Netui databinding expression language throws errors when BeanInfo netui databinding EL does not to work when java.beans.BeanInfo is used to override JavaBean property names. Workaround: Do not override JavaBean property names using BeanInfo if you use a JavaBean in Netui databinding. If you must databind to such a bean, wrap the bean in a UI version of the bean that follows the JavaBean property naming convention.	9.0
CR227429	The service control generator does not support implicitly wrapped WSDL types. In the 8.1 release of WebLogic Server, service controls generated from wrapped style WSDLs hid the wrapping details from the user, resulting in implicitly wrapped types. In the current 9.0 release implicitly wrapped types are not supported, that is, the generated control does not hide that parameters are wrapped when the service is called.	9.0
CR232509	The Beehive Web Service Control is not included in the version of Beehive shipped with Weblogic Workshop. Workaround: Use the Web Service Control included as part of WebLogic Server instead. For details and instructions, see the online documentation at http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/controls/service/navServiceControl.html.	9.0
CR233609	The version of Beehive shipped with WebLogic Server 9.0 does not include the Web Service metadata sub-project. Consequently, the Web Service metadata documentation has not been included and hyperlinks to the removed documentation content are broken.	9.0
CR234170	Weblogic 9.0 ships with Beehive v1m1. This is an upgrade of the Beehive v1m1 available from the Apache Web site. The following improvements were made: Fixed Apache Beehive issue 829, "Controls deserialization broken because it's looking for the wrong delimiter." See http://issues.apache.org/jira/browse/BEEHIVE-829 for details. Fixed Apache Beehive issue 834, "JDBC Control throws NPE after deserialization." See http://issues.apache.org/jira/browse/BEEHIVE-834 for details. Weblogic 9.0 Beehive v1m1 ships with XMLBeans v2. Changes were made to the JMS Control to fix some deserialization problems.	9.0 Beta	9.0
CR234997	The application.xml file contained in weblogic-beehive-1.0.ear causes errors when parsed with the Xerces XML parser. The application.xml file contained in BEA_HOME/weblogic90/common/deployable-libraries/weblogic-beehive-1.0.ear has whitespaces before the xml declaration <?xml version=?1.0? encoding=?UTF-8??> Workaround: Remove the whitespaces at the beginning of the file: 1. Extract all files in BEA_HOME/common/deployable-libraries/weblogic-beehive-1.0.ear into a folder. 2. Edit application.xml, removing the whitespace preceding <?xml version=?1.0? encoding=?UTF-8??> 3. Make a new EAR file of the same name (weblogic-beehive-1.0.ear) containing all files extracted from the original EAR file. 4. Replace the original EAR file with the new one.	9.0
CR237173	The build-control-module task references a CLASSPATH property that does not exist. If you use the build-control-module task and see the following error message during the build process: <drive>:\bea\weblogic90\beehive\weblogic-beehive\ant\weblogic-beehive-buildmodules.xml:140: taskdef class org.apache.beehive.controls.runtime.packaging.ControlJarTask cannot be found you need to modify the Ant build script that calls it. Workaround: Add the following line to the Ant build script: <property name="controls.jars.prop" refid="controls.dependency.path"/> after importing weblogic-beehive-imports.xml and weblogic-beehive-tools.xml, but before importing weblogic-beehive-buildmodules.xml, as indicated by the following example: <import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-imports.xml"/> <import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-tools.xml"/> <property name="controls.jars.prop" refid="controls.dependency.path"/> <import file="${beehive.home}/weblogic-beehive/ant/weblogic-beehive-buildmodules.xml"/>	9.0

 

---

Beangen Issues

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

 

---

Core Server Issues

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

 

---

Deployment Issues

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

 

---

Diagnostics Issues

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

 

---

Documentation Issues

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

 

---

EJB Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR202400 CR203119	Using EJBGen to generate XML Schema Definition-based (XSD) deployment descriptors is not supported in the Beta release; you can use EJBGen to generate Document Type Definition-based (DTD) deployment descriptors only. Workaround: Use DDConverter to convert your DTD-based descriptors to XSD-based deployment descriptors, and then, as necessary, manually edit or create descriptors in the deployment descriptor files. You can use an XML editor to edit deployment descriptor files.	9.0 Beta	9.0
CR207543	When you deploy to a cluster an application that contains many EJBs, the following error occasionally occurs: # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0xfec6a454, pid=16651, tid=27 # # Java VM: Java HotSpot(TM) Server VM (1.5.0-b64 mixed mode) # Problematic frame: # V [libjvm.so+0x46a454] ... Workaround: Create multiple applications that each contain fewer EJBs instead of one application that contains all of the EJBs.	9.0 Beta
CR217875	If you use Web Services with reliable messaging, you will see a warning message such as: <Jun 8, 2005 9:33:36 AM PDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'uuid-677826faf045b124-7059d65b-1045cccaa 17--7ffb', class weblogic.wsee.server.jms.MdbWS was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.> Work around: Ignore the message; it has no effect on the applications.	9.0
CR217889	Deploying a Web Service using a security model with custom roles or policies generates warnings about deployment descriptor roles or policies being ignored. Disregard these warning messages. Because the default security model is deployment descriptors only, these messages are not typically logged.	9.0
CR227246	The remote-client-timeout parameter was added as an WebLogic RMI compiler option in WebLogic Server 9.0. This parameter specifies an RMI-level timeout in seconds for remote clients that call the home and remote methods of the EJB. The remote-client-timeout parameter is currently not available for EJBGen.	9.0
CR231076	Monitoring information is not always available for Message Driven Beans.	9.0
CR231909	Using automatic table creation to deploy EJBs for Sybase results in every column in every table being non-null. As a result, if the EJB create method only takes a few of the CMP fields, creating EJBs fails with the following error: column does not allow nulls	9.0
CR233275	A Messaging Proxy Service still receives and routes messages after it has been deleted if the user sends the messages to it. Workaround: Do not use the JMS destination to which the deleted Messaging Proxy Service was listening.	9.0
CR234045	When WebLogic Server 7.0 or WebLogic Server 8.1 is interoperating with WebLogic Server 9.0 and WebLogic Server 9.0 throws a WorkRejectedException (for example, when WebLogic Server 9.0 is in ADMIN mode instead of RUNNING), the following exception is raised on the WebLogic Server 7.0 or 8.1 server: java.lang.ClassNotFoundException: Can't load class: weblogic.work.WorkRejectedException Workaround: Fix the problem that causes the WorkRejectedException, or use WebLogic Server 8.1-style execute queues in WebLogic Server 9.0.	9.0

 

---

Examples Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR191354	Medical Records does not yet use deployment plans.	9.0 Beta
CR200319	Examples descriptor definitions need to be updated from version 8.1 and J2EE 1.3 to version 9.0 and J2EE 1.4.	9.0 Beta	9.0
CR208963	README.TXT instructs you to run setup\config to build the domain. This is no longer necessary because the Medical Records domain template does that.	9.0 Beta
CR208965	The medrec.wls.config target in SAMPLES_HOME/server/medrec/setup/build.xml has a known issue with respect to security configuration.	9.0 Beta
CR234212	In the JMS Queue example instructions, the queue's corresponding connection factory instance is referred to as exampleQueue. However, the actual connection factory name in the Examples server is weblogic.examples.jms.QueueConnectionFactory, which is identical to the connection factory's JNDI name.	9.0
CR234523	When you start the MedRec server, the following exception is thrown: javax.naming.NameNotFoundException: While trying to look up comp/jmx/runtime in .; remaining name 'comp/jmx/runtime' This exception prevents RecordSessionEJBLifecycleListener from registering the MedRec's custom model MBean, which affects the ability to disable the feature that keeps track of how many times RecordSessionEJB writes a prescription to the database. In addition, when you stop the MedRec server and/or undeploy the medrecEar, a NullPointerException occurs in RecordSessionEJBLifecycleListener.preStop(). This exception prevents RecordSessionEJBLifecycleListener from unregistering the model MBean in the MBean server. Both issues are related to CR234476.	9.0

 

---

Installation Issues

Change Request Number	Description and Workaround	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: Use the Beehive documentation that is on the install CD rather than the documentation on the Apache website.	9.0

 

---

J2EE Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR222344	The implementation of WebLogic Web application libraries does not support the registration of listeners from tag library descriptor (TLD) files within a Web application library. Workaround: Copy the listener registration to the web.xml file in your Web module.	9.0
CR234476	In ApplicationLifecycleListeners methods such as preStop and postStart, JNDI bindings such as workarea, jmxRuntime, and UserTransaction are currently unavailable.	9.0

 

---

JDBC Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR188442	The Oracle Thin JDBC driver has not been certified with JDK 5.0. In internal testing, BEA has noted test failures with the DECIMAL data type (TAR 4019650.995). Workaround: This issue has been fixed in Oracle's 10.2.0.2 thin driver. Please obtain the driver from Oracle.	9.0 Beta	Oracle 10.2.0.2 thin driver.
CR206152	In order for multi data sources to deploy correctly on server startup, data sources listed in a multi data source must be deployed before the multi data source is deployed. Objects with the same MBean type are deployed in alphabetical order. Multi data sources and data sources are the same MBean type; therefore, multi data source names must start with a letter that is later in the alphabet than the first letter of every data source listed within the multi data source.	9.0 Beta	9.0
CR207566	When creating a JDBC data source through the Administration Console, you cannot save the data source configuration if the database server is not accessible, even if no target servers or clusters are selected. This problem occurs because the change management functionality in the Administration Console tests the data source when you attempt to save your changes. Workaround: Make sure the database is available or use the WebLogic Scripting Tool to configure the JDBC data source.	9.0 Beta	9.0
CR223899	Clear text passwords are not allowed if ProductionModeEnabled is set to true. Workaround: To deploy an application that contains application-scoped DataSource descriptors with ProductionModeEnabled set to true, the password for the Datasource must be in an encrypted format. To encrypt the Datasource password: 1. Create the domain in which you will be deploying the application. 2. From within the domain, run the following utility: java weblogic.security.Encrypt 3. Open the EAR file, and cut and paste this encrypted password into the appscoped descriptor (remove the clear text password). The usage for encrypt is simply: java weblogic.security.Encrypt <password-to-be-encrypted>	9.0
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

 

---

JMS Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR174763	During an attempt to dynamically deploy and undeploy a JMS server that is hosting a JMS module, the module destinations do not go away nor come back properly. Workaround: Redeploy every JMS module associated and let the module determine its new set of deployments.	9.0 Beta	9.0
CR189696	Upgrading a previous version of the JMS JDBC Store to the 9.0 WebLogic JDBC Store may not work if the customer is using a non-supported database version.	9.0 Beta	9.0
CR200510	JMS compatibility with previous releases does not persist a JMSdestinationMBean erroneously parented by the DomainMBean instead of the JMSServerMBean. This errors occurs because a JMSDestinationMBean that is created under the DomainMBean is not persisted anywhere. Therefore, if an error causes the configuration to be rolled back, then the JMSDestinationMBean is removed when the edit tree is compared with the runtime tree. In addition, starting and stopping the Administration Server also causes these JMSDestinationMBeans to be removed.	9.0 Beta	9.0
CR200572	A message-driven bean (MDB) cannot reach a destination configured in a JMS module that is packaged in the same EAR as the MDB unless the MDB uses the global JNDI name to find the destination.	9.0 Beta	9.0
CR202787	Dynamic attributes for SAF Imported Destinations in a JMS module cannot be changed dynamically.	9.0 Beta	9.0
CR202808	The recommended way to create JMS application modules (stand-alone or packaged) is to use the WebLogic Scripting Tool (WLST) or the Administration Console to create a JMS system module, and then copy and rename the resulting descriptor file in the domain\config\jms directory. However, when using WLST, the resulting descriptor file may not have the required -jms.xml suffix since it is not added by default. Descriptor files without a -jms.xml suffix will still work because they are not being validated.	9.0 Beta	9.0
CR205307 CR207946	A deployed Uniform Distributed Destination (UDD) cannot be dynamically undeployed using the weblogic.deployer utility. Workaround: Untarget the UDD and then restart the server.	9.0 Beta	9.0
CR206495	You cannot create a distributed destination member and its physical destination in the same edit session with the Administration Console. Workaround: 1. Click Lock and Edit in the Administration Console. 2. Create the distributed destination. 3. Activate the distributed destination, and then lock the Console again. 4. Add the member to the distributed destination and activate it again.	9.0 Beta	9.0
CR206824	When the Administration Console is used to recreate and activate a deleted JMS destination, WebLogic Server throws the following exception: weblogic.application.ModuleException: The Durable flag may only be set before activation However, the reactivation of a recreated destination does succeed in the Administration Console.	9.0 Beta	9.0
CR207765	When configuring JMS Store-and-Forward (SAF) through the Administration Console, you must configure a SAF Error Handling Name for a SAF Imported Destinations. Otherwise, the Console sets the Error Handling Name value to None, which causes the activation to fail and can cause problems at server reboot. Workaround: Always configure Error Handling for SAF Imported Destinations and its SAF Queues and SAF Topics, even if you do not require error handling. In addition, the creation of SAF Imported Destinations or SAF Queues/Topics and the configuration of Error Handling must be activated in the same "Lock and Edit" session.	9.0 Beta	9.0
CR210328	The SAFAgentRuntimeMBean statistic returns the wrong value for MesssageReceivedCount, MesssageCurrentCount, and MessagesPendingCount.	9.0
CR232327	Currently, WebLogic Server does not clean up persistent data after there has been a failed persistent store upgrade.	9.0
CR233223	Negatively acknowledged messages get a new SAF sequence number inside the messaging kernel, which causes out-of-order messages on the SAF endpoint. In the event that there are errors while forwarding messages from one server to another, messages may be dropped.	9.0

 

---

JMX Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR173079 CR193100 CR193105 CR192450 CR194792 CR206474 CR210843	The following public, non-deprecated APIs have been removed in either 8.1 or 9.0. Publication of these APIs in prior releases was erroneous. The APIs are part of BEA's internal implementation and are subject to change. In most cases, the APIs are not useful to external clients. weblogic.management.DistributedManagementException int MAX_EXCEPTIONS weblogic.management.WebLogicObjectName WebLogicObjectName(java.lang.String, java.lang.String) In weblogic.management.configuration.WTCServerMBean: all add operationsk such as addExport() all remove operations, such as removeExport() settBridgeRedirects(weblogic.management.configuration.WTCtBridgeRedirectMBean[]) setExports(weblogic.management.configuration.WTCExportMBean[]) setImports(weblogic.management.configuration.WTCImportMBean[]) setLocalTuxDoms(weblogic.management.configuration.WTCLocalTuxDomMBean[]) setPasswords(weblogic.management.configuration.WTCPasswordMBean[]) setRemoteTuxDoms(weblogic.management.configuration.WTCRemoteTuxDomMBean[])	9.0 Beta	9.0
CR173079 CR193100 CR193105 CR192450 CR194792 CR206474 CR210843 continued	The following public, non-deprecated APIs have been removed in either 8.1 or 9.0. Publication of these APIs in prior releases was erroneous. The APIs are part of BEA's internal implementation and are subject to change. In most cases, the APIs are not useful to external clients. In weblogic.management.configuration.XMLRegistryMBean: all add operations such as addEntitySpecRegistryEntry() all remove operations, such as removeParserSelectRegistryEntry() In JMSServerMBean, removeSessionPool() and addSessionPool() In ServerRuntimeInfo, getJVMID() In ServerMBean, the ExpectedToRun attribute In weblogic.management.runtime.DomainRuntimeMBean, getCurrentClusterDeploymentTarget, setCurrentClusterDeploymentTarget, getCurrentClusterDeploymentTimeout, setCurrentClusterDeploymentTimeout	9.0 Beta	9.0
CR174782 CR185687	WebLogic Server APIs and MBean operations now return javax.management.ObjectName instead of WebLogicObjectName. The WebLogic Server 9.0 JMX implementation is based on JMX 1.2, which eliminates the ability to subclass javax.management.ObjectName. The class weblogic.management.WebLogicObjectName is a subtype of ObjectName and is therefore subject to this JMX restriction. Workaround: If you wrote JMX clients to interact with prior WebLogic Server releases, and if these clients used methods such as RemoteMBeanServer.queryMBeans() or MBeanHome.getObjectName(), update the clients so that either they do not use the deprecated RemoteMBeanServer or MBeanHome interfaces, or they do not cast the return values as WebLogicObjectName.	9.0 Beta	9.0
CR176977	If a JMX application runs in a WebLogic Server 8.1 server instance or runs in a separate JVM but refers to WebLogic Server 8.1 classes in its classpath, the application throws exceptions if it uses JMX to connect to a WebLogic Server 9.0 server instance. The exceptions are a result of major changes in the JMX specification between Java 5.0 and previous versions. Workaround: Use a JMX application running in a WebLogic Server 9.0 environment.	9.0 Beta	9.0

 

---

Jolt Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR206564	Jolt session pools fail to start up in WebLogic Server.	9.0 Beta	9.0

 

---

JSP and Servlet Issues

Change Request Number	Description and Workaround	Found In	Fixed In
N/A	For this Beta release, the JSP 2.0 servlet class to be used for compiling JSPs on the server side is weblogic.servlet.JavelinxJSPServlet. Custom patterns other than *.jsp or *.jspx should be mapped to this servlet. For example: <servlet> <servlet-name>JSPServlet</servlet-name> <servlet-class>weblogic.servlet.JavelinxJSPServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>JSPServlet</servlet-name> <url-pattern>*.psp</url-pattern> </servlet-mapping>	9.0 Beta
CR203749	Some JSP code may contain variants of syntax that are not commonly supported by standard JSP compilers. The WebLogic Server 9.0 release has stricter syntactic rules than prior releases, and may reject some JSP code that previously compiled but does not adhere to the JSP 2.0 specification. For example, the following JSP syntax yields compilation errors in WebLogic Server 9.0: <%@ page import=" import javax.naming.Context; import javax.naming.InitialContext; import weblogic.management.MBeanHome; import java.lang.System; " %> To address this, an attribute in weblogic.xml has been added to enable backwards compatibility in JSPs. The syntax to enable backwards compatibility is as follows: <jsp-descriptor> <jsp-param> <param-name>backward-compatible</param-name> <param-value>true</param-value> </jsp-param> </jsp-descriptor> If a domain is automatically upgraded from a prior WebLogic Server release to WebLogic Server 9.0, then the backwardCompatible flag is automatically set, and there is no need to revise the weblogic.xml file. Code that does not adhere to the JSP 2.0 specification will not compile out-of-the-box.	9.0 Beta	9.0
CR234493	JMX reserves certain characters for its use. The names specified by users for WebLogic Server configuration artifacts or J2EE artifacts are used by WebLogic Server to create JMX ObjectNames. If a user name for any WebLogic Server configuration artifacts such as servers, or clusters, or J2EE artifacts such as beans, servlets, modules, or applications contains the following special characters: comma(,) colon(:) asterisk(*) question mark (?) equals (=) WebLogic Server will throw the following exception: java.lang.Error: Unable to build an ObjectName for the instance Workaround: Avoid using these special charectors when naming these artifacts.	9.0
CR235453	An infinite loop may occur when printing huge numbers of multi-byte characters. If your BEA_HOME is created by using these kits the Japanese, Chinese, and Korean installer kits for WebLogic Server 9.0, the fix is included in your kit. Workaround: Call customer support to request the patch for this.	9.0

 

---

JTA Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR209155	Migrating the Transaction Recovery Service as an individual service is not available in the Beta release. Attempts to migrate the service result in a null pointer exception. Workaround: Configure a migratable server in place of migrating the Transaction Recovery Service. See "Server Migration."	9.0 Beta	9.0
CR232975	The Oracle Thin driver installed with Weblogic Server may not work correctly for OCI calls if your Oracle client is not the same version or does not have the required patches. Workaround: For OCI calls, use the Oracle driver that comes with the Oracle client Installation.	9.0

 

---

Java Virtual Machine (JVM) Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR128477	Japanese characters are garbled when ISO-2022-JP encoding is used in Servlet/JSP. This problem comes from the JVM bug. For information about the JVM bug, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6221056.	9.0
CR183099	In J2SE 1.5, certain garbage collector optimizations cause virtual machine crashes. Such crashes, unlike the virtual machine crashes caused by Just-in-Time (JIT) JVMs, have no workarounds. SUN and BEA are actively working on gathering data to narrow down the root cause and provide a fix for this issue.	9.0
CR229034	An unexpected error has been detected by HotSpot Virtual Machine. For more information about this issue, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4282986. Workaround: Download the J2SE 1.5.0.4 kit provided by Sun, and put into the jdk150_04 directory instead of the jdk150_03 directory.	9.0
CR230700	On Solaris, if you use the default locale, currency values will display with "?" instead of the proper currency symbol, for example, ?100 instead of $100. This is a known Solaris problem (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4370406) and is due to the default locale having a default currency symbol that does not display properly. Workaround: Specify a real (non-default) locale, for example, en_us. The currency symbol appropriate to that locale will then be displayed.	9.0
CR231489	The -Djrockit.codegen.optpriority option has been added to improve the performance of early-running tasks, such as logging in to the Administration Console on a single-processor machine that is running WebLogic Server on JRockit. The scripts created by an install for setting up a WebLogic Server environment automatically add this option to the command line. Because the JRockit optimization thread is given lower priority, this option may delay some JRockit optimizations, which may result in a slower achievement of full performance. Workaround: Lower the priority of the optimization thread. With a Java application like an application server (Weblogic Server) or an IDE (Eclipse or Weblogic Workshop), it is usually best practice to postpone optimizing code to a later time when the system is not busy with application work. This can be achieved by assigning the optimization thread a lower priority with the JVM argument: -Djrockit.codegen.optpriority=1. This is only recommended for a single CPU machine.	9.0
CR231522	After an upgrade of MedRec from WebLogic Server 8.1 to 9.0 on Solaris, the server crashes with a JVM error. Workaround: To start the upgraded server without crashing it, remove -Xverify:none from the server start command by setting JAVA_OPTIONS="" in the setDomainEnv.sh file after the following line: . ${WL_HOME}/common/bin/commEnv.sh	9.0

 

---

Monitoring Issues

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

 

---

Node Manager Issues

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

 

---

Online Help Issues

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

 

---

Operations, Administration, and Management Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR226286	Currently if the execution of a WebLogic Server Scripting Tool (WLST) script fails, WLST ends without proper failure notification. As a result, calling components that depend on a successful WLST script execution are not aware of the failure, such as when WLST is employed via Ant, which is a common use case.	9.0
CR228706	If you use WLST as a module, you cannot overwrite another Unix user's wlst_module.py files.	9.0	Works As Designed
CR231633	Multi-byte characters are garbled when WebLogic Scripting Tool (WLST) runs in interactive mode.	9.0
CR232858	WebLogic Server Scripting Tool fails to launch when multi-byte characters are used in the installation path.	9.0
CR233635	The Managed Server fails to boot and a SecurityInitializationException is thrown if either the administrator user name or the Managed Server name includes multi-byte characters.	9.0
CR233874	The following classes have been removed for public use without deprecating them: Group LegalChecks LoggingLegalHelper Principal ServerLegalHelper WebServiceLegalHelper These classes are for internal implementation purposes only and should not have been publicized in previous releases.	8.1	9.0
CR234394	When invoking nmConnect from WLST with a Node Manager type of SSH or RSH, WLST copies the wlscontrol.sh to a temporary directory before invoking it, but the execute permission is not set for the file. As a result, the attempt to invoke nmConnect() with nmType SSH or RSH will fail. Workaround: After running java weblogic.WLST and a failed first attempt to run nmConnect(), change the file permission so that the temporary file created by WLST (for example /var/tmp/wlstTemp/wlscontrol.sh) has the execute bit on.	9.0

 

---

Plug-ins Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR217777	Deadlock occurs in Apache HTTP Server plug-in under load. When using the Apache HTTP Server plug-in for distributing client connection requests to WebLogic Server instances in a cluster, clients may be unable to connect to the cluster and the following message is logged in the Apache HTTP Server plug-in: [error] server reached MaxClients setting, consider raising the MaxClients setting This problem occurs under load on all platforms. Workaround: When configuring the Apache HTTP Server plug-in, set the value for the MaxClients parameter in the httpd.conf configuration file to be equivalent to the number of client connections that the cluster needs to be able to support. For more information about configuring the Apache HTTP Server plug-in, see "Installing and Configuring the Apache HTTP Server Plug-In" in Using Web Server Plug-Ins with WebLogic Server.	9.0 Beta	9.0
CR233476	Failover using Apache plug-in on Linux is not working because the POST requests are timing out. Workaround: Set KeepAliveEnabled=false in httpd.conf or use Apache MPM worker.	9.0

 

---

RMI-IIOP Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR113155	A CORBA client may hang if a server crashes during a the commit phase of an Object Transaction Service (OTS) managed transaction.	9.0 Beta
CR204705	WebLogic Server IIOP does not currently support the use of the JMX remote API (JSR 160) to call JMX remotely from a Java client. Workaround: If possible, use the WebLogic Thin client or the WebLogic Fat client.	9.0 Beta	9.0
CR206436	JDK-IIOP client performance degrades slowly as the number of client calls processed by a server increases. Eventually, data transmission becomes slow enough to cause a message timeout. It is most noticeable when extremely large objects are being transmitted. Workaround: If possible, use the WebLogic Thin client or the WebLogic Fat client.	9.0 Beta

 

---

Security Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR182523	Information on how to configure domains to enable inter-domain transactions (that is, all participating domains run on WebLogic Server 9.x, 8.x, 7.x, and 6.x domains or a combination of 9.x, 8.x, 7.x and 6.x) is incorrect in the Administration Console Help. Workaround: The information required to configure domains to enable inter-domain transactions is located online. See Configuring Domains for Inter-Domain Transactions in Programming WebLogic JTA.	9.0 Beta	9.2
CR200004	If the server's SSL identity is changed, the SAML credential mapper continues to use the original SSL identity until the server is re-booted. For example, the SSL configuration is dynamic but currently SAML only uses the SSL configuration available when the server booted.	9.0
CR200229	You can not change the order of security providers using the Administration Console.	9.0 Beta	9.0
CR204707	After you upgrade from Compatibility security to this release of WebLogic Server, the users and groups from the Compatibility realm are not displayed in the Administration Console.	9.0 Beta
CR204887	You can not use wildcards in the Administration Console to restrict the search of users and groups.	9.0 Beta	9.0
CR205481	Prior to this release, if you did not define a credential for the domain, the startup process for a WebLogic Server instance would create one for you. In WebLogic Server 9.0, you must define a credential for the domain before you can start any servers in the domain. A credential is generated when you create a domain. A credential is also generated by the upgrade process if one has not already been defined when you upgrade a domain from 8.1 to 9.0.	9.0 Beta	9.0
CR205481	Update security clients to use the SecurityConfigurationMBean generateCredential() operation instead of setting the SecurityConfigurationMBean CredentialGenerated attribute to true. Prior to WebLogic Server 9.0, security clients caused WebLogic Server to generate a credential for the domain by setting the SecurityConfigurationMBean CredentialGenerated attribute to true. While this behavior is maintained (and deprecated) for backwards compatibility, BEA recommends that you update your clients to use the new technique: Use the generateCredential() operation to generate and set a credential. Alternatively, define your own credential and set it as the value of the SecurityConfigurationMBean Credential attribute.	9.0 Beta	9.0
CR205933CR208534	The server cannot be locked down due to the following known problems: A user account can not be unlocked using the Administration Console. Security policies can not be set on a Server resource using the Administration Console.	9.0 Beta	9.0
CR207444	When you use the Administration Console to define security roles and policies on an individual bean in an EJB module, you cannot define credential mappings for the bean.	9.0 Beta
CR207766	The intermediate files that the WebLogic Server 9.0 BETA MBeanMaker generates erroneously includes two types of constructors for you to complete. One type is based on ModelMBean and the other type is based on RequiredModelMBean. The constructors that are based on ModelMBean will no longer be generated or supported after this Beta release. Workaround: When using MBeanMaker to create MBeans for custom security providers, supply content only for the constructors that are based on RequiredModelMBean.	9.0 Beta
CR226651	When deploying a Web application with CustomRolesAndPolicies mode, the following warning message appears: <Warning> <Security> <BEA-090669> <Ignored deployment of policy for resource "type=<url>, application=XBus Kernel, contextPath=/asdf, uri=/"> This warning also always appears at server startup.	9.0
CR231321	The option, -Dweblogic.system.StoreBootIdentity, only works if the appropriate server security directory exists which is usually created by the Configuration Wizard or upgrade tool. However, the appropriate server security directory could be absent in domains checked into source-control systems.	9.0
CR233284	The Web Service-based predicate "Element requires signature by" is listed twice when policy conditions on a Web Service resource are added. The predicate implementations are in fact the same.	9.0
CR233756	Security roles and security policies defined in deployment descriptors are not seen in the Administration Console until changes in the configuration are activated and the application is restarted.	9.0
CR233887	The 9.0 WebLogic Server javadocs mistakenly published the following internal classes that are not part of public API. Do not use them. weblogic.management.security.authentication.UserLockoutManagerImpl weblogic.management.security.audit.ContextHandlerImpl	9.0
CR234126	The addition and removal of security providers should require a reboot to appear in the runtime MBean tree. However, WebLogic Server displays the additional security providers in the runtime MBean tree immediately and so the security providers are immediately available for management operations. Even though the providers become available for management operations immediately, the server continues to use the set of providers that was present at boot time for security runtime operations (e.g. ATN, ATZ, Audit, etc.). Workaround: A reboot of the server is required for these new changes to the security framework to affect the runtime security operations. This is true for all security providers.	9.0

 

---

Spring Framework on WebLogic Server Issues

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

 

---

Start Script Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR203343	If you execute the startWebLogic script located in the WebLogic Server example domains directory (WL_HOME/samples/domains/wl_server), the incorrect page may be displayed in a browser after the server starts. Workaround: The correct script for starting the server in the wl_server domain is the startWebLogicEx script. The script, which is used by the Start Menu and QuickStart shortcuts, starts the server in the Examples domain and launches a browser to display a Web page that provides access to information about using WebLogic Server 9.0 Beta. This script is unique to the Examples server and does not accompany all domain templates. Note: With some configurations, the informational Web page is not displayed. Instead, an error window containing the following message may be displayed: Unable to open http://localhost:7001/index.jsp If this message is displayed, close the error window, and enter the following URL in your preferred Web browser: http://localhost:7001/index.jsp	9.0 Beta	9.0

 

---

Tools Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR210252	EJBGen now recognizes max-beans-in-free-pool and initial-beans-in-free-pool for entity beans.	9.0

 

---

Upgrade Wizard Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR207305	When you upgrade the WebLogic Server examples domain (WL_HOME/samples/domains/wl_server) to 9.0, the SAMPLES_HOME environment variable is set incorrectly in the setDomainEnv script for that domain. Workaround: After the upgrade is complete, open the setDomainEnv script in the samples domain and set the SAMPLES_HOME variable to the correct value. This variable should be set to the directory containing the upgraded sample application.	9.0 Beta	9.0
CR208018	The value of the JAVA_VENDOR environment variable is not retained after an upgrade. Workaround: To ensure that the correct JVM is used in a domain after it has been upgraded, make sure that the value for the JAVA_VENDOR variable is set to the correct default value in the setDomainEnv script. For example, the following code excerpt in the setDomainEnv.cmd script sets the Sun Java 2 SDK 1.5.0 as the default JVM: if "%JAVA_VENDOR%"=="BEA" ( set JAVA_HOME=%BEA_JAVA_HOME% ) else ( if "%JAVA_VENDOR%"=="Sun" ( set JAVA_HOME=%SUN_JAVA_HOME% ) else ( set JAVA_VENDOR=Sun set JAVA_HOME=C:\bea\jdk150b ) )	9.0 Beta	9.0

 

---

Utilities Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR230693	If you are using UNIX and an IOException occurs in OpenBrowser.java, either: 1. Check to see whether "netscape" can be called from the command-line (must be in the PATH), or 2. Change the default browser from Netscape to an installed browser using the unixBrowser attribute on <openbrowser> as in the following example: unixBrowser="mozilla"	9.0

 

---

Web Application Issues

Change Request Number	Description and Workaround	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: For a JPF webapp, make sure your web.xml file corresponds to version 2.4 of Sun's Servlet Deployment Descriptor Schema, which can be found at http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd.	9.0

 

---

Web Services and XML Issues

Change Request Number	Description and Workaround	Found In	Fixed In
CR135158	Use of the @javax.jws.OneWay annotation with WS-Security encryption or digital signatures is not supported.	9.0 Beta	9.0
CR179307	The jwsc Ant task returns an error if the Java Web Service (JWS) file does not contain a package statement. The error is: [jwsc] java.lang.IllegalArgumentException: Endpoint interface does not contain a package name:SimpleImplPortType Workaround: Include a package statement in the JWS file.	9.0 Beta	9.0
CR188080	The WebLogic Web Services run-time does not reuse existing security headers in the SOAP response message when adding additional security information as specified by an attached WS-Policy file. Rather, the runtime incorrectly creates a completely new security header.	9.0 Beta	9.0
CR189091	Reliable messaging XML policy files are not validated.	9.0 Beta	9.0
CR189158	WebLogic Server currently does not support Sparse Arrays and Partially Transmitted Arrays as required by the JAX-RPC 1.1 Spec.	9.0
CR189856	WebLogic Server currently does not support soap arrays when the soapenc:Array type is used directly as the type of an element as in the following example: <xs:element name="generic" type="soapenc:Array"/>	9.0
CR191716	The WebLogic Web Services run-time does not process the security header with the right role and does not reuse already existing security headers for the role.	9.0 Beta	9.0
CR195090	The jwsc WebLogic Web Services Ant task does not support generating a Web Service from a JWS file that throws a user-defined exception. Only RemoteExceptions are supported.	9.0 Beta	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
CR200545	When you encrypt a SOAP message, an error is returned if you specify a base64 transform in an Integrity assertion by setting the URI attribute of the Policy/Integrity/Target/Transform element in a WS-Policy file to http://www.w3.org/2000/09/xmldsig#base64",	9.0 Beta	9.0
CR201674	The following exception occurs when you send a null value to a Web Service method whose input parameter is of type Holder: java.rmi.RemoteException: Parameter "ParamName" is an in-out or out param. but the holder class is not passed in.	9.0 Beta	9.0
CR201970	The clientgen Ant task returns an error when run against a Web Service of type document-literal and at least one of the input parameters is of the following data type: Image, MimeMultipart, Source, or DataHandler.	9.0 Beta	9.0
CR202377	The jwsc Ant task generates an incorrect XML Schema when generating the XML artifacts of a Web Service of type document-literal bare that uses arrays as input parameters.	9.0 Beta	9.0
CR203290	The rolesReferenced attribute of the JSR-181 @javax.jws.SecurityRoles JWS annotation has not been implemented.	9.0 Beta	9.0
CR203758	WebLogic Web Services do not support multi-dimensional arrays as input parameters.	9.0 Beta
CR203762	WebLogic Web Services do not support arrays of user-defined data types as input parameters.	9.0 Beta	9.0
CR203769	The clientgen Ant task returns an error when run against a Web Service that has two or more methods, both of which use certain types of arrays as input parameters. The returned error is: weblogic.wsee.tools.WsBuildException: com.bea.xml.XmlException: C:/somepath/tempdir/WEB-INF/RpcArrayBasicJavaService.wsdl:0: error: cvc-identity-constraint.4.2.2: Duplicate key 'ArrayOfbyte' for key constraint 'type@http://www.w3.org/2001/XMLSchema' If only one method of the Web Service uses arrays, the clientgen Ant task completes without error. The Array types that cannot be parameters for two different methods within the same Web Service are as follows: Float[] & float[] --> Duplicate key 'ArrayOffloat' error Double[] & double[] --> Duplicate key 'ArrayOfdouble' error Byte[] & byte[] --> Duplicate key 'ArrayOfbyte' error Boolean[] & boolean[] --> Duplicate key 'ArrayOfboolean' error Calendar[] & Date[] --> Duplicate key 'ArrayOfdateTime' error	9.0 Beta	9.0
CR203868	Arrays as input parameters are not supported for document-style WebLogic Web Services.	9.0 Beta	9.0
CR204454	When you sign a SOAP message, an error is returned if you specify an xmldsig-filter2 transform in a Confidentiality assertion by setting the URI attribute of the Policy/Confidentiality/Target/Transform element in a WS-Policy file to http://www.w3.org/2000/09/xmldsig#base64".	9.0 Beta
CR205428	If you invoke a WebLogic Web Service that has a complex input parameter, and pass it a null value (xsi:nil='true'), the Web Service returns a javax.xml.rpc.soap.SOAPFaultException exception.	9.0 Beta	9.0
CR208416	The wsdl2service Ant task does not generate the JAX-RPC data type mapping file if the WSDL from which it is generating a Web Service specifies a fault. This means that, although you might be able to deploy the generated Web Service, you will not be able to correctly invoke its operations. Similarly, the clientgen Ant task also does not generate the client-side JAX-RPC mapping file when the WSDL file contains a fault. Workaround: Create the JAX-RPC mapping file manually.	9.0 Beta	9.0
CR218519	Applicable to jwsc, wsdlc, and clientgen: Web Service interfaces, implementations and parameter types with upper case package names may have problems building and running in some operating systems. BEA strongly recommends that you use lowercase letters for the package names.	9.0
CR223291	When a client sends an instance of complex type to a service, the service echoes back the received instance. If the complex type contains the "any" element as shown below, and the "any" content contains data, this data is not passed to the service. <element name="collection"> <complexType> <sequence> <element name="description" type="r:anycontent"/> <element ref="r:recipe" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> </element>	9.0
CR228385	The Web Service Description Language (WSDL) compiler does not generate serializable data types, so data cannot be passed to remote EJBs or stored in a JMS destination.	9.0
CR230549	WLHttpsTransport causes the following error: AsyncReponseService returned a 404	9.0
CR231508	When a WebLogic Server Web Service uses XMLObject as a parameter, a java.lang.IncompatibleClassChangeError exception is thrown at runtime when the client tries to access the service.	9.0
CR231707	After clicking the 'test' link for any Web service, WebLogic Server currently does not forward you to the stub Test Client page as it should.	9.0
CR233778	Controls declared public in a JWS File cannot be compiled using <jwsc>. When an annotated control is declared public in a JWS class (a class annotated with @WebService) and is compiled with <jwsc>, improper wrapper code is generated. This will result in a compile-time error (com.bea.util.jam.internal.javadoc.JavadocParsingException). For example, the following code will result in a compile-time error if compiled with <jwsc>, because the control myControl is a public field: @WebService public class Foo { @Control public MyControl myCtrl; ? } Workaround: Change the access modifier to private, protected, or package protected.	9.0
CR234262	The javax.xml.transform.Source attachment does not work when the source xml has non-ascii characters.	9.0
CR235270	The wsdlc Web Services Ant task cannot handle doc-literal-bare style Web Service when the element is not defined in wsdl:part as in the following example: <message name="getTempRequest"> <part name="zip" type="xsd:string"/> </message> Workaround: Add the element as in the following example: <message name="getTempRequest"> <part name="zip" element="s0:getTemp" type="xsd:string"/> </message>	9.0
CR237192	The @weblogic.jws.security.SecurityRoles JWS annotation only works at the operation-level; specifying it at the class-level in your JWS file has no effect at all.	9.0
CR237196	The @weblogic.jws.security.SecurityIdentity JWS annotation does not work as documented; specifying it in your JWS file has no effect at all.	9.0

 

---

WebLogic Tuxedo Connector Issues

Change Request Number	Description and Workaround	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 to 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: 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
CR128581	Limitation exists in WTC to handle only one large FML table. This limitation crashes Workshop JVM. mkfldclass32 should now issue a warning when a field table will grow too large to be handled as a static class.	8.1	9.0
CR171892	A failure with WTC tpacall/tpenqueue/tpdequeue/tpconnect with TPNOTRAN flag set forces the rollback of the transaction, although it should not.	8.1 SP2	9.0
CR194844	You cannot configure WTC failover for two Tuxedo domains with the same access point ID. Link-level failover supporting comma-separated listing in the NWAddr attribute for LocalTuxDom and RemoteTuxDom is available in WLS 9.0.	8.1	9.0
CR202460	WebLogic Server deadlocks when all ExecuteThreads are busy waiting for replies in weblogic.iiop.SequencedRequestMessage.waitForData.	8.1 SP2	9.0