Release Notes

WebLogic Server 8.1 Known Issues

The following sections describe known issues, levels of support, notes, and general problems in WebLogic Server8.1 and its service packs:

Known Issues in WebLogic Server 8.1 SP6

Core Known Issues

Change Request Number

Description

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp6` patch.

Change Request Number	Description
CR263825	You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the `CR263825_810sp6` patch.

JDBC Known Issues

Change Request Number

Description

CR280439

There is a performance degradation in the WebLogic Type 4 JDBC Driver for Oracle `getAsciiStream()` method call caused by fixes and enhancements to character set support in the driver. In general, the updated driver outperforms the previous version of the driver.

Workaround or Solution:

Use the `getCharacterStream()` method instead of `getAsciiStream()`.

Change Request Number	Description
CR280439	There is a performance degradation in the WebLogic Type 4 JDBC Driver for Oracle `getAsciiStream()` method call caused by fixes and enhancements to character set support in the driver. In general, the updated driver outperforms the previous version of the driver. Workaround or Solution: Use the `getCharacterStream()` method instead of `getAsciiStream()`.

JTA Known Issues

Change Request Number

Description

CR259037

When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.

Workaround or Solution:

Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Change Request Number	Description
CR259037	When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other. Workaround or Solution: Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Servlets & JSPs Known Issues

Change Request Number	Description
CR262289	When calling the `close()` method on the `InputStream` obtained from the `HttpsURLConnection` class, the underlying SSL socket might not be closed even when the `disconnect()` method is called. This can result in a socket leak. Workaround or Solution: To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the `HttpsURLConnection#disconnect()` method instead of the `InputStream#close()` method.

Change Request Number

Description

CR262289

When calling the close() method on the InputStream obtained from the HttpsURLConnection class, the underlying SSL socket might not be closed even when the disconnect() method is called. This can result in a socket leak.

Workaround or Solution:

To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the HttpsURLConnection#disconnect() method instead of the InputStream#close() method.

Console Help Know Issues

Change Request Number	Description
CR227849	Unable to start WebLogic Server after changing the password from the Administration Console. Workaround or Solution: After you change the user password from the Administration Console, make sure that you also change the password in the `<domain directory>/boot.properties` file. In this file, the password is stored in the encrypted format. However, when you edit the file, you can enter the password in clear text. After restarting the server, the password is automatically encrypted and stored in the file. Note: Updating the password in the `boot.properties` file is applicable to both Administration Server and Managed Servers. To remotely start Managed Servers from the Administration Console, after changing the password, in addition to changing the password in the `boot.properties` file, make sure that you change the password from the Remote Start tab in the Administration Console. For information about changing the password from the console, see "Changing the Password of a User" in Security in Administration Console Online Help.

Change Request Number

Description

CR227849

Unable to start WebLogic Server after changing the password from the Administration Console.

Workaround or Solution:

After you change the user password from the Administration Console, make sure that you also change the password in the <domain directory>/boot.properties file. In this file, the password is stored in the encrypted format. However, when you edit the file, you can enter the password in clear text. After restarting the server, the password is automatically encrypted and stored in the file.

Note: Updating the password in the boot.properties file is applicable to both Administration Server and Managed Servers.

To remotely start Managed Servers from the Administration Console, after changing the password, in addition to changing the password in the boot.properties file, make sure that you change the password from the Remote Start tab in the Administration Console. For information about changing the password from the console, see "Changing the Password of a User" in Security in Administration Console Online Help.

Known Issues in WebLogic Server 8.1 SP5

Core WebLogic Server Known Issues

Change
Request
Number

Description

CR185820 CR185821

If a client has installed a reverse-proxy server with IP mapping, server IP addresses and domain names may be unavailable.

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.

CR236083

Clustered `HttpSession` replication may trigger a "Received a stale replication request" error when all of the following conditions exist:

1. The cluster is configured with `PersistentStoreType` set to replicated (and/or replicated if clustered).
2. The cluster is replicating HTTP sessions for a heavy client load, with several hundred concurrent users.
3. Some server threads handling client traffic are delayed while waiting for responses from a database.

CR272727

The `ulimit -n` command to limit the number of open file descriptors is not supported in `ksh` shell on HP-UX.

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 the `ksh` shell on HP-UX. So, in WebLogic Server 8.1SP5, the `commEnv.sh` script does not set the upper limit of open file descriptors for this HP-UX shell.

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

Workaround: You can manually limit the number of open file descriptors. However, this workaround is not available in the `ksh` shell environment

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp5` patch.

Change Request Number	Description
CR185820 CR185821	If a client has installed a reverse-proxy server with IP mapping, server IP addresses and domain names may be unavailable.
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.
CR236083	Clustered `HttpSession` replication may trigger a "Received a stale replication request" error when all of the following conditions exist: 1. The cluster is configured with `PersistentStoreType` set to replicated (and/or replicated if clustered). 2. The cluster is replicating HTTP sessions for a heavy client load, with several hundred concurrent users. 3. Some server threads handling client traffic are delayed while waiting for responses from a database.
CR272727	The `ulimit -n` command to limit the number of open file descriptors is not supported in `ksh` shell on HP-UX. 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 the `ksh` shell on HP-UX. So, in WebLogic Server 8.1SP5, the `commEnv.sh` script does not set the upper limit of open file descriptors for this HP-UX shell. Operating system: HP-UX 11.0, 11i on PA-RISC Workaround: You can manually limit the number of open file descriptors. However, this workaround is not available in the `ksh` shell environment
CR263825	You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the `CR263825_810sp5` patch.

JDBC Known Issues

Change Request Number

Description

CR251945

When a connection pool failed to satisfy a user request, the multipool tried to disable that pool. However, the disable action could only be done by a user belonging to the "Admin" group. `ResourcePermissionsException` occurred when the current user did not have the required permissions.

Change Request Number	Description
CR251945	When a connection pool failed to satisfy a user request, the multipool tried to disable that pool. However, the disable action could only be done by a user belonging to the "Admin" group. `ResourcePermissionsException` occurred when the current user did not have the required permissions.

JTA Known Issues

Change Request Number

Description

CR259037

When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.

Workaround or Solution:

Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Change Request Number	Description
CR259037	When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other. Workaround or Solution: Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

RMI Known Issues

Change Request Number

Description

CR286661

The WebLogic cluster `ClusterCommunicationService` started before applications were started locally on the server. So the cluster JNDI bindings failed to find certain application-specific classes on the server.

Workaround: Initialize `ClusterCommunicationService` after all applications are deployed locally on the server.

Change Request Number	Description
CR286661	The WebLogic cluster `ClusterCommunicationService` started before applications were started locally on the server. So the cluster JNDI bindings failed to find certain application-specific classes on the server. Workaround: Initialize `ClusterCommunicationService` after all applications are deployed locally on the server.

Security Known Issues

Change Request Number

Description

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 Administration Console Online Help.

Change Request Number	Description
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 Administration Console Online Help.

Servlets & JSPs Known Issues

Change Request Number	Description
CR262289	When calling the `close()` method on the `InputStream` obtained from the `HttpsURLConnection` class, the underlying SSL socket might not be closed even when the `disconnect()` method is called. This can result in a socket leak. Workaround or Solution: To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the `HttpsURLConnection#disconnect()` method instead of the `InputStream#close()` method.

Change Request Number

Description

CR262289

Workaround or Solution:

To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the HttpsURLConnection#disconnect() method instead of the InputStream#close() method.

Spring Framework on WebLogic Server Issues

Change Request Number

Description and Workaround

CR236708

There is an Antlr conflict between Hibernate 3 and WebLogic Server.

Workaround:

Place `Antlr2.7.5.jar` before `weblogic.jar` in your CLASSPATH.

CR237532

There is a WebApp classloading issue with the Spring Framework.

Workaround:

Contact BEA Customer Support for a WebLogic Server-Spring combination patch.

Change Request Number	Description and Workaround
CR236708	There is an Antlr conflict between Hibernate 3 and WebLogic Server. Workaround: Place `Antlr2.7.5.jar` before `weblogic.jar` in your CLASSPATH.
CR237532	There is a WebApp classloading issue with the Spring Framework. Workaround: Contact BEA Customer Support for a WebLogic Server-Spring combination patch.

Known Issues in WebLogic Server 8.1 SP4

Administration Console Known Issues

Change Request Number

Description

CR186747

When viewing the Administration Console in with the language preference set to Japanese or Korean, the links to customize the information displayed on the page ("Customize this view..." in English) do not work.

Workaround: Select "English" for Language on the Console—>Preferences tab in the Administration Console.

Change Request Number	Description
CR186747	When viewing the Administration Console in with the language preference set to Japanese or Korean, the links to customize the information displayed on the page ("Customize this view..." in English) do not work. Workaround: Select "English" for Language on the Console—>Preferences tab in the Administration Console.

Cluster Known Issues

Change
Request
Number

Description

CR172156

In WebLogic Server 8.1, use of more than about 20 channels in a cluster can result in the formation of multicast header transmissions that exceed the default maximum packet size. The MTUSize attribute in the Server element of config.xml sets the maximum size for packets sent using the associated network card to 1500. Sending packets that exceed the value of MTUSize can result in a java.lang.NegativeArraySizeException, similar to:

java.lang.NegativeArraySizeException at weblogic.common.internal.WLObjectOutputStreamBase2.writeBytes(WLObjectOutputStreamBase2.java:97) at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java:340) at weblogic.cluster.MulticastSender.send(MulticastSender.java:156) at weblogic.cluster.AttributeManager.sendAttributes(AttributeManager.java:52) at weblogic.cluster.ClusterCommunicationService.resume(ClusterCommunicationService.java:79) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1042) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)

When the problem was replicated in a cluster with 22 channels, it was solved by setting MTUSize to 2500.

Workaround: If you see NegativeArraySizeExceptions in a cluster with a large number of channels, increase incrementally the value of MTUSize until the exception does not occur.

Change Request Number	Description
CR172156	In WebLogic Server 8.1, use of more than about 20 channels in a cluster can result in the formation of multicast header transmissions that exceed the default maximum packet size. The MTUSize attribute in the Server element of config.xml sets the maximum size for packets sent using the associated network card to 1500. Sending packets that exceed the value of MTUSize can result in a java.lang.NegativeArraySizeException, similar to: java.lang.NegativeArraySizeException at weblogic.common.internal.WLObjectOutputStreamBase2.writeBytes(WLObjectOutputStreamBase2.java:97) at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java:340) at weblogic.cluster.MulticastSender.send(MulticastSender.java:156) at weblogic.cluster.AttributeManager.sendAttributes(AttributeManager.java:52) at weblogic.cluster.ClusterCommunicationService.resume(ClusterCommunicationService.java:79) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1042) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32) When the problem was replicated in a cluster with 22 channels, it was solved by setting MTUSize to 2500. Workaround: If you see NegativeArraySizeExceptions in a cluster with a large number of channels, increase incrementally the value of MTUSize until the exception does not occur.

Core WebLogic Server Known Issues

Change
Request
Number

Description

CR093104

In earlier service packs, the NT Performance pack caused thread deadlock under some circumstances. The problem was exhibited under light loads during stress tests of a JSP accessing a database. Thread dumps showed the majority of "default" execute threads stuck in "waiting for monitor entry":

`"ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x273fb548 nid=0xadc waiting for monitor entry [0x2810f000..0x2810fdc4]`

Workaround: If you experience such deadlocks, create a `.hotspot_compiler` file in the directory where you invoke the JVM and put the following lines in that file:

`exclude weblogic/socket/NTSocketMuxer processSockets`

exclude weblogic/socket/NTSocketMuxer trigger

exclude weblogic/socket/NTSocketMuxer cleanup

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp4` patch.

CR183137

Certain combinations of Java command-line options can cause the Sun JDK to crash with a HotSpot Virtual Machine Error when JSPs are precompiled in production mode (-server) with debug enabled. The symptom is an error like the following:

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

In particular, the following combination of options seems to cause this problem:

Domain configured with Sun JDK 1.4.2_04 (not BEA JRockit^®)

Server running in production mode (`-server` option)

Debug enabled

JSP Precompilation enabled (The `weblogic.xml` file for a Web application specifies `precompile=true`)

Sun JVM command-line options associated with this issue include:

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

Workarounds: There are several ways to avoid this issue (choose one):

Use the JRockit JVM instead of the Sun JVM.

Edit the server start script to start with `-client` (not `-server`) when debugging with the Sun JDK.

Disable debugging (edit `setDomainEnv` or manually remove debug JVM arguments).

Do not precompile when debugging.

CR239324 CR239819

If a socket is unregistered and then registered, and if between the two calls the timeout timer never runs, the data structures are getting out of sync which prevents the newly-registered socket from ever timing out.

This problem was resolved in 8.1 SP5.

Change Request Number	Description
CR093104	In earlier service packs, the NT Performance pack caused thread deadlock under some circumstances. The problem was exhibited under light loads during stress tests of a JSP accessing a database. Thread dumps showed the majority of "default" execute threads stuck in "waiting for monitor entry": `"ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x273fb548 nid=0xadc waiting for monitor entry [0x2810f000..0x2810fdc4]` Workaround: If you experience such deadlocks, create a `.hotspot_compiler` file in the directory where you invoke the JVM and put the following lines in that file: `exclude weblogic/socket/NTSocketMuxer processSockets` exclude weblogic/socket/NTSocketMuxer trigger exclude weblogic/socket/NTSocketMuxer cleanup
CR263825	You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the `CR263825_810sp4` patch.
CR183137	Certain combinations of Java command-line options can cause the Sun JDK to crash with a HotSpot Virtual Machine Error when JSPs are precompiled in production mode (-server) with debug enabled. The symptom is an error like the following: `# 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` In particular, the following combination of options seems to cause this problem: Domain configured with Sun JDK 1.4.2_04 (not BEA JRockit^®) Server running in production mode (`-server` option) Debug enabled JSP Precompilation enabled (The `weblogic.xml` file for a Web application specifies `precompile=true`) Sun JVM command-line options associated with this issue include: -server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -java.compiler=NONE -ea -da:com.bea... -da:javelin... -da:weblogic... Workarounds: There are several ways to avoid this issue (choose one): Use the JRockit JVM instead of the Sun JVM. Edit the server start script to start with `-client` (not `-server`) when debugging with the Sun JDK. Disable debugging (edit `setDomainEnv` or manually remove debug JVM arguments). Do not precompile when debugging.
CR239324 CR239819	If a socket is unregistered and then registered, and if between the two calls the timeout timer never runs, the data structures are getting out of sync which prevents the newly-registered socket from ever timing out. This problem was resolved in 8.1 SP5.

Deployment Known Issues

Change Request Number

Description

CR264560

When the element `home-is-clusterable` is set to `True` in weblogic-ejb-jar.xml file and the EJB is deployed in a cluster and if all the cluster members are not started at the same time, there is a possibility of AssertionError and failure to server startup.

Workaround:

Precompile the EJB application and verify that the final JAR file has WLStub.class files. If these files do not exist then compile again with -disableHotCodeGen flag.

If precompilation is not possible and the EJB is compiled on the server during runtime then add the -disableHotCodeGen flag to the server's extraEJBCOptions. You can add the flag using Server > General Tab > Advanced Options > Extra EJB Compiler Options.

CR210073

When all the modules of an application are pinned (deployed or targeted) to some of the servers in a cluster and no module is targeted to the cluster, a potential deadlock of the Admin RMI threads may cause application deployment to hang.

Workaround: Increase the RMI pool size by specifying -Dweblogic.management.rmiQueueSize=xx in java command in weblogic startup script. It is recommended that the value of xx be equal to one more than the number of managed servers in the domain. The default value for this pool size is 3.

Change Request Number	Description
CR264560	When the element `home-is-clusterable` is set to `True` in weblogic-ejb-jar.xml file and the EJB is deployed in a cluster and if all the cluster members are not started at the same time, there is a possibility of AssertionError and failure to server startup. Workaround: Precompile the EJB application and verify that the final JAR file has WLStub.class files. If these files do not exist then compile again with -disableHotCodeGen flag. If precompilation is not possible and the EJB is compiled on the server during runtime then add the -disableHotCodeGen flag to the server's extraEJBCOptions. You can add the flag using Server > General Tab > Advanced Options > Extra EJB Compiler Options.
CR210073	When all the modules of an application are pinned (deployed or targeted) to some of the servers in a cluster and no module is targeted to the cluster, a potential deadlock of the Admin RMI threads may cause application deployment to hang. Workaround: Increase the RMI pool size by specifying -Dweblogic.management.rmiQueueSize=xx in java command in weblogic startup script. It is recommended that the value of xx be equal to one more than the number of managed servers in the domain. The default value for this pool size is 3.

Documentation Known Issues

Change Request Number

Description

CR196210

Previous versions of this document and various other sample documents erroneously described using weblogic.management.Admin.getInstance().getAdminMBeanHome() as a way to look up the MBeanHome interface on the Administration Server.

However, the weblogic.management.Admin class is not public. 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.

n/a

Links in the Administration Console Online Help to the JRockit documentation are to the JRockit 8.1 SP3 documentation instead of the JRockit 1.4.2 documentation. A listing of all JRockit documentation can be found at http://e-docs.bea.com/more_jrockit.html.

Change Request Number	Description
CR196210	Previous versions of this document and various other sample documents erroneously described using weblogic.management.Admin.getInstance().getAdminMBeanHome() as a way to look up the MBeanHome interface on the Administration Server. However, the weblogic.management.Admin class is not public. 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.
n/a	Links in the Administration Console Online Help to the JRockit documentation are to the JRockit 8.1 SP3 documentation instead of the JRockit 1.4.2 documentation. A listing of all JRockit documentation can be found at http://e-docs.bea.com/more_jrockit.html.

Examples Known Issues

Change Request Number

Description

CR175804

The `iiop.ejb.entity.tuxclient` sample does not run successfully.

This problem is due to changes in JVM behavior regarding vector marshalling. A BEA Tuxedo^® 8.1 rolling patch is expected to be released in the near future to resolve this issue.

Change Request Number	Description
CR175804	The `iiop.ejb.entity.tuxclient` sample does not run successfully. This problem is due to changes in JVM behavior regarding vector marshalling. A BEA Tuxedo^® 8.1 rolling patch is expected to be released in the near future to resolve this issue.

Installation Known Issues

Change Request Number

Description

CR182698

When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux AS or ES 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.)

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.

Change Request Number	Description
CR182698	When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux AS or ES 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.) 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.

JDBC Known Issues

Change Request Number

Description

CR184298

When using a pooled JDBC connection on a WebLogic Server client, if the JDBC driver classes in the client `CLASSPATH` are not the exact same version as in the server `CLASSPATH`, you may see a `java.rmi.UnmarshalException`. This issue was noted when using a RowSet control in BEA WebLogic Workshop^®.

Workaround: Make sure JDBC driver classes in the client and server `CLASSPATHs` are the same.

CR190393

CountOfTestFailuresTillFlush is not closing all connections when the stipulated number of test failures has been reached, and CountOfRefreshFailuresTillDisable does not disable the pool after the stipulated number of failures.

There is no workaround for this issue in 8.1SP4.

This problem was resolved in 8.1 SP5.

Change Request Number	Description
CR184298	When using a pooled JDBC connection on a WebLogic Server client, if the JDBC driver classes in the client `CLASSPATH` are not the exact same version as in the server `CLASSPATH`, you may see a `java.rmi.UnmarshalException`. This issue was noted when using a RowSet control in BEA WebLogic Workshop^®. Workaround: Make sure JDBC driver classes in the client and server `CLASSPATHs` are the same.
CR190393	CountOfTestFailuresTillFlush is not closing all connections when the stipulated number of test failures has been reached, and CountOfRefreshFailuresTillDisable does not disable the pool after the stipulated number of failures. There is no workaround for this issue in 8.1SP4. This problem was resolved in 8.1 SP5.

JTA Known Issues

Change Request Number

Description

CR259037

When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.

Workaround or Solution:

Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Change Request Number	Description
CR259037	When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other. Workaround or Solution: Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Node Manager Known Issues

Change Request Number

Description

CR203668

When using Managed Servers with the Node Manager, if the Managed Server fails to restart within the time period specified by the Restart Interval attribute and number of attempts specified by the Max Restarts within Interval attribute, the Managed Server will have be restarted manually.

CR209806

When a machine has been configured in the Admin Console and the listen port for the Node Manager is left unspecified, the Admin Server checks the default port 5555 for the presence of a Node Manager. As a result, the Admin Server may encounter conflict with other processes running on port 5555 even when the Node Manager is not deployed.

Change Request Number	Description
CR203668	When using Managed Servers with the Node Manager, if the Managed Server fails to restart within the time period specified by the Restart Interval attribute and number of attempts specified by the Max Restarts within Interval attribute, the Managed Server will have be restarted manually.
CR209806	When a machine has been configured in the Admin Console and the listen port for the Node Manager is left unspecified, the Admin Server checks the default port 5555 for the presence of a Node Manager. As a result, the Admin Server may encounter conflict with other processes running on port 5555 even when the Node Manager is not deployed.

Security Known Issues

Change Request Number

Description

CR187784

The context path and uri arguments for the URLResource are stored in lowercase on Windows and mixed case on UNIX. As a result, if you define roles and policies in a domain on one operating system, export them, and then import them to a domain on the other operating system, the roles and policies may not work correctly. The end result is that webapp pages that you protect on one operating system may not be protected when the roles and policies are imported to a domain on the other operating system.

CR206178

Using WLS8.1-SP3 with JDK 1.4.2 and making an outbound ssl connection causes the following error:

"java.lang.IllegalStateException: Cipher not initialized ".

The problem is resolved when the customer copied all the jars from the /jre/lib/ext folder of JDK 1.4.1 into the /jre/lib/ext of JDK 1.4.2.

Change Request Number	Description
CR187784	The context path and uri arguments for the URLResource are stored in lowercase on Windows and mixed case on UNIX. As a result, if you define roles and policies in a domain on one operating system, export them, and then import them to a domain on the other operating system, the roles and policies may not work correctly. The end result is that webapp pages that you protect on one operating system may not be protected when the roles and policies are imported to a domain on the other operating system.
CR206178	Using WLS8.1-SP3 with JDK 1.4.2 and making an outbound ssl connection causes the following error: "java.lang.IllegalStateException: Cipher not initialized ". The problem is resolved when the customer copied all the jars from the /jre/lib/ext folder of JDK 1.4.1 into the /jre/lib/ext of JDK 1.4.2.

Servlets & JSPs Known Issues

Change Request Number	Description
CR262289	When calling the `close()` method on the `InputStream` obtained from the `HttpsURLConnection` class, the underlying SSL socket might not be closed even when the `disconnect()` method is called. This can result in a socket leak. Workaround or Solution: To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the `HttpsURLConnection#disconnect()` method instead of the `InputStream#close()` method.

Change Request Number

Description

CR262289

Workaround or Solution:

To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the HttpsURLConnection#disconnect() method instead of the InputStream#close() method.

Transactions Known Issues

Change Request Number

Description

CR201308

If your application is using XA transactions with the Oracle thin driver 10.1.0.3, you must grant execute permission on the dbms_system table to the database user used to connect to the database, along with other database preparations for XA:

1. Execute the following command: `@xaview.sql`

2. Grant the following permissions:

`grant select on v$xatrans$ to public (or <user>);`

`grant select on pending_trans$ to public;`

`grant select on dba_2pc_pending to public;`

`grant select on dba_pending_transactions to public;`

(when using the Oracle Thin driver 10.1.0.3 or later)
`grant execute on dbms_system to <user>;`

If the above steps are not performed on the database server, normal XA database queries and updates may work fine. However, when the Weblogic Server Transaction Manager performs recovery on a re-boot after a crash, recover for the Oracle resource will fail with XAER_RMERR. Crash recovery is a standard operation for an XA resource.

Note: Weblogic Server 8.1SP4 ships with the Oracle Thin driver 10.1.0.2, so granting permission on the dbms_system is required only if you use a different version of the driver.

See "Using the Oracle Thin/XA Driver" in Programming WebLogic JTA for more information about using the Oracle Thin/XA driver with WebLogic Server.

CR220662

Under certain failure conditions following a database server or database network crash, pending transaction branches on failed Oracle Real Application Clusters (RAC) instances may not be properly resolved. Use one of the following methods to correct this problem:

To prevent data loss, restart the coordinating managed server

If data loss is acceptable, forcibly roll back the transaction in the Oracle database

Change Request Number	Description
CR201308	If your application is using XA transactions with the Oracle thin driver 10.1.0.3, you must grant execute permission on the dbms_system table to the database user used to connect to the database, along with other database preparations for XA: 1. Execute the following command: `@xaview.sql` 2. Grant the following permissions: `grant select on v$xatrans$ to public (or <user>);` `grant select on pending_trans$ to public;` `grant select on dba_2pc_pending to public;` `grant select on dba_pending_transactions to public;` (when using the Oracle Thin driver 10.1.0.3 or later) `grant execute on dbms_system to <user>;` If the above steps are not performed on the database server, normal XA database queries and updates may work fine. However, when the Weblogic Server Transaction Manager performs recovery on a re-boot after a crash, recover for the Oracle resource will fail with XAER_RMERR. Crash recovery is a standard operation for an XA resource. Note: Weblogic Server 8.1SP4 ships with the Oracle Thin driver 10.1.0.2, so granting permission on the dbms_system is required only if you use a different version of the driver. See "Using the Oracle Thin/XA Driver" in Programming WebLogic JTA for more information about using the Oracle Thin/XA driver with WebLogic Server.
CR220662	Under certain failure conditions following a database server or database network crash, pending transaction branches on failed Oracle Real Application Clusters (RAC) instances may not be properly resolved. Use one of the following methods to correct this problem: To prevent data loss, restart the coordinating managed server If data loss is acceptable, forcibly roll back the transaction in the Oracle database

Web Services Known Issues

Change Request Number

Description

CR107595

SSL does not work for J2ME clients on WebLogic Server 8.1.

Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

Change Request Number	Description
CR107595	SSL does not work for J2ME clients on WebLogic Server 8.1. Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

WebLogic Tuxedo Connector (WTC) Known Issues

Change Request Number

Description

CR185475

WTC cannot have multiple connections within a single transaction.

If multiple TuxedoConnections are instantiated within a single transaction, only the first TuxedoConnection instance is enlisted in the transaction.

CR179956

WTC imported service Resource Name must match Remote Name.

WTC imported service Resource Name and Remote Service Name cannot differ. When the imported service Mbean is updated (to give a different resource name), the WTCService cache is not updated.

Workaround: Reboot the WebLogic Server instance.

CR127660

View classes are not set on a per connection basis.

A shared BEA WebLogic Tuxedo Connector^{^TM} 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.

Change Request Number	Description
CR185475	WTC cannot have multiple connections within a single transaction. If multiple TuxedoConnections are instantiated within a single transaction, only the first TuxedoConnection instance is enlisted in the transaction.
CR179956	WTC imported service Resource Name must match Remote Name. WTC imported service Resource Name and Remote Service Name cannot differ. When the imported service Mbean is updated (to give a different resource name), the WTCService cache is not updated. Workaround: Reboot the WebLogic Server instance.
CR127660	View classes are not set on a per connection basis. A shared BEA WebLogic Tuxedo Connector^{^TM} 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.

WebLogic Type 4 JDBC Drivers Known Issues

Change
Request
Number

Description

CR202674

The WebLogic Type 4 JDBC driver for DB2 is not included in the WebLogic Server 8.1 SP4 release. It was removed because DB2 support is not yet available for WebLogic Server 8.1 SP4. For customers that require DB2 support, BEA recommends that you use WebLogic Server 8.1 SP3 until DB2 support is available for WebLogic Server 8.1 SP4.

--

Oracle Driver

The WebLogic JDBC Oracle driver now describes columns defined as FLOAT or FLOAT(n) as a DOUBLE SQL type. The driver previously described these columns as a FLOAT SQL type. Both the DOUBLE type and the FLOAT type represent a double precision floating point number.

--

SQL Server Driver

The SendStringParameterAsUnicode connection option is set to true by default. Setting this option to true can negatively impact performance if an application does string comparison in SQL and the data stored in the database is not Unicode. On the other hand, setting this option to false can cause data corruption or unexpected comparison results if the data is not stored in the default database character set. Microsoft SQL Server allows you to define columns in a table that use a character set other than the default database character set. When sending parameter data to the server, the driver does not know what the character set is for the column that is being compared or modified. Sending parameter data as Unicode will always work, but is subject to the conversion and performance issues mentioned in the Microsoft document: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271566.

CR183190

Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using a DB2 database, you may see the following error:

`"java.sql.SQLException: [BEA][DB2 JDBC Driver]No more available statements.`

`Please recreate your package with a larger dynamicSections value."`

There is no workaround for this issue in 8.1SP4.

This problem was resolved in 8.1 SP5.

Change Request Number	Description
CR202674	The WebLogic Type 4 JDBC driver for DB2 is not included in the WebLogic Server 8.1 SP4 release. It was removed because DB2 support is not yet available for WebLogic Server 8.1 SP4. For customers that require DB2 support, BEA recommends that you use WebLogic Server 8.1 SP3 until DB2 support is available for WebLogic Server 8.1 SP4.
--	Oracle Driver The WebLogic JDBC Oracle driver now describes columns defined as FLOAT or FLOAT(n) as a DOUBLE SQL type. The driver previously described these columns as a FLOAT SQL type. Both the DOUBLE type and the FLOAT type represent a double precision floating point number.
--	SQL Server Driver The SendStringParameterAsUnicode connection option is set to true by default. Setting this option to true can negatively impact performance if an application does string comparison in SQL and the data stored in the database is not Unicode. On the other hand, setting this option to false can cause data corruption or unexpected comparison results if the data is not stored in the default database character set. Microsoft SQL Server allows you to define columns in a table that use a character set other than the default database character set. When sending parameter data to the server, the driver does not know what the character set is for the column that is being compared or modified. Sending parameter data as Unicode will always work, but is subject to the conversion and performance issues mentioned in the Microsoft document: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271566.
CR183190	Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using a DB2 database, you may see the following error: `"java.sql.SQLException: [BEA][DB2 JDBC Driver]No more available statements.` `Please recreate your package with a larger dynamicSections value."` There is no workaround for this issue in 8.1SP4. This problem was resolved in 8.1 SP5.

Known Issues in WebLogic Server 8.1 SP3

The following sections describe known issues in WebLogic Server 8.1 SP3:

Administration Console Known Issues

Change Request Number

Description

CR186747

When viewing the Administration Console in with the language preference set to Japanese or Korean, the links to customize the information displayed on the page ("Customize this view..." in English) do not work.

Workaround: Select "English" for Language on the Console—>Preferences tab in the Administration Console.

Change Request Number	Description
CR186747	When viewing the Administration Console in with the language preference set to Japanese or Korean, the links to customize the information displayed on the page ("Customize this view..." in English) do not work. Workaround: Select "English" for Language on the Console—>Preferences tab in the Administration Console.

Cluster Known Issues

Change
Request
Number

Description

CR172156

In WebLogic Server 8.1, use of more than about 20 channels in a cluster can result in the formation of multicast header transmissions that exceed the default maximum packet size. The MTUSize attribute in the Server element of config.xml sets the maximum size for packets sent using the associated network card to 1500. Sending packets that exceed the value of MTUSize can result in a java.lang.NegativeArraySizeException, similar to:

java.lang.NegativeArraySizeException at weblogic.common.internal.WLObjectOutputStreamBase2.writeBytes(WLObjectOutputStreamBase2.java:97) at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java:340) at weblogic.cluster.MulticastSender.send(MulticastSender.java:156) at weblogic.cluster.AttributeManager.sendAttributes(AttributeManager.java:52) at weblogic.cluster.ClusterCommunicationService.resume(ClusterCommunicationService.java:79) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1042) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)

When the problem was replicated in a cluster with 22 channels, it was solved by setting MTUSize to 2500.

Workaround: If you see NegativeArraySizeExceptions in a cluster with a large number of channels, increase incrementally the value of MTUSize until the exception does not occur.

Change Request Number	Description
CR172156	In WebLogic Server 8.1, use of more than about 20 channels in a cluster can result in the formation of multicast header transmissions that exceed the default maximum packet size. The MTUSize attribute in the Server element of config.xml sets the maximum size for packets sent using the associated network card to 1500. Sending packets that exceed the value of MTUSize can result in a java.lang.NegativeArraySizeException, similar to: java.lang.NegativeArraySizeException at weblogic.common.internal.WLObjectOutputStreamBase2.writeBytes(WLObjectOutputStreamBase2.java:97) at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java:340) at weblogic.cluster.MulticastSender.send(MulticastSender.java:156) at weblogic.cluster.AttributeManager.sendAttributes(AttributeManager.java:52) at weblogic.cluster.ClusterCommunicationService.resume(ClusterCommunicationService.java:79) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1042) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32) When the problem was replicated in a cluster with 22 channels, it was solved by setting MTUSize to 2500. Workaround: If you see NegativeArraySizeExceptions in a cluster with a large number of channels, increase incrementally the value of MTUSize until the exception does not occur.

Core WebLogic Server Known Issues

Change
Request
Number

Description

CR093104

In earlier service packs, the NT Performance pack caused thread deadlock under some circumstances. The problem was exhibited under light loads during stress tests of a JSP accessing a database. Thread dumps showed the majority of "default" execute threads stuck in "waiting for monitor entry":

`"ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x273fb548 nid=0xadc waiting for monitor entry [0x2810f000..0x2810fdc4]`

Workaround: If you experience such deadlocks, create a `.hotspot_compiler` file in the directory where you invoke the JVM and put the following line in that file:

`exclude weblogic/socket/NTSocketMuxer processSockets`

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp3` patch.

CR183137

Certain combinations of Java command-line options can cause the Sun JDK to crash with a HotSpot Virtual Machine Error when JSPs are precompiled in production mode (-server) with debug enabled. The symptom is an error like the following:

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

In particular, the following combination of options seems to cause this problem:

Domain configured with Sun JDK 1.4.2_04 (not JRockit)

Server running in production mode (`-server` option)

Debug enabled

JSP Precompilation enabled (The `weblogic.xml` file for a Web application specifies `precompile=true`)

Sun JVM command-line options associated with this issue include:

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

Workarounds: There are several ways to avoid this issue (choose one):

Use the JRockit JVM instead of the Sun JVM.

Edit the server start script to start with `-client` (not `-server`) when debugging with the Sun JDK.

Disable debugging (edit `setDomainEnv` or manually remove debug JVM arguments).

Do not precompile when debugging.

CR240499

In HP-UX, the thread runs with the default thread-priority assigned by the operating system even when a different thread priority is set from the Administration Console.

Workaround:

1. As a root user, run the following command
`setprivgrp <`user-group> `RTSCHED`
where, user-group is the unix-group.
2. Add the following java command line option to start WebLogic script
`-XX:SchedulerPriorityRange=SCHED_RTPRIO`

Change Request Number	Description
CR093104	In earlier service packs, the NT Performance pack caused thread deadlock under some circumstances. The problem was exhibited under light loads during stress tests of a JSP accessing a database. Thread dumps showed the majority of "default" execute threads stuck in "waiting for monitor entry": `"ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x273fb548 nid=0xadc waiting for monitor entry [0x2810f000..0x2810fdc4]` Workaround: If you experience such deadlocks, create a `.hotspot_compiler` file in the directory where you invoke the JVM and put the following line in that file: `exclude weblogic/socket/NTSocketMuxer processSockets`
CR263825	You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the `CR263825_810sp3` patch.
CR183137	Certain combinations of Java command-line options can cause the Sun JDK to crash with a HotSpot Virtual Machine Error when JSPs are precompiled in production mode (-server) with debug enabled. The symptom is an error like the following: `# 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` In particular, the following combination of options seems to cause this problem: Domain configured with Sun JDK 1.4.2_04 (not JRockit) Server running in production mode (`-server` option) Debug enabled JSP Precompilation enabled (The `weblogic.xml` file for a Web application specifies `precompile=true`) Sun JVM command-line options associated with this issue include: -server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -java.compiler=NONE -ea -da:com.bea... -da:javelin... -da:weblogic... Workarounds: There are several ways to avoid this issue (choose one): Use the JRockit JVM instead of the Sun JVM. Edit the server start script to start with `-client` (not `-server`) when debugging with the Sun JDK. Disable debugging (edit `setDomainEnv` or manually remove debug JVM arguments). Do not precompile when debugging.
CR240499	In HP-UX, the thread runs with the default thread-priority assigned by the operating system even when a different thread priority is set from the Administration Console. Workaround: 1. As a root user, run the following command `setprivgrp <`user-group> `RTSCHED` where, user-group is the unix-group. 2. Add the following java command line option to start WebLogic script `-XX:SchedulerPriorityRange=SCHED_RTPRIO`

Documentation Known Issues

Change Request Number

Description

n/a

Links in the Administration Console Online Help to the JRockit documentation are to the JRockit 8.1 SP3 documentation instead of the JRockit 1.4.2 documentation. A listing of all JRockit documentation can be found at http://e-docs.bea.com/more_jrockit.html.

Change Request Number	Description
n/a	Links in the Administration Console Online Help to the JRockit documentation are to the JRockit 8.1 SP3 documentation instead of the JRockit 1.4.2 documentation. A listing of all JRockit documentation can be found at http://e-docs.bea.com/more_jrockit.html.

Examples Known Issues

Change Request Number

Description

CR175804

The `iiop.ejb.entity.tuxclient` sample does not run successfully.

This problem is due to changes in JVM behavior regarding vector marshalling. A Tuxedo 8.1 rolling patch is expected to be released in the near future to resolve this issue.

Change Request Number	Description
CR175804	The `iiop.ejb.entity.tuxclient` sample does not run successfully. This problem is due to changes in JVM behavior regarding vector marshalling. A Tuxedo 8.1 rolling patch is expected to be released in the near future to resolve this issue.

Installation Known Issues

Change Request Number

Description

CR182698

When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux AS or ES 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.)

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.

Change Request Number	Description
CR182698	When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux AS or ES 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.) 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.

JDBC Known Issues

Change Request Number

Description

CR179600

Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using an Oracle database, this can result in out-of-cursor failures.

A patch is available for this issue. To get the patch, contact BEA Customer Support and reference CR179600.

This problem was resolved in 8.1 SP4.

CR183190

Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using a DB2 database, you may see the following error:

`"java.sql.SQLException: [BEA][DB2 JDBC Driver]No more available statements.`

`Please recreate your package with a larger dynamicSections value."`

There is no workaround for this issue in 8.1SP3.

This problem was resolved in 8.1 SP5.

CR184298

When using a pooled JDBC connection on a WebLogic Server client, if the JDBC driver classes in the client `CLASSPATH` are not the exact same version as in the server `CLASSPATH`, you may see a `java.rmi.UnmarshalException`. This issue was noted when using a RowSet control in WebLogic Workshop.

Workaround: Make sure JDBC driver classes in the client and server `CLASSPATHs` are the same.

CR190393

CountOfTestFailuresTillFlush is not closing all connections when the stipulated number of test failures has been reached, and CountOfRefreshFailuresTillDisable does not disable the pool after the stipulated number of failures.

There is no workaround for this issue in 8.1SP3.

This problem was resolved in 8.1 SP5.

Change Request Number	Description
CR179600	Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using an Oracle database, this can result in out-of-cursor failures. A patch is available for this issue. To get the patch, contact BEA Customer Support and reference CR179600. This problem was resolved in 8.1 SP4.
CR183190	Under certain statement failure conditions, cached statements are leaked without being closed, which can lead to DBMS resource problems. When using a DB2 database, you may see the following error: `"java.sql.SQLException: [BEA][DB2 JDBC Driver]No more available statements.` `Please recreate your package with a larger dynamicSections value."` There is no workaround for this issue in 8.1SP3. This problem was resolved in 8.1 SP5.
CR184298	When using a pooled JDBC connection on a WebLogic Server client, if the JDBC driver classes in the client `CLASSPATH` are not the exact same version as in the server `CLASSPATH`, you may see a `java.rmi.UnmarshalException`. This issue was noted when using a RowSet control in WebLogic Workshop. Workaround: Make sure JDBC driver classes in the client and server `CLASSPATHs` are the same.
CR190393	CountOfTestFailuresTillFlush is not closing all connections when the stipulated number of test failures has been reached, and CountOfRefreshFailuresTillDisable does not disable the pool after the stipulated number of failures. There is no workaround for this issue in 8.1SP3. This problem was resolved in 8.1 SP5.

JTA Known Issues

Change Request Number

Description

CR259037

When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.

Workaround or Solution:

Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

Change Request Number	Description
CR259037	When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other. Workaround or Solution: Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

RMI/IIOP Known Issues

Change Request Number

Description

CR124596
CR192252

The enhancement described in CR124596 was not fully implemented in WebLogic Server 8.1SP3. The optional enhancement to the BEA ORB forces reconnection when bootstrapping and allows hardware load-balancers to correctly balance connection attempts.

A patch for WebLogic Server 8.1SP3 is now available. To get the patch, contact BEA Customer Support and reference the patch for CR192252.

This problem was resolved in 8.1 SP4 for CR192252.

Change Request Number	Description
CR124596 CR192252	The enhancement described in CR124596 was not fully implemented in WebLogic Server 8.1SP3. The optional enhancement to the BEA ORB forces reconnection when bootstrapping and allows hardware load-balancers to correctly balance connection attempts. A patch for WebLogic Server 8.1SP3 is now available. To get the patch, contact BEA Customer Support and reference the patch for CR192252. This problem was resolved in 8.1 SP4 for CR192252.

Security Known Issues

Change Request Number

Description

CR184421

When importing security data into a new security realm, the user `weblogic` loses membership in all groups except `Administrators`. After importing the data, you must manually add `weblogic` to any required groups.

CR187784

The context path and uri arguments for the URLResource are stored in lowercase on Windows and mixed case on UNIX. As a result, if you define roles and policies in a domain on one operating system, export them, and then import them to a domain on the other operating system, the roles and policies may not work correctly. The end result is that webapp pages that you protect on one operating system may not be protected when the roles and policies are imported to a domain on the other operating system.

Change Request Number	Description
CR184421	When importing security data into a new security realm, the user `weblogic` loses membership in all groups except `Administrators`. After importing the data, you must manually add `weblogic` to any required groups.
CR187784	The context path and uri arguments for the URLResource are stored in lowercase on Windows and mixed case on UNIX. As a result, if you define roles and policies in a domain on one operating system, export them, and then import them to a domain on the other operating system, the roles and policies may not work correctly. The end result is that webapp pages that you protect on one operating system may not be protected when the roles and policies are imported to a domain on the other operating system.

Servlets & JSPs Known Issues

Change Request Number	Description
CR262289	When calling the `close()` method on the `InputStream` obtained from the `HttpsURLConnection` class, the underlying SSL socket might not be closed even when the `disconnect()` method is called. This can result in a socket leak. Workaround or Solution: To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the `HttpsURLConnection#disconnect()` method instead of the `InputStream#close()` method.

Change Request Number

Description

CR262289

Workaround or Solution:

To avoid such a socket leak and ensure all underlying resources are closed, you are advised to use the HttpsURLConnection#disconnect() method instead of the InputStream#close() method.

Transactions Known Issues

Change Request Number

Description

CR193458

When using DataDirect Connect for BEA WebLogic JDBC Drivers^{^TM} version 3.4 with a DB2 database, you may see XAER_RMERR errors for applications that previously ran without errors using the 3.3 version of the drivers. The problem is caused by implicit closing of result sets, a feature added to the drivers to improve performance.

Workaround: DataDirect added a connection property to control implicit result set closing: `AllowImplicitResultSetCloseForXA`. The feature is enabled by default. To disable implicit result set closings, set `AllowImplicitResultSetCloseForXA=false`. To make this setting for a JDBC connection pool, add it to the Properties for the connection pool on the JDBC Connection Pool —> Configuration —> General tab in the Administration Console. The resulting change in the `config.xml` file resembles the following `config.xml` excerpt:

`<JDBCConnectionPool DriverName="com.ddtek.jdbcx.db2.DB2DataSource" Name="myPool" Properties="user=scott; portNumber=50000; databaseName=SAMPLE; serverName=dbserver1.yourco.COM; batchPerformanceWorkaround=true;`AllowImplicitResultSetCloseForXA=false`" ...`

`URL="jdbc:datadirect:db2://dbserver1:50000;DatabaseName=SAMPLE" />`

Note: This issue applies to the DataDirect Connect for JDBC version 3.4 drivers for DB2 only. The problem has not been observed with drivers for other database management systems or previous releases of the DB2 drivers. `AllowImplicitResultSetCloseForXA` is ignored for these other drivers.

Change Request Number	Description
CR193458	When using DataDirect Connect for BEA WebLogic JDBC Drivers^{^TM} version 3.4 with a DB2 database, you may see XAER_RMERR errors for applications that previously ran without errors using the 3.3 version of the drivers. The problem is caused by implicit closing of result sets, a feature added to the drivers to improve performance. Workaround: DataDirect added a connection property to control implicit result set closing: `AllowImplicitResultSetCloseForXA`. The feature is enabled by default. To disable implicit result set closings, set `AllowImplicitResultSetCloseForXA=false`. To make this setting for a JDBC connection pool, add it to the Properties for the connection pool on the JDBC Connection Pool —> Configuration —> General tab in the Administration Console. The resulting change in the `config.xml` file resembles the following `config.xml` excerpt: `<JDBCConnectionPool DriverName="com.ddtek.jdbcx.db2.DB2DataSource" Name="myPool" Properties="user=scott; portNumber=50000; databaseName=SAMPLE; serverName=dbserver1.yourco.COM; batchPerformanceWorkaround=true;`AllowImplicitResultSetCloseForXA=false`" ...` `URL="jdbc:datadirect:db2://dbserver1:50000;DatabaseName=SAMPLE" />` Note: This issue applies to the DataDirect Connect for JDBC version 3.4 drivers for DB2 only. The problem has not been observed with drivers for other database management systems or previous releases of the DB2 drivers. `AllowImplicitResultSetCloseForXA` is ignored for these other drivers.

Web Services Known Issues

Change Request Number

Description

CR107595

SSL does not work for J2ME clients on WebLogic Server 8.1.

Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

Change Request Number	Description
CR107595	SSL does not work for J2ME clients on WebLogic Server 8.1. Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

WebLogic Tuxedo Connector (WTC) Known Issues

Change Request Number	Description
CR185475	WTC cannot have multiple connections within a single transaction. If multiple TuxedoConnections are instantiated within a single transaction, only the first TuxedoConnection instance is enlisted in the transaction.
CR179956	WTC imported service Resource Name must match Remote Name. WTC imported service Resource Name and Remote Service Name cannot differ. When the imported service Mbean is updated (to give a different resource name), the WTCService cache is not updated. Workaround: Reboot the WebLogic Server instance.
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.

Change Request Number

Description

CR185475

WTC cannot have multiple connections within a single transaction.

If multiple TuxedoConnections are instantiated within a single transaction, only the first TuxedoConnection instance is enlisted in the transaction.

CR179956

WTC imported service Resource Name must match Remote Name.

WTC imported service Resource Name and Remote Service Name cannot differ. When the imported service Mbean is updated (to give a different resource name), the WTCService cache is not updated.

Workaround: Reboot the WebLogic Server instance.

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.

Known Issues in WebLogic Server 8.1 SP2

The following sections describe known issues in WebLogic Server 8.1 SP2:

Patch Available for Sun Java 2 1.4.2 SDK, Oracle 10g Driver, and SQL Server, Sybase or DB2 Database Users

If you are using WebLogic Server or BEA WebLogic Platform^{^TM} 8.1 SP2 with the Sun Java 2 1.4.2 SDK, or the Oracle 10g driver, or a SQL Server, Sybase or DB2 database, you may need to install the WebLogic Platform 8.1 SP2 SDK1.4.2/Oracle10gdriver/Database patch. This patch, and a description of the specific configurations that require it, are available at the following dev2dev Web site:

http://dev2dev.bea.com/products/wlplatform81/patch/wlplat81sp2_patch.jsp

Administration Console Known Issues

Change Request Number

Description

CR125552

When using the WebLogic Server 8.1 Administration Console on machines that have JDK version 1.4.1_02 installed, the navigation applet fails to load and the system freezes.

Workaround: Uninstall JDK version 1.4.1_02 from the system and reinstall version JDK version 1.4.2_01 or later.

CR129594

The WebLogic Server Administration Console's JDBC Connection Pool Configuration tab does not have an option to rollback local transactions upon closing a connection.

Workaround: Set this option by editing the `config.xml` JDBCConnectionPool attribute RollbackLocalTxUponConnClose, or via the Configuration Wizard.

CR132229

The separators for multiple addresses in BEA Jolt^{^TM} and WLEC ConnectionPools are incorrectly identified as semicolons.

Workaround: Use commas to separate multiple addresses when configuring Jolt and WLEC Primary and Secondary Address fields.

Change Request Number	Description
CR125552	When using the WebLogic Server 8.1 Administration Console on machines that have JDK version 1.4.1_02 installed, the navigation applet fails to load and the system freezes. Workaround: Uninstall JDK version 1.4.1_02 from the system and reinstall version JDK version 1.4.2_01 or later.
CR129594	The WebLogic Server Administration Console's JDBC Connection Pool Configuration tab does not have an option to rollback local transactions upon closing a connection. Workaround: Set this option by editing the `config.xml` JDBCConnectionPool attribute RollbackLocalTxUponConnClose, or via the Configuration Wizard.
CR132229	The separators for multiple addresses in BEA Jolt^{^TM} and WLEC ConnectionPools are incorrectly identified as semicolons. Workaround: Use commas to separate multiple addresses when configuring Jolt and WLEC Primary and Secondary Address fields.

Configuration Wizard Known Issues

Change Request Number

Description

CR125514

When running the `config_builder.sh` script from the `BEA_HOME/wls81/common/bin` directory on a Solaris platform, the Configuration Template Builder does not start. The message "Unable to instantiate GUI, defaulting to console mode" is displayed, but rather than starting up in Console mode, a command prompt is displayed. The Configuration Template Builder is not supported in console mode—a graphics environment is required.

Workaround: Run the Configuration Wizard using xWindows.

Note: The error message will be changed in the next service pack to more accurately communicate this limitation.

Change Request Number	Description
CR125514	When running the `config_builder.sh` script from the `BEA_HOME/wls81/common/bin` directory on a Solaris platform, the Configuration Template Builder does not start. The message "Unable to instantiate GUI, defaulting to console mode" is displayed, but rather than starting up in Console mode, a command prompt is displayed. The Configuration Template Builder is not supported in console mode—a graphics environment is required. Workaround: Run the Configuration Wizard using xWindows. Note: The error message will be changed in the next service pack to more accurately communicate this limitation.

Connector Known Issues

Change Request Number

Description

n/a

When a connection request is made, WebLogic Server returns to the client (via the resource adapter) a Proxy object that wraps the connection object. WebLogic Server uses this proxy to provide features that assist applications using the WebLogic Server implementation of the J2EE Connector Architecture. These features include (1) connection leak detection capabilities and (2) late XAResource enlistment when a connection request is made before starting a global transaction that uses that connection.

If the connection object returned from a connection request is cast as a `Connection` class, a `ClassCastException` can occur. This exception is caused by either (1) the resource adapter doing the cast or (2) the client doing the cast during a connection request.

In WebLogic Server 8.1 SP2, an attempt is made to detect the `ClassCastException` caused by the resource adapter case (1) above. If the server detects that this cast is failing, it turns off the proxy wrapper feature and proceeds by returning the connection object during a connection request (unwrapped). The server logs a warning message to indicate that the proxy wrapper has been turned off. When this type of cast failure occurs, connection leak detection and late XAResource enlistment features are also turned off (but currently no indication of this is given in the Console monitoring).

WebLogic Server attempts to detect the `ClassCastException` by acting as a client using container-managed security. Doing so requires the resource adapter to be deployed with security credentials defined.

If the client is doing the cast and getting a `ClassCastException`, the customer (client) code can be modified as follows:

Workaround: If the client casts the connection object to `MyConnection`, instead of `MyConnection` being a class that implements the resource adapter's `Connection` interface, modify it to be an interface that extends `Connection`. Implement a `MyConnectionImpl` class that implements the `MyConnection` interface.

CR100048

If two adapters are configured to use the same Enterprise Information System (EIS) with the same Resource Manager, then using the two adapters in the same transaction can result in deadlocks or long delays followed by a transaction failure. This is because most Resource Managers, including Oracle's, do not allow adapters to share an EIS.

CR127127

The IIOP thin-client is not supported on AIX (or other platforms with the IBM VM) due to dependencies on the Sun VM.

Note: Only clients are affected by this issue. A thin-client running on another platform will work just fine against WebLogic Server running on AIX.

Change Request Number	Description
n/a	When a connection request is made, WebLogic Server returns to the client (via the resource adapter) a Proxy object that wraps the connection object. WebLogic Server uses this proxy to provide features that assist applications using the WebLogic Server implementation of the J2EE Connector Architecture. These features include (1) connection leak detection capabilities and (2) late XAResource enlistment when a connection request is made before starting a global transaction that uses that connection. If the connection object returned from a connection request is cast as a `Connection` class, a `ClassCastException` can occur. This exception is caused by either (1) the resource adapter doing the cast or (2) the client doing the cast during a connection request. In WebLogic Server 8.1 SP2, an attempt is made to detect the `ClassCastException` caused by the resource adapter case (1) above. If the server detects that this cast is failing, it turns off the proxy wrapper feature and proceeds by returning the connection object during a connection request (unwrapped). The server logs a warning message to indicate that the proxy wrapper has been turned off. When this type of cast failure occurs, connection leak detection and late XAResource enlistment features are also turned off (but currently no indication of this is given in the Console monitoring). WebLogic Server attempts to detect the `ClassCastException` by acting as a client using container-managed security. Doing so requires the resource adapter to be deployed with security credentials defined. If the client is doing the cast and getting a `ClassCastException`, the customer (client) code can be modified as follows: Workaround: If the client casts the connection object to `MyConnection`, instead of `MyConnection` being a class that implements the resource adapter's `Connection` interface, modify it to be an interface that extends `Connection`. Implement a `MyConnectionImpl` class that implements the `MyConnection` interface.
CR100048	If two adapters are configured to use the same Enterprise Information System (EIS) with the same Resource Manager, then using the two adapters in the same transaction can result in deadlocks or long delays followed by a transaction failure. This is because most Resource Managers, including Oracle's, do not allow adapters to share an EIS.
CR127127	The IIOP thin-client is not supported on AIX (or other platforms with the IBM VM) due to dependencies on the Sun VM. Note: Only clients are affected by this issue. A thin-client running on another platform will work just fine against WebLogic Server running on AIX.

Core Known Issues

Change Request Number

Description

CR106616

After several operations on the WebLogic Server Administration Console, Netscape Version 4.79 running on Linux AS2.1 and HP-UX shuts down with a bus error, sometimes with a core dump.

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp2` patch.

Change Request Number	Description
CR106616	After several operations on the WebLogic Server Administration Console, Netscape Version 4.79 running on Linux AS2.1 and HP-UX shuts down with a bus error, sometimes with a core dump.
CR263825	You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the `CR263825_810sp2` patch.

EJB Known Issues

Change Request Number

Description

CR112393

An EJB JAR is referencing another utility JAR through the Manifest classpath. When you compile an EJB using the `weblogic.appc` utility, classes included in the referenced JAR are not found. The `appc` compiler explodes the source JAR in a temporary directory and the classfinder looks for the dependent JAR in that temporary directory; however, the classes are not copied into the temporary directory.

Workaround:

This issue only exists for stand-alone modules that are not part of an EAR file. BEA recommends that you package the EJB JAR file and utility JAR file together in an EAR file. This will ensure they are always tied together. If you choose not to do this, BEA recommends you use the `weblogic.ejbc` utility rather than `weblogic.appc`.

Note: The `weblogic.ejbc` utility is a deprecated utility and will not be available in future releases.

CR126613

An MDB running in a transactional context interacts with an external system (such as an LDAP server) and message processing takes longer than transaction timeout value. The MDB throws the following exception and message processing stops:

`weblogic.utils.AssertionError: *** ASSERTION FAILED *[ Left-over JTA transaction found on MDB listener thread ] at weblogic.utils.Debug.assertion(Debug.java:57) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:245) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)`

Workaround:** Increase the value of the transaction timeout to make it high enough.

Change Request Number	Description
CR112393	An EJB JAR is referencing another utility JAR through the Manifest classpath. When you compile an EJB using the `weblogic.appc` utility, classes included in the referenced JAR are not found. The `appc` compiler explodes the source JAR in a temporary directory and the classfinder looks for the dependent JAR in that temporary directory; however, the classes are not copied into the temporary directory. Workaround: This issue only exists for stand-alone modules that are not part of an EAR file. BEA recommends that you package the EJB JAR file and utility JAR file together in an EAR file. This will ensure they are always tied together. If you choose not to do this, BEA recommends you use the `weblogic.ejbc` utility rather than `weblogic.appc`. Note: The `weblogic.ejbc` utility is a deprecated utility and will not be available in future releases.
CR126613	An MDB running in a transactional context interacts with an external system (such as an LDAP server) and message processing takes longer than transaction timeout value. The MDB throws the following exception and message processing stops: `weblogic.utils.AssertionError: *** ASSERTION FAILED *[ Left-over JTA transaction found on MDB listener thread ] at weblogic.utils.Debug.assertion(Debug.java:57) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:245) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)` Workaround:** Increase the value of the transaction timeout to make it high enough.

Examples Known Issues

Change Request Number

Description

CR104550

The `config.xml` file for the samples banking application domain contains an incorrect name for the EJB. With this error, the application cannot find the EJB.

`<Application Deployed="true" Name="app_banking" Path=".\config\migrationdomain\applications" StagedTargets="migrationserver"> <EJBComponent Name="app_banking" Targets="migrationserver" URI="app_banking.jar"/> </Application>`

It should contain:

`<Application Deployed="true" Name="containerManaged" Path=".\config\migrationdomain\applications" StagedTargets="migrationserver"> <EJBComponent Name="containerManaged" Targets="migrationserver" URI="app_banking.jar"/> </Application>`

Workaround: Undeploy the EJB, and redeploy it with the correct name, containerManaged.

Change Request Number	Description
CR104550	The `config.xml` file for the samples banking application domain contains an incorrect name for the EJB. With this error, the application cannot find the EJB. `<Application Deployed="true" Name="app_banking" Path=".\config\migrationdomain\applications" StagedTargets="migrationserver"> <EJBComponent Name="app_banking" Targets="migrationserver" URI="app_banking.jar"/> </Application>` It should contain: `<Application Deployed="true" Name="containerManaged" Path=".\config\migrationdomain\applications" StagedTargets="migrationserver"> <EJBComponent Name="containerManaged" Targets="migrationserver" URI="app_banking.jar"/> </Application>` Workaround: Undeploy the EJB, and redeploy it with the correct name, containerManaged.

General Known Issues

Change Request Number

Description

CR128912

There is a known issue in HP-UX SDK 1.4.1.05 character set API and as a result, `Charset.availableCharsets()` always fails. This problem manifests itself in WebLogic Server SP2 using JVM 1.4.1.05.

Workaround: Download and use HP's 1.4.1.06 JVM, available as part of the JDK 1.4.1.06 at http://www.hp.com/products1/unix/java/.

Change Request Number	Description
CR128912	There is a known issue in HP-UX SDK 1.4.1.05 character set API and as a result, `Charset.availableCharsets()` always fails. This problem manifests itself in WebLogic Server SP2 using JVM 1.4.1.05. Workaround: Download and use HP's 1.4.1.06 JVM, available as part of the JDK 1.4.1.06 at http://www.hp.com/products1/unix/java/.

Installation Known Issues

Change Request Number

Description

CR127350

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.

Workaround: Before installing SP2, make backup copies of any files or applications that you have created in WL_HOME.

JMS Known Issues

Change Request Number

Description

CR125979

Customers who set up a JMS bridge within a cluster may find that when starting the bridge, the following exception is thrown from the Managed Servers, and that the JMS message cannot be sent to the intended destination.

<Oct 16, 2003 3:12:49 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> <Oct 16, 2003 3:23:17 PM PDT> <Error> <JMS> <BEA-040368> <The following exception has occurred: java.lang.NullPointerException at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:519) at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:956) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.Kernel.execute(Kernel.java:336) at weblogic.kernel.Kernel.execute(Kernel.java:321) at ...

Workaround:

Deploy the adapter to individual servers instead of to the entire cluster. The adapter must be deployed on the same server to which the bridge is targeted. For instructions, see http://e-docs.bea.com/wls/docs81/ConsoleHelp/messaging_bridge.html#1109910.

This problem was resolved in 8.1 SP3.

CR128596

In some cases, messages remain in the source queue of the JMS bridge in the sending-side cluster after restarting a Managed Server on the receiving side cluster.

Workaround: Apply the patch for CR128596 to all WebLogic Server instances.

This problem was resolved in 8.1 SP3.

JTA Known Issues

Change Request Number

Description

CR259037

When a transaction times out at logging time, you could experience a deadlock situation. The thread that is trying to write the transaction to the transaction log (TLOG) times out, a different thread trying to execute the rollback to clean the same transaction from the TLOG and deadlock each other.

Workaround or Solution:

Decrease the value of the `CheckpointIntervalSeconds` attribute and move TLOGs to a directory where they will not run out of memory.

JVM Known Issues

Change Request Number

Description

CR131717

Due to a bug in the Sun JDK version 1.4.2_02, a server ExecuteThread freezes or a client JVM hangs when using JDK version 1.4.2_02 with Japanese encodings ISO-2022-JP and ISO2022JP. Customers not using Japanese encodings will not be affected by this bug.

Workaround: This bug will be fixed in JDK version 1.4.2_04 (available February 12, 2004), as documented at http://developer.java.sun.com/developer/bugParade/bugs/4879522.html. In the meantime, Japanese customers can use JDK version 1.4.1.

CR132292

WebLogic Server 8.1 Known Issues

Known Issues in WebLogic Server 8.1 SP6

Core Known Issues Change Request Number Description CR263825 You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases. Workaround: Contact your BEA support representative for the CR263825_810sp6 patch.

Servlets & JSPs Known Issues

Console Help Know Issues

Known Issues in WebLogic Server 8.1 SP5

Servlets & JSPs Known Issues

Known Issues in WebLogic Server 8.1 SP4

Servlets & JSPs Known Issues

Web Services Known Issues Change Request Number Description CR107595 SSL does not work for J2ME clients on WebLogic Server 8.1. Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

Known Issues in WebLogic Server 8.1 SP3

Servlets & JSPs Known Issues

Web Services Known Issues Change Request Number Description CR107595 SSL does not work for J2ME clients on WebLogic Server 8.1. Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

WebLogic Tuxedo Connector (WTC) Known Issues

Known Issues in WebLogic Server 8.1 SP2

Patch Available for Sun Java 2 1.4.2 SDK, Oracle 10g Driver, and SQL Server, Sybase or DB2 Database Users

Core Known Issues

Change Request Number

Description

CR263825

You may experience performance issues due to changes in JRockit SocketMuxer support for JRockit 1.4.2_10 and all later 1.4.2 releases.

Workaround:

Contact your BEA support representative for the `CR263825_810sp6` patch.

Web Services Known Issues

Change Request Number

Description

CR107595

SSL does not work for J2ME clients on WebLogic Server 8.1.

Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.

Web Services Known Issues

Change Request Number

Description

CR107595

SSL does not work for J2ME clients on WebLogic Server 8.1.

Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.