WebLogic Server

http://e-docs.bea.com/wls/docs81/notes/index.html

WebLogic Workshop

http://e-docs.bea.com/workshop/docs81/relnotes/relnotes.html

WebLogic Integration

http://e-docs.bea.com/wli/docs81/relnotes/index.html

WebLogic Portal

http://e-docs.bea.com/wlp/docs81/relnotes/relnotes.html

BEA JRockit

http://e-docs.bea.com/wljrockit/docs142/relnotes/relnotes.html

Date

Description

08/18/06

Added support for MircoSoft SQL Server 2005. See Database Support for 8.1 SP6 in Supported Configurations for WebLogic Platform 8.1.

08/18/06

Added CR287393, which addresses how to use the Config Wizard to create a JDBC connection pool when the database is MircoSoft SQL Server 2005, to Known Limitations.

12/02/05

Added CR248707, which addresses the removal of the WebLogic Workshop IDE from a production environment, to Known Limitations.

WLST Online

As a download from dev2dev.

The software, including documentation that explains how to set up and use WLST Online, is available at the following Web site:

https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=13

As of SP5, WLST Online is supported for use with all releases of WebLogic Platform 7.0 and 8.1.

WLST Offline

As a set of JAR files and scripts bundled with the WebLogic Platform 8.1 SP5 software.

Instructions for setting up and using WLST Offline, as well as sample scripts for configuring domains, are available from dev2dev at the following Web site:

https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=97

WLST Offline is now supported for use with WebLogic Platform 8.1 SP5 and later service packs only.

WLST Offline is not supported in WebLogic Platform 7.0, or in releases of WebLogic Platform 8.1 prior to SP5.

HP-UX

For Itanium-based systems, download and install the latest Runtime plug-in version 1.4.2 from:

http://www.hp.com/products1/unix/java/java2/jpi/downloads/

For PA-RISC-based systems, download and install the latest Runtime Environment for Java version 1.4.2 from:

http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/index_pa-risc.html

Red Hat Enterprise Linux

Complete the following steps:

1. Go to the following URL and choose Download J2SE JRE: http://java.sun.com/j2se/1.4.2/download.html.

2. Accept the licence agreement that is displayed.

3. Choose either the RPM in self-extracting file, or the self-extracting file.

Sun Solaris

Complete the following steps:

1. Go to the following URL and choose Download J2SE JRE: http://java.sun.com/j2se/1.4.2/download.html.

2. Accept the licence agreement that is displayed.

3. Choose the JRE appropriate for your system.

CR258654

When there is an invalid login attempt, while using the com.bea.p13n.controls.login.UserLoginControl, only a `Failed Authentication' exception message is displayed. A more descriptive message is required to be displayed to the user.

Workaround: The Authentication.java throws the Login Exception. Modify the Authentication.java to call the WebLogic Server servlet authentication method. Put a switch in Authentication to specify either to function as before or propagate the LoginException upward.

CR097633

Each script in WL_HOME/common/eval/pointbase/tools/startPointBaseConsole requires a PointBase Server to be started independently

If a PointBase Server is not running when the PointBase Console is launched, the Connect to the Database option fails with an error message (SQL State 08004).

Operating System: All

Workaround: Before launching either a domain-based startPointBaseConsole script or the PointBase Console (from one of the Example links on the Start menu), start the WebLogic Server for the relevant domain. As it starts each domain, WebLogic Server also starts the PointBase Server associated with the domain.

When you log in to the database console (by selecting Connect to the Database), enter weblogic as both your user ID and your password.

CR099617

Restrict the addition of an application via extension template if the application already exists in the domain

The Configuration Wizard allows you to extend a domain using an extension template that contains an application name that already exists in the target domain. As a result, two applications of the same name will end up in the config.xml file for the domain.

Operating System: All

Workaround: No workaround exists. Make sure that any extension template you plan to use does not contain an application with the same name as an application in your domain.

CR107937/
34347

Workshop Web service fails to invoke secure WebLogic Server Web service due to a missing timestamp header

Interoperability between Workshop Web services and a secure WebLogic Server Web service is currently not supported.

Operating System: All

Workaround: N/A

CR108897/
12823

Windows-31J is not included in versions 1.4.0 through 1.4.1_03 of the Sun Java 2 SDK

The WebLogic Workshop 8.1 IDE and compiler use a new API from Sun called java.nio.Charset (introduced in the Sun Java 2 SDK 1.4.0). The implementation of this API contains a bug: Windows-31J, the Japanese character set most commonly used in Windows, is not included in versions 1.4.0 through 1.4.1_03 of the Sun Java 2 SDK. For details, see:

http://developer.java.sun.com/developer/bugParade/bugs/4626545.html

The absence of Windows-31J does not mean that users cannot read and write their files using Japanese; other character sets are available. If, however, characters from a character set other than Windows-31J are included in an IDE file, the IDE fails silently: it allows the user to save the file, without issuing a warning that the file has been corrupted by the inclusion of non-Windows-31J characters.

This problem will be solved in two future versions of the Sun Java 2 SDK: 1.4.1_05 and 1.4.2. These versions will include the Windows-31J (MS932) character set.

Operating System: All

Workaround: For types of files that may include encoding headers, including HTML, XML, and JSP files, specify UTF-8, instead of Windows -31J, for the file's encoding.

CR109961

If you change the DBMS Name for PointBase on Configure JDBC Connection Pools, the database files are not renamed

In the Configuration Wizard window labeled Configure JDBC Connection Pools, you can change the values of several PointBase parameters: DBMS Name, Dbms Host, Dbms Port, User Name, and User Password. Your changes, however, are reflected only in the config.xml file for your domain; your PointBase database files and startup scripts are not updated with the new values.

Operating System: All

Workaround: When using the Configuration Wizard and a PointBase database, always accept the default values for DBMS Name, DBMS Host, DBMS Port, User Name, and User Password.

CR110086

The PointBase database must use port number 9093

The Configuration Wizard offers the option of changing the port number used by PointBase from the default. If you do change the PointBase port number, however, the test connection for the database fails and the server cannot start properly.

Operating System: All

Workaround: Always accept the default port number for PointBase: 9093.

CR110828

When you try to stop the server by entering Ctrl+c, the PointBase process running in the background is not killed

If you enter Ctrl+c to stop a server on a platform comprising Windows and PointBase, and then try to start a different server, you may get exceptions, but you will not get any obvious clues about the problem.

Operating System: All

Workaround: On Windows platforms, run the stopWeblogic script (stopWebLogic.cmd on Windows or stopWebLogic.sh on UNIX) to shut down the server and all related processes.

CR110893

Generated stopWebLogic script cannot stop PointBase configured at a nondefault port

The Configuration Wizard does not customize the stopWebLogic script (stopWebLogic.cmd on Windows or stopWebLogic.sh on UNIX) of a created domain with a user-specified PointBase port number. When the server is shut down from a WebLogic Server console, the PointBase server is left running.

Operating System: All

Workaround: You have a choice of two workarounds:

• Run the stopWebLogic script to force a shutdown of the WebLogic Server.

• Shut down the WebLogic Server from the WebLogic Server console and then run the stopWebLogic script again.

CR111126/
36644

Corrupted connections in connection pool using MS SQL Server and XA are used

Shared use of a JDBC connection pool for global (XA) transactions by multiple Data Sources creates recovery problems in the event of a failure.

Operating System: All

Workaround: If you are using an MS SQL Server driver and corrupted connections have already occurred, adjust the JDBC Connection Pool configuration in the WebLogic Server Administration Console by doing the following:

1. With the Administration Server running, log in to your domain's Administration Console and navigate to domain_name—>Services—>JDBC—>Connection Pools—>pool_name.

2. Click Show to display the Advanced Options section.

3. Check Test Reserved Connections to enable your reserved connections.

4. In the Test Table Name field, enter dbo.sysusers.

5. Click Apply.

The corrupted connections are no longer used.

CR125469

A java.lang.IncompatibleClassChangeError exception is generated when the clientgen or autotype Ant task is executed to generate non-built-in data type components from an XML Schema file

This problem happens only when the following two circumstances occur simultaneously: (a) the wlxbean.jar and xbean.jar files are specified in the CLASSPATH variable for your build or deployment environment; and (b) you are using the clientgen or autotype Ant task to generate non-built-in data type components from an XML Schema that references SOAP encoding data types. The two JAR files, used by the XMLBeans feature, are part of WebLogic Platform and Workshop; they are not part of WebLogic Server. The JAR files contain SOAP-encoding data type classes that conflict with those generated by the Ant tasks.

This problem is discussed further in FAQs: Web Services in WebLogic Server Frequently Asked Questions.

Operating System: All

Workaround: Use any of the following three ways to work around this problem:

1. Use the packageName or packageBase attribute of the autotype Ant task (or the typePackageName or typePackageBase attribute of the clientgen Ant task) to force the Ant-task-generated SOAP-encoding data types into a user-specified package so that they do not conflict with the XMLBeans data types. For information about the attributes of the autotype and client Ant tasks, see Web Service Ant Tasks and Command-Line Utilities.

2. Remove the xbean.jar and wlxbean.jar files from your build and deployment environment. These files are installed in the WL_HOME\server\lib directory by WebLogic Platform, where WL_HOME refers to the main WebLogic Platform installation directory, such as c:\beahome\weblogic81. If you need these JAR files (because some of your Web Services use XMLBeans), then do the following: (a) find all the EAR files that contain WebLogic Web Services that, in turn, use XMLBeans; and (b) put a copy of the two JAR files (xbean.jar and wlxbean.jar) in the APP-INF/lib directory of each such EAR file.

3. If you do not use WebLogic Workshop to create applications, or if you do not deploy any applications generated by WebLogic Workshop, then you can remove the conflicting SOAP-encoding classes from the wlxbean.jar and xbean.jar files.

CR126214

When Smart Update is used to revert a Service Pack installation, the End-to-End sample application domain is not reverted

After a WebLogic Platform installation is reverted from SP2 to a previous release, the End-to-End sample application does not start.

Operating System: All

Workaround: After you revert a WebLogic Platform installation, restart the server in the End-to-End sample application domain you are using.

CR126952/
CR126651/
CR127350

Upgrade installer overwrites all user applications in the samples directory

As part of the upgrade procedure, the WebLogic Platform 8.1 SP2 installation program automatically overwrites any files, including applications, that you have created in WL_HOME.

Operating System: All

Workaround: Before installing SP2, make backup copies of any files or applications that you have created in WL_HOME. As a general best practice, however, if you want to ensure that your application files are untouched by newer installations of WebLogic Platform, create new domains outside of the BEA product directory.

For more detailed information regarding additional workarounds, please contact BEA Customer Support and reference CR126952.

CR128232/
43254

WebLogic Integration and End-to-End sample domains log MDB warnings during server startup

When the server is started in either a Platform or End-to-end sample domain, the following messages are logged:

• <BEA-014006> <The message driven bean (MDB) named "ProcessTrackingEventErrorListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.>

• <BEA-014006> <The message driven bean (MDB) named "InstanceInfoEventListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.>

• <BEA-014006> <The message driven bean (MDB) named "ProcessTrackingEventListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.>

Operating System: All

Workaround: These messages are advisory; they can be ignored. It is possible, by using the WebLogic Server Administration Console, to create the execute queues listed in these logged messages in such a way that they contain the listed EJBs. If you create execute queues in this way, however, make sure that you specify a thread size that accommodates the relevant application and tracking level. For more information about creating execute queues, see "Execute Queue —>  Configuration" in the WebLogic Server Administration Console Online Help at the following URL:

http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_executequeue_config.html

CR135846

Use of org.apache.xalan.processor.TransformerFactoryImpl causes portability issues

In the weblogic.xml.jaxp.WebLogicTransformerFactory API, the constructor is using org.apache.xalan.processor.TransformerFactoryImpl as the default. This behavior contradicts the specification in the WebLogic Server Administration Console Online Help document (http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_xmlregistry_config.html), which specifies weblogic.apache.xalan.processor.TransformerFactoryImpl as the default.

Also, use of the Xalan transformer obtained directly from Apache causes portability issues, because this version is newer than the JAXP currently shipped with WebLogic Server.

Operating System: All

Workaround: Set the Transformer Factory to weblogic.apache.xalan.processor.TransformerFactoryImpl. For details, see:

http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html

CR137592

Java error when running Workshop without Administrator privileges

If you install WebLogic Workshop on a Windows system as a user with Administrator privileges, then all users must have Administrator privileges to use Workshop. Otherwise, users without Administrator privileges receive the following error when running a Workshop application:

java.lang.SecurityException: Could not open windows registry node Software\JavaSoft\prefs at root 0x80000002: Access Denied

Operating system: Windows

Workaround: On Windows systems, install and use WebLogic Workshop as a user with Administrator privileges.

CR172412

Distributed queues assigned to an additional cluster cannot be configured because they do not appear in the JMS Queue dropdown list in the Configuration Wizard

When using the Configuration Wizard to create a multi-cluster domain, a problem exists in the Configure JMS Distributed Queue Members window. This problem occurs when adding a distributed queue member to a JMS distributed queue that has been assigned to a second cluster. When you click on the queue, and click the Add button, the JMS Queue dropdown list is empty. This prevents you from using the Configuration Wizard to assign distributed queue members to a JMS distributed queue not on the primary cluster.

Operating system: All

Workaround: After creating the domain, use the WebLogic Server Administration Console to configure JMS distributed queues as follows:

1. Start the Administration Server and the Administration Console.

2. In the Administration Console, select Services—> JMS—> Distributed Destinations.

3. Select the Distributed Destination to configure.

4. Select the AutoDeploy tab, and add the distributed queue members for the desired JMS distributed queue.

CR181310

Anonymous login to Web application resources under certain circumstances can fail

If your config.xml file contains the flag FullyDelegateAuthorization=true, anonymous access to resources in a Web application are denied when those resources have no security restraints specified in the application's web.xml file.

This combination, namely, flag FullyDelegateAuthorization=true, along with the value of CLIENT-CERT in the <login-config> element of the web.xml file, causes anonymous access to any resource within the Web application to fail with the following error: 401 - Unauthorized.

Operating System: All

Workarounds: (1) If you require these settings and the use of CLIENT-CERT, you need to create a descriptor constraint for each of the resource URLs used by the Web application. For more information about using CLIENT-CERT, see "Two-Way SSL" in the WebLogic Workshop Help at the following URL:

http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/security/transport/conTwoWaySSL.html

(2) If you are not using WebLogic Integration, you can change FullyDelegateAuthorization from true to false.

CR181772

Domain administration port: error starting managed server on same machine as Administration Server

When a cluster domain is configured with Managed Servers on multiple machines, including a machine that hosts both a Managed Server and the Administration Server, errors are generated in the log file for the Managed Server that is on the same machine as the Administration Server.

Operating System: All

Workaround: The administration port accepts only secure, SSL traffic, and all connections via the port require authentication. Enabling the administration port imposes the following restrictions on your domain:

• The Administration Server and all Managed Servers in your domain must be configured with support for the SSL protocol. Managed Servers that do not support SSL cannot connect with the Administration Server during startup—you will have to disable the administration port in order to configure them.

• Because all server instances in the domain must enable or disable the administration port at the same time, you configure the administration port at the domain level. You can change an individual Managed Server's administration port number, but you cannot enable or disable the administration port for an individual Managed Server. The ability to change the port number is useful if you have multiple server instances with the same Listen Address.

• After you enable the administration port, you must establish an SSL connection to the Administration Server in order to start any Managed Server in the domain. This applies whether you start Managed Servers manually, at the command line, or using Node Manager. For instructions to establish the SSL connection, see "Booting Managed Servers to Use Administration Port" in "Configuring Network Resources" in Configuring and Managing WebLogic Server at the following URL:

http://e-docs.bea.com/wls/docs81/adminguide/network.html

• After enabling the administration port, all Administration Console traffic must connect via the administration port.

• If multiple server instances run on the same computer in a domain that uses a domain-wide administration port, you must either: host the server instances on a multi-homed machine and assign each server instance a unique listen address; or, override the domain-wide port on all but one of one of the servers instances on the machine. Override the port using the Local Administration Port Override option on the Advanced Attributes portion of the Server—>  Connections—>  SSL Ports page in the Administration Console.

CR182698

Smart Update fails to complete on Red Hat Linux 64-bit systems

When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux 3.0 on Itanium systems, Smart Update hangs and does not complete the installation. (Smart Update works on Red Hat Enterprise Linux 2.1 on Itanium, but not 3.0.)

Operating System: Red Hat Enterprise Linux AS, ES 3.0 on Itanium

Workaround: Do not use Smart Update to upgrade to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux 3.0. Either use the upgrade installer, or perform a new installation of WebLogic Server 8.1 SP3.

For more information about using the upgrade installer, see "Installing Service Packs and Rolling Patches Using a Downloadable Upgrade Installer" in "Installing Service Packs and Rolling Patches" in Installing BEA WebLogic Platform at the following URL:

http://e-docs.bea.com/platform/docs81/install/update.html

Note that if you are simultaneously upgrading WebLogic Server 8.1 and Red Hat Enterprise Linux (from 2.1 to 3.0), you can complete the following procedure to use Smart Update successfully to upgrade to SP3:

1. Upgrade WebLogic Server 8.1 to SP3.

2. Upgrade your machine from Red Hat Enterprise Linux 2.1 to 3.0.

CR183569

Sun JDK HotSpot compiler crashes when precompiling JSPs in production mode (-server) with debug enabled

In domains configured with the Sun Java 2 SDK 1.4.2_04, the Sun JDK HotSpot compiler can crash while precompiling JSPs with a HotSpot Virtual Machine Error. A log similar to the following may be generated:

# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_04-b05 mixed mode)
#
# Error ID: 53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=5 tid=0x2d48f578 nid=0xc10 runnable
#

This problem is most likely to occur with the following JVM command-line options:

-server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -java.compiler=NONE -ea -da:com.bea...
-da:javelin... -da:weblogic...

Operating System: All

Workaround: Any of the following workarounds prevent this problem from occurring:

• Use the BEA JRockit SDK instead of the Sun Java 2 SDK.

• Edit the WebLogic Server start script to start using the -client (not -server) option when debugging with Sun Java 2 SDK 1.4.2_04.

• Disable debugging, either by editing the setDomainEnv script, or by manually removing the JVM debug arguments.

• Don't precompile when debugging.

• Update the domain configuration to use the Sun Java 2 SDK 1.4.2_05 or later.

CR192264

EAR file component with pathname longer than 255 characters may not be accessible

Before an EAR file is deployed on a domain, it is exploded to the.applications folder. When the combined length of (a) the full path of the domain that includes a particular component, and (b) the relative path of the component itself exceeds 255 characters, the component in question cannot be located.

Operating System: Windows

Workaround: Keep the domain path as short as possible.

CR203645

When you add a Managed Server to a cluster in an existing domain, the domain fails to start

If you add a Managed Server to a cluster in an existing domain, the updated domain fails to boot. This limitation exists if you attempt to add the Managed Server outside the scope of creating a new domain or modifying an existing domain via an extension template.

Operating System: All

Workaround: To add a Managed Server to a cluster, you must add the server via either a domain or a domain extension template. For example, you can add a Managed Server to an existing domain via the Configuration Wizard or WLST Offline in either of the following ways:

• You can extend the domain via an extension template. While applying the extension template, you can specify the additional Managed Server.

• You can create a template of the existing domain, then create a new domain based on that template in which you specify the additional Managed Server.

CR204361

When creating an extension template, the JMSDistributedQueues in a cluster domain are lost

When using the Template Builder to create an extension template of a clustered domain that includes JMS distributed queues, those queues are excluded from the resulting template.

Operating System: All

Workaround: At the time you use the resulting template to extend a domain, configure each JMS distributed queue as required.

CR204521

Downgrading from SP5 to SP4 or SP3 may fail on HP-UX if maxdsiz is too small

If you upgrade from 8.1 SP3 to 8.1 SP4, or from 8.1 SP4 to 8.1 SP5, by using Smart Update or the Upgrade Installer on an HP-UX 11.0 or 11i on PA-RISC configuration, and then try to use the same tool to downgrade from 8.1 SP5 to 8.1 SP4, or 8.1 SP4 to 8.1 SP3, the downgrade attempt may fail.

Operating system: HP-UX 11.0, 11i on PA-RISC

Workaround:

• When downgrading from 8.1 SP5 to SP4, set the maxdsiz kernel parameter to 1 GB or higher.

• When downgrading from 8.1 SP4 to SP3, set the maxdsiz kernel parameter to 2 GB or higher.

CR206782

Error encountered while upgrading from SP2 to SP3 on AIX

If you upgrade WebLogic Platform from 8.1 SP2 to 8.1 SP3 on AIX, the upgrade process might fail before completion with the following message:

Fatal error. Cannot move libmuxer.so which is in use.

This condition occurs due to improper system memory cleanup when WebLogic Server 8.1 SP2 shuts down.

Operating system: IBM AIX 5.1 or 5.2 PowerPC, POWER3, POWER4, and POWER5

Workaround: Before upgrading to SP3, you must manually clean out any unused libraries on your machine by using the slibclean command, which you must execute as root. (Note that rebooting the machine after running this command is not necessary.)

CR208487

Applications fail to launch from QuickStart if the installation directory name includes High-ASCII characters

If the directory name for either the BEA Home or WebLogic Home directories contains characters from the High-ASCII character set, you cannot use QuickStart to launch applications, such as the Configuration Wizard. This is a limitation imposed by the Sun Java 2 J2SE.

Operating system: Any system in which the Sun Java 2 J2SE is used

Workaround: If you plan to use QuickStart to launch applications, during installation you should choose directories for BEA Home and WebLogic Server Home with names that include only the ASCII character set.

CR209566

The 'ulimit -n' command to limit the number of open file descriptors is not provided in commEnv.sh on HP-UX platforms

On many UNIX platforms, WL_HOME/common/bin/commEnv.sh script invokes the ulimit -n command to set the upper limit of number of open file descriptors to 1024 before WebLogic Server is started. However the -n option of the ulimit command is not supported by HP-UX shells (except ksh). In WLS8.1SP5, the commEnv.sh script does not set the upper limit of open file descriptors for HP-UX.

Operating system: HP-UX 11.0, 11i on PA-RISC

Workaround: In your shell environment, you can manually limit the number of open file descriptors, which should be set to less than 1024.

CR212708

Smart Update hangs during upgrade to SP4 on HP-UX

If you use Smart Update to upgrade WebLogic Platform 8.1 on HP-UX 11i Itanium systems, the upgrade procedure hangs before running to completion. This problem occurs when you upgrade to any service pack of WebLogic Platform 8.1.

Operating system: HP-UX 11i Itanium

Workaround: Use the package upgrade installer instead of Smart Update for upgrading a WebLogic Platform 8.1 installation. For more information, see "Installing Service Packs and Rolling Patches Using a Downloadable Upgrade Installer" in "Installing Service Packs and Rolling Patches" in Installing BEA WebLogic Platform at the following URL:

http://e-docs.bea.com/platform/docs81/install/update.html

CR226286

WLST failures should cause WLST to exit with failure

Currently if the execution of a WebLogic Server Scripting Tool (WLST) script fails, WLST terminates without sending a 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.

Operating System: All

Workaround: When invoking WLST from an Ant script, it is recommended that you fork a new JVM by specifying fork="true". This will ensure a clean environment and prevent the WLST exit command, which calls System.exit(0), from exiting the Ant script.

CR228706

Cannot overwrite another user's wlst_module.py file

If you use WLST as a module, you are unable to overwrite another user's wlst_module.py files.

Operating System: UNIX

Workaround: Make sure you have write permissions to the directory specified by the java.io.tmpdir Java system property.

CR231633

Multibyte characters are garbled when WLST runs in interactive mode

If you install WebLogic Platform on a machine that is configured with the multibyte character set, and launch WLST from a command window prompt, the output generated by WLST—in both the command window as well as any files into which WLST writes—is garbled.

This problem occurs only when WLST is used offline in interactive mode; that is, when not connected to a running WebLogic Server instance.

Operating System: All

Workaround: On machines configured with the multibyte character set, use WLST offline in script mode.

CR232858

WLST fails to launch when multibyte characters are used in the installation path

If the names of the directories in which WebLogic Platform is installed contain multibyte characters, attempting to start WLST from a command window fails, and an error message similar to the following example is displayed:

>Initializing WebLogic Scripting Tool (WLST) ...
>Problem invoking WLST - Traceback (innermost last):
> File "<string>", line 7, in ?
>ImportError: No module named plateng

Operating System: All

Workaround: When installing WebLogic Platform, do not specify directories for BEA Home or WebLogic Home that have names containing the multibyte character set.

CR235573

Failover with Oracle RAC takes longer than the time specified in Test Interval in RDBMSAuthenticator

In a domain configured with Oracle RAC, the length of time required for failover to a secondary RAC node to complete is longer than the time specified in the Test Interval parameter in the RDBMSAuthenticator window.

Operating System: All

Workaround: The RDBMSAuthenticator will failover to a secondary RAC node only after detecting a database connection failure, either through failed user authentication attempts or through RDBMSAuthenticator connection tests. Connections that fail the tests are closed and reopened to re-establish a valid physical database connection, as determined by the Test Interval parameter specified while creating the RDBMSAuthenticator.

The Test Interval setting should be based on a trade-off between system availability requirements and database performance impact. Lower settings will reduce the amount of time to detect RAC failures and reduce the likelihood of failed user authentication attempts, but will increase the database load. The default setting is 120 seconds. To minimize failed user authentication attempts due to RAC failures, set the Test Interval parameter to its minimum value of 5 seconds.

With the Administration Server running, log in to your domain's Administration Console and navigate to Security—> Realms—> myrealm—> Providers—> Authentication—> RDBMSauthenticator. Select the Details tab—> Test Interval. The Test Interval parameter sets the amount of time for connections to be closed and re-established.

CR237216
CR241625

Japanese characters are garbled in the graphical user interface to the installation program, Configuration Wizard, and Template Builder

On Red Hat Enterprise Linux 4.0 systems configured with the Japanese character set, the graphical user interfaces to the installation program, Configuration Wizard, and Template Builder fail to display correctly. This problem is caused by a limitation in the Sun Java 2 J2SE 1.4.2_08 JDK, which does not have the font.properties files for the Japanese character set for Red Hat Enterprise Linux 4.0 systems.

Operating System: Red Hat Enterprise Linux 4.0

Workaround: Use the console-mode interfaces to these applications.

Note: This limitation does not exist on Red Hat Enterprise Linux 3.0 systems. However, for Red Hat Enterprise Linux 4.0 systems, Sun provides a workaround that is described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6235633.

CR248707

Cannot install WebLogic Integration in a production environment without also installing the WebLogic Workshop IDE

In WebLogic Platform 8.1 SP5, when you use a custom or silent-mode installation method to install the WebLogic Integration server component, both the WebLogic Workshop Runtime Framework and the IDE are installed. Only the WebLogic Workshop Runtime Framework should be installed with the WebLogic Integration server component.

Operating System: All

Workaround: To remove the WebLogic Workshop IDE from a production environment, manually delete the BEA_HOME\weblogic81\workshop directory and files.

CR287393

When using the Config Wizard to configure a JDBC pool connection, if you choose MS SQL Server as the database, the drop down for drivers does not list MS SQL 2005 as an option.

Workaround: Depending on whether the pool is XA or non-XA, choose:

• The BEA MS SQL Server Driver ( Type 4XA) Versions:7.0,2000 or

• The BEA MS SQL Server Driver ( Type 4) Versions:7.0,2000

CR283816

WLS 8.1 SP6 B2B Soaks with MSSQL Database fails with XA Exception.

In WebLogic Platform 8.1SP6, when JDBC connection pools have the ShrinkingEnabled attribute set to true, the 3.5 Data Direct driver used to fail long-running tests.

Workaround: For optimal JDBC pool performance and stability, set ShrinkingEnabled attribute to false.

CR127141

Exception occurs while the End-to-End server is being shut down

If you boot the End-to-End server and then run the stopWebLogic script (stopWebLogic on Windows, stopWebLogic.sh on UNIX), the stopWebLogic script throws an exception on the server console.

Operating System: All

Workaround: N/A.

Fix Information: In SP3, the exception occurred while applications were being undeployed. In SP4, this problem no longer occurs because multiple applications with the same LoadOrder are deployed and undeployed in alphabetical order of deployment name.

CR181354

Application-scoped roles cause an error dialog to be displayed in the Workshop IDE

After creating security roles in the Workshop IDE, an error dialog box is displayed with the following message:

Authentication failure when connecting to the server

This error does not prevent application deployment or role creation, but will occur with domains that are based on the Basic WebLogic Portal Domain template or Basic WebLogic Platform Domain template. The cause of this error is nominally the Identity Assertion security provider that is required for the Web Services for Remote Portals (WSRP) feature of WebLogic Portal, and occurs when the classloader of the JVM for the Workshop IDE is unable to locate the JAR file for that security provider. However, this error can occur with any custom security provider that cannot be located by the IDE JVM classloader.

Operating System: All

Workaround: The JAR file for the WSRP Identify Assertion provider, as well as any additional custom security provider configured for your domain, needs to be added to the classpath for the Workshop IDE. The IDE classpath is specified in the file WL_HOME/workshop/Workshop.cfg.

Fix Information: The Manifest.mf file for wlw-ide.jar has been changed such that wsrp-security-providers.jar is added to the Shared-Class-Path entry.

CR182859

Domains created with the Configuration Wizard using non-XA compliant JDBC drivers are configured with EnableTwoPhaseCommit=true, which can result in data risks under certain failure conditions

When the Configuration Wizard tool is used to configure a domain using non-XA JDBC drivers, the EnableTwoPhaseCommit setting on Tx Data Source(s) is set to true by default. In some cases, under failure conditions, this setting can result in data risks as described in "Limitations and Risks When Using a Non-XA Driver in Global Transactions" in the WebLogic Server Administration Console Online Help at the following URL:

http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html

Operating System: All

Workaround: The EnableTwoPhaseCommit=true setting applies only when non-XA JDBC drivers are used. This setting is used to allow non-XA drivers to participate in XA transactions. If XA-compliant JDBC drivers are used (preferred), this issue does not apply. Depending on the resources involved in a distributed transaction, this setting may or may not be used. This setting is described in the following topics in the WebLogic Server Administration Console Online Help:

• "Configuring Non-XA JDBC Drivers for Distributed Transactions" in "Connection Pool and Data Source Configuration Guidelines" in "JDBC Connection Pools" at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_connection_pools.html

• "JDBC DataSources" at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html

To summarize the key information from the preceding topics:

• If the only resource involved in a distributed transaction is a non-XA connection pool resource, use the EnableTwoPhaseCommit=false setting on the Tx Data Source. In this case, the setting is ignored and one-phase commit is used. The data risks under failure are not present.

• If more than one resource is used in a distributed transaction, but only one non-XA connection pool resource is involved, it is necessary to set EnableTwoPhaseCommit=true on the Tx Data Source to avoid errors during XA prepare. In this case, the data risks described in the preceding link are present because two-phase commit is being simulated for this resource.