> > WebLogic Server Virtual Edition Known and Resolved Issues
WebLogic Server Virtual Edition Known and Resolved Issues
This document describes known problems in WebLogic Server Virtual Edition. Entries include a description of the problem, and a workaround or solution where appropriate.
Change Request Number
Description and Workaround or Solution
Found In
Fixed In
Limited scaling from additional CPUs.
While WLS-VE supports multiple processor machines, using multiple processors does not improve performance to the extent it does with non-virtualized WLS server instances.
9.2 v1.0
CR316773
Using CTRL-C to shut down a WLS-VE server instance in the Virtual Infrastructure Client console window can cause an error:
Error connecting: VMX Connection handshake failed for mks of /vmfs/volumes/<volume-id-string>/<WLS-VE instance name>/<WLS-VE instance name>.vmx
Do you want to try again?
This error is harmless and can be ignored.
9.2 v1.0
CR320392
When you use the WebLogic Server Administration Server to stop a managed server, you get the message:
'The object that you were viewing has been deleted, either by you or another user. Please make another selection.'
This message can be ignored. It indicates that the managed server has been shutdown.
9.2 v1.0
CR321795
If you have an auto-mounted NFS home directory, you may see the following error message plus a stack trace during an installation:
java.lang.SecurityException: Could not lock User prefs.Lock file access denied.
If you have a normal NFS mounted home directory, you may see the following error message plus a stack trace during an installation:
java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode WARNING: Could not lock User prefs. Unix error code 37.
java.util.prefs.FileSystemPreferences syncWorld WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException:
These errors are harmless.
9.2 v1.0
CR322574
The uninstallation program reports servers as running, even though they have been shut down. You get the message:
Uninstaller has detected at least one server is running. It is recommended to shutdown all running servers before uninstallation. Do you want to continue? If yes, certain files will not be uninstalled.
Workaround:
Delete the file <domain_dir>/servers/server_name/tmp, then run the uninstallation program.
