8 Known Issues

This section includes known issues for WebLogic on JRockit VE.

• Section 8.1, "Install Oracle VM Server Patch (Version 2.2.0 Only)"

• Section 8.2, "No Support for Sample Domains"

• Section 8.3, "Performance When Using Multiple CPUs"

• Section 8.4, "xm console Command Does Not Display the Server Console"

• Section 8.5, "Initially Start Virtual Machines Using OVM Manager"

• Section 8.6, "Changes to VM Adapter Name and Version In Virtual Node MBean Are Ignored"

• Section 8.7, "Improve Performance with Conversational Web Services"

Note:

For a list of known issues in Oracle JRockit Virtual Edition 11.1.1.3.0, refer to the "Known Issues" section in the User's Guide for Oracle JRockit Virtual Edition.

For a list of known issues in Oracle WebLogic Server, refer to the Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86. []

8.1 Install Oracle VM Server Patch (Version 2.2.0 Only)

In order to fully support high availability, it is recommended that you install the patch for the Oracle VM agent and Xen packages. This patch is not required to be installed if you are using Oracle VM 2.2.1 or later.

If you do not install the recommended patch, any normal or abnormal shutdowns of WebLogic Server will result in WebLogic Server being automatically restarted by Oracle VM, regardless of whether this is the intended behavior. For example, if WebLogic Server shuts down because of a non-restartable failure, or if the user logs in to the WebLogic Server Administration Console to manually shut down a WebLogic Server VM, Oracle VM will restart the VM and server. In addition, the configured limits for maximum number of restart attempts for the server are ignored.

The Oracle VM patch is available from the Oracle Unbreakable Linux (ULN) site at http://linux.oracle.com by selecting the ovm22_i386_latest channel. For detailed instructions, see the FAQ at https://linux.oracle.com/uln_faq.html. Once you update the Oracle VM Server using the patch, ensure that the Oracle VM packages use the following minimum versions:

• ovs-agent-2.3-38

• xen-3.4.0-0.1.10

• xen-64-3.4.0-0.1.10

• xen-debugger-3.4.0-0.1.10

• xen-devel-3.4.0-0.1.10

• xen-tools-3.4.0-0.1.10

8.2 No Support for Sample Domains

This version of WebLogic on JRockit VE does not include support for the medrec, medrec-spring, or the wls-server sample domains.

However, the WebLogic on JRockit VE package includes instructions to reconfigure the MedRec sample domain in a physical environment to work with Oracle Database, and then that environment can be migrated to a WebLogic Server VM. For more information, see Using the Oracle WebLogic Server on JRockit Virtual Edition MedRec Domain With Oracle DB (wlsve_medrec_domain_with_odb.pdf).

8.3 Performance When Using Multiple CPUs

In a virtual machine that is configured with multiple virtual CPUs, in certain circumstances (for example, when there is a lot of synchronization between threads), performance might be affected.

In the current release, Oracle recommends that you start with a configuration with a single virtual CPU. If necessary, you can try adding more virtual CPUs to see if it helps improve performance, but in this release adding additional Virtual CPUs may not improve performance on all workloads.

8.4 xm console Command Does Not Display the Server Console

When a WebLogic Server VM is started using OVM Manager, the server console is not displayed automatically in the OVM machine when you execute the xm console <vm-name> command. To display the server console:

1. Execute the xm console <vm-name> command.

2. Type 1.

   The current configuration status and the server log are displayed.

3. To exit the VM console, use Ctrl + ].

8.5 Initially Start Virtual Machines Using OVM Manager

There is a delay in communication between Oracle VM Manager and Xen (xm) when initially starting the WebLogic Server VM using the xm command.

Workaround

Use the Oracle VM Manager console to initially import, discover, and approve the virtual image, and then you can safely use WLST, the Administration Console, and the xm command to start and stop WebLogic Server VMs.

8.6 Changes to VM Adapter Name and Version In Virtual Node MBean Are Ignored

The Oracle VM 2.2 adapter name and version, respectively, may be changed in the Administration Console or using WLST and result in changes to the correct Mbean, but these values are ignored when making the connection and the hard-coded values always apply.

Workaround

Specify -Dvmm.type and -Dvmm.api.version on the weblogic.Server command line.

8.7 Improve Performance with Conversational Web Services

To improve performance when using conversational Web services, include the following option in the <java-arguments> stanza of the wlsve.xml file:

-Dweblogic.store.AvoidDirectIO=true