|
|
|
|
|
Exception com.bea.plateng.patch.PatchInstallationException is thrown when you apply or remove patch using Smart Update or during an incremental installation to a BEA_HOME with Node Manager already running
When Node Manager is running, the process locks the file weblogic_patch.jar. As a result, patch cannot be installed or removed successfully because it fails to update weblogic_patch.jar.
Operating System: Windows
Workaround: Shut down Node Manager when you perform incremental installation or invoke Smart Update from the same BEA_HOME.
|
|
|
Silent installer fails when installing Platform in an existing BEA_HOME containing WLS 10.0MP1, which was installed using WLS 10.0 MP1 installer
Workaround: Install WebLogic Platform 10.2 by using one of the following methods:
- Use the GUI mode of installation
- Use the WebLogic Platform10.2 installer to install WLS 10.0 MP1; avoid using the WLS 10.0 MP1 installer.
|
|
|
Deployment of WebLogic Portal applications fails in a WebLogic Platform 10.2 domain that is upgraded from WebLogic Platform 8.1 SP5 domain
Workaround: On the 8.1 domain, open the domain-info.xml file from the _cfgwiz_donotdelete directory. Search for the following text:
name='WebLogic Portal Extension'
Remove the extra space between the words Portal and Extension and then proceed with the domain upgrade.
|
|
|
You cannot rollback WebLogic Server 10.0 MP1 to the previous version using Platform uninstaller
All products in WebLogic Platform 10.2 are based on WLS 10.0 MP1 (10.0.1). The WebLogic Platform uninstaller allows you to rollback WLS 10.0.1 to 10.0.0 when WLP 10.2, WLI 10.2, and WLW 10.2 are installed. However, you must not rollback WLS to 10.0.0 because it is not a valid product combination.
Workaround: Uninstall WLP 10.2, WLI 10.2, and WLW 10.2 and then rollback WLS to 10.0.0.
|
|
|
com.bea.plateng.domain.ValidateException when extending ALSB cluster domain with WLI
When you create either a WLI or an ALSB domain, the wls_webservice.jar template is applied to the products. When extending the WLI domain with ALSB or ALSB domain with WLI, the Configuration Wizard applies the wls_webservice.jar template again, resulting in com.bea.plateng.domain.ValidateException.
Workaround: You can either use the Configuration Wizard or use a WLST script to extend the domain.
Using Configuration Wizard
- Create an ALSB cluster domain.
- Launch Configuration Wizard to extend the ALSB cluster domain using templates.
For more information about extending a domain using templates, see
Extending an Existing Domain.
- In the Select Extension Source screen of Configuration Wizard, browse to BEA_HOME
\wli_10.2\common\templates\ and select p13n.jar.
- Close the Configuration Wizard after extending the domain.
- Repeat steps 2 to 4 for
wli_worklist.jar and wli_jpd.jar templates (in step 3, choose wli_worklist.jar and wli_jpd.jar respectively.
| Note: |
Every time you extend the domain with a new template, you must finish the domain extension process. Domain extension does not work if you click Previous after extending a domain with one template and without closing the Configuration Wizard. You must use the templates p13n.jar, wli_worklist.jar, and wli_jpd.jar in the same order. |
Extending the domain using WLST is easier than using the Configuration Wizard. Use the script ExtendDom.py, which is attached to
CR359409. To support the loadDB operation and properties, three more scripts are attached to the CR— dataSourceSetupOracle.py, dataSourceSetup.py, and propertyUtil.py. Copy these scripts to the WLST path. Follow these steps:
- Edit
ExtendDom.py as per your environment (lines 12-22).
- Copy the other three scripts to the same folder as
ExtendDom.py.
- Launch WLST (
$WLSERVER_HOME/common/bin/WLST.cmd).
- Run
execfile('$PATH/ExtendDom.py')
-
exit()
|
|
|
java.util.zip.ZipException when you install Weblogic Integration 10.2 in a directory other than BEA_HOME
When you install WebLogic Platform, you can specify a non-default product Home for WebLogic Integration. However, WebLogic Integration does not work in this case.
Workaround: Install WebLogic Server and WebLogic Integration together in the same BEA_HOME. The WebLogic Server directory must be BEA_HOME/wlserver_10.0 and WebLogic Integration directory must be BEA_HOME/wli_10.2.
|
|
|
FileNotFoundException when using the Previous button in the Configuration Wizard
After creating a domain by using the Configuration Wizard, you cannot use the Previous button to go back to the Welcome screen of the wizard.
Workaround: To create another domain, exit the Configuration Wizard and restart the wizard.
|
|
|
*.jks files are not included when unpacking a WebLogic Portal domain template
When you unpack a WebLogic Portal domain template, which was created by using the pack command or the Domain Template Builder, and unpack the template into a managed server domain, the managed server fails because *.jks files are missing.
Workaround: Copy the *.jks files from the original domain to the new domain.
|
|
|
WebLogic Portal domain created on Windows cannot be transferred to Solaris
While creating portal domain template, pack (or Domain Template Builder) refers four different libraries to the same directory causing conflicting libraries references in the config.xml inside the resulting template.
Operating System: Windows, Solaris
Workaround: Use Domain Template Builder to create the portal domain template. In the "Add" or "Omit" Application screen, try to customize the path to differentiate the paths to those different libraries:
content-management-app-lib#10.2.0@10.2.0
content-management-web-lib#10.2.0@10.2.0
webdav-app-lib#10.2.0@10.2.0
webdav-web-lib#10.2.0@10.2.0.0
|
|
|
Installation fails when the BEA_HOME path name is long
The patch installation fails ( java.lang.IllegalArgumentException) during the patch install process when the BEA_HOME path name is long.
The patch system uses the java Preferences class to determine the default location for the patch cache directory. It uses the absolute path for BEA_HOME as the basis for a node name to retrieve this data. This class has a limitation of 80 characters for node names, and therefore throws an exception when the path name is long, causing the patch installation to fail.
Operating System: Solaris
Workaround: The absolute path for the BEA_HOME directory must not exceed 70 characters.
|
|
|
Using WLST to run a script that uses loadProperties fails when a property name in the file contains improper characters.
An error message is displayed when you use loadProperties to load a property that contains a . (period) character in the property name.
Workaround: In the loadProperties file, specify the property name without using the . (period) character. For example, use sbm instead of sbm.db.default as property name.
|
|
|
On Solaris, when multiple users run Domain Provisioning tools like the Configuration Wizard, Domain Stop Server Script or WLST Off-Line Scripting, it is possible that subsequent users of the tool might encounter error messages like:
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/lib/tools.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/weblogic91/server/lib/weblogic.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/weblogic91/server/lib/webservices.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/jre/lib/rt.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/jre/lib/jsse.jar'
This message appears because WLST creates a temporary directory (for example, on Solaris it is /var/tmp/wlstTemp) that gets shared by all users and it is unable to differentiate between users. As a result, access to the directory gets blocked when the user accessing the directory is not the one who originally created the directory.
Workaround: Manually adjust directory permissions.
|
|
|
Unknown Publisher Security Alert
On the Windows platform, an Unknown Publisher security alert may be encountered when launching a downloaded 9.2 installer, even though BEA's digital signature is present and correctly registered.
This is a known Microsoft Windows problem with very large digitally-signed files. BEA has already filed a support case with Microsoft, Case # SRX060608602617. Contact BEA Customer Support for more information.
Operating System: Windows
|
|
|
Installer hangs on Windows XP during Node Manager configuration
If you choose to install Node Manager as a Windows service, which is an option available via a custom installation, the installation program may hang after you specify a listen port for Node Manager.
This problem may occur if Windows Firewall is running, and the listen port chosen for Node Manager has not been specified as a Windows Firewall exception.
Operating System: Windows XP Professional with Service Pack 2
Workaround: Before you run the installation program, do either of the following:
- Turn off Windows Firewall (recommended)
- Add the port you want to use for the Node Manager listen port as a Windows Firewall exception
If you choose to turn off Windows Firewall prior to installation, you can turn it back on after the installation procedure is complete.
|
|
|
Configuration of application-scoped resources cannot be changed in domain template
If you create a template or extension template of a domain that contains application-scoped resources, and then create or extend a clustered domain on the basis of that template or extension, the Configuration Wizard may not properly retarget the application-scoped resources. If the template on which a clustered domain is based contains application-scoped JMS or JDBC resources, the domain may fail to start.
Workaround: Note the following best practices for creating domains and templates:
- When creating a domain or extension template, include only JMS and JDBC resources that are global to the domain and that can be customized during the domain creation process; for example, JDBC data source and JMS file store settings for the domain, or cluster configuration settings.
- Rely on the application and on the application deployment process to create the required application-scoped resources in the target environment.
- If you are migrating an application from a non-clustered to a clustered domain, and the application includes packaged JMS resources for which you want to have scalability and load balancing, you can do the following:
— In place of each JMS queue in the packaged JMS module, create a uniform distributed JMS queue.
— Configure a JMS server for each Managed Server in the cluster.
— Include the connection factory and the uniform distributed queues in the same sub deployment group, and deploy them to the cluster.
When the application is deployed, each Managed Server in the cluster has a connection factory and a member for each distributed queue. For information about configuring JMS for a clustered environment, see
“Configuring Clustered WebLogic JMS Resources” in Configuring and Managing WebLogic JMS.
- After you create or extend the domain, you may need to perform additional steps to make sure that the application and its application-scoped resources are targeted and deployed properly for a clustered environment. For more information on the targeting and deployment of application-scoped modules, see
“Deploying Applications and Modules” in Deploying Applications to WebLogic Server.
|
|
|
QuickStart is not displayed correctly after installation
When installing AquaLogic Service Bus or WebLogic Server, if you specify a directory for either the BEA Home directory or WebLogic Server Home directory that contains a multibyte character set in the directory name, QuickStart is not displayed correctly after the installation is complete.
Operating System: Any system in which the Sun Java 2 J2SE 5.0 is used.
Workaround: During installation, choose directories for BEA Home and WebLogic Server Home with names that include only the ASCII character set.
|
|
|
Exception java.lang.UnsupportedOperationException thrown from domain configured using WLST offline
When operating in offline mode, WLST does not support the creation of security roles. If a WLST offline script includes statements that define security roles, WLST terminates abnormally when executing the script, throwing the java.lang.UnsupportedOperationException exception.
Workaround: Use WLST in online mode to specify security roles.
|
|
|
Limited support in Template Builder for compatibility-mode security
When using the Domain Template Builder to create a template from a domain that contains a Compatibility security configuration, you cannot create or assign additional users, groups, and global roles.
Workaround: After you create a domain based on a template that contains a Compatibility security configuration, boot the domain and add users, groups, and roles via the WebLogic Server Administration Console.
|
|
|
Server fails to start when domain name includes a dot and the dot is preceded and followed by strings of a certain length
If you create a domain and assign a name that has all the following characteristics, the domain will not start:
- The name includes the period character (.).
- Two alphanumeric characters precede the period.
- Five or more alphanumeric characters follow the dot.
For example, a domain created with the name zq.domain will not start.
Workaround: When choosing a domain name, do one of the following:
- Do not use a name that contains a dot character.
- If you use a dot character, make sure that you provide more than two characters preceding the dot.
|
|
|
PointBase is not disabled after a domain is extended using two or more extension templates, and an extension template other than the first is used to change the database from PointBase to a production RDBMS
If you extend a domain using two or more extension templates, and switch the database from PointBase to a production RDBMS when applying the second template or a subsequent one, PointBase is not disabled for the domain.
Workaround: Two workarounds can be used to avoid this problem, as follows:
- When extending the domain using the first extension template, specify the production RDBMS. This step ensures that subsequent extension templates do not re-enable PointBase.
- When starting the domain, run the WebLogic Server start script specifying the
nopointbase option. For example:
UNIX:
startWebLogic.sh nopointbase
Windows:
startWebLogic nopointbase
|
|
|
WebLogic Server fails to start and displays the message that the server is not found in the WL_HOME directory
A message similar to the following is displayed when you try to start WebLogic Server:
The WebLogic Server wasn't found in directory directory-name. Please edit the setWLSEnv.cmd script so that the WL_HOME variable points to the WebLogic installation directory. Your environment has not been set.
This problem is caused by a Windows bug that limits the length of the directory name you can use for the BEA Home directory.
Workaround: Do not choose a BEA Home directory name that contains more than 12 characters.
|
|
|
Thread dump occurs when Ctrl+C is used to stop server
Using Ctrl+C to stop a WebLogic Server instance results in a thread dump in the command window from which the server was started. This problem occurs because the RDBMS configured for the domain halts before the WebLogic Server shutdown procedure is completed.
This problem can happen in either the WebLogic Server Examples domain or Avitek Medical Records domain when configured with the default PointBase RDBMS, but potentially can happen in any domain in which the RDBMS is configured to start and stop with WebLogic Server.
Operating System: Windows
Workaround: The recommended way to shut down a WebLogic Server instance is via the WebLogic Server Administration Console. For details, see
“Starting and Stopping Servers” in Managing Server Startup and Shutdown.
|
