> Release Notes > Known Limitations

Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Known Limitations

Problem ID
Description
CR364909
ALINT installation fails if wrong characters are entered in BEAHOME.
Workaround: Do not enter '+' or any other special characters in the BEAHOME field value, while running the installation program.
CR365516
Exception com.bea.plateng.patch.PatchInstallationException is thrown when you attempt to apply or remove patch using SmartUpdate or during incremental installation to a BEA_HOME with Node Manager already running.
When the Node Manager is running, the process locks file weblogic_patch.jar. As a result, patch cannot be installed or removed successfully when it fails to update weblogic_patch.jar.
Workaround: Shut down Node Manager when you perform incremental installation or invoke SmartUpdate from the same BEA_HOME.
CR359409
CR361499
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.
Operating System: All
Workaround: You can either use the Configuration Wizard or use a WLST script to extend the domain.
Using Configuration Wizard
  1. Create an ALSB cluster domain.
  2. Launch Configuration Wizard to extend the ALSB cluster domain using templates.

    3. For more information about extending a domain using templates, see Extending an Existing Domain.

  3. In the Select Extension Source screen of Configuration Wizard, browse to BEA_HOME\wli_10.2\common\templates\ and select p13n.jar.
  4. Close the Configuration Wizard after extending the domain.
  5. 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.

Using WLST
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:
  1. Edit ExtendDom.py as per your environment (lines 12-22).
  2. Copy the other three scripts to the same folder as ExtendDom.py.
  3. Launch WLST ($WLSERVER_HOME/common/bin/WLST.cmd).
  4. Run execfile('$PATH/ExtendDom.py')
  5. exit()
CR356244
ALINT domain is not represented correctly in the Windows Start Menu. The description of the links do not indicate that it is an ALINT domain.
When an ALINT domain is created, the server and the console names are misleading. This domain is an ALINT domain with both WLI and ALSB configuration defined appropriately.
Workaround: After creating the domain, rename the start menu item description to reflect the ALInt domain. To do this, right-click on the menu item, click Properties, and change the description on the General tab.
CR352916
A WLI Web Project may contain Java Web Services besides JPDs. When a SAM view is generated for such a project, only JPDs are shown in the SAM view, the Java Web Services are ignored.
A WLI Web Project may contain Java Web Services besides JPDs and Task Plan. When a SAM view is generated for such a project, only JPDs and Task Plans are shown in the SAM view, the Java Web Services are ignored.
CR349584
Using cross-domain security functionality between WLI and other domains (ALSB, ALDSP), an Invalid Subject exception is displayed on WLS console.
Workaround: None. By design, cross-domain security cannot be used for RMI calls between EJBs. RMI calls work only between JMS, JTA, MDB, and WAN replication.


  Back to Top       Previous  Next