Skip Headers
Oracle® Fusion Middleware Release Notes for Oracle WebLogic Portal
10g Release 3 (10.3.5)

Part Number E14247-07
Go to Documentation Home
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
View PDF

1 Oracle WebLogic Portal Release Notes

This document contains information on the following subjects:

1.1 What's New in Oracle WebLogic Portal 10.3.5

The purpose of this release is to address certain changes in supported software configurations. Additional change includes:

The following guides have been updated for Oracle WebLogic Portal 10.3.5 release:

1.2 Required Patches

At the time of this publication, there are no known required patches for Oracle WebLogic Portal 10.3.5.

1.3 Supported Platform Information

For information about Oracle-supported hardware and software configurations, see "Oracle Fusion Middleware Supported System Configurations."

1.4 Supported Standards

This release of WebLogic Portal supports the standards listed in Table 1-1.

Table 1-1 Java Standards

Standard Version

JSF - Sun Reference Implementation

1.1, 1.2


1.1, 1.2, 1.3



Note: Beehive requires either Struts 1.1 or 1.2. Beehive is not supported with Struts 1.3. See "Apache Beehive and Apache Struts Supported Configurations" in the Oracle Fusion Middleware Portal Development Guide for Oracle WebLogic Portal.

JSR 170 and JSR 170-compliant repositories

1.0 Level 1 and Level 2 (excluding optional features)


2.1 (with Servlet 2.5, the default for new projects)

2.0 (with Servlet 2.4)


1.1, 1.2

Java Portlets

JSR 168 and JSR 286


1.0 and 2.0


1.1 (JSR 311)


2.4 and 2.5

1.5 Known Limitations and Workarounds in WebLogic Portal

This section describes problems that have been identified in WebLogic Portal. For each problem listed in the following tables, a problem ID called a CR number is specified. These IDs enable Oracle and users to monitor the status of issues while solutions are developed. This section groups the known limitations by functional area.

For more information, see the following sections:

1.5.1 Installation

Table 1-2 lists known limitations and workarounds for installing WebLogic Portal.

Table 1-2 Known Limitations and Workarounds for Installation

Problem ID Description


Uninstalling WebLogic Portal within a domain that includes WebLogic Integration results in removal of domain dependent files.

The uninstall process removes portal-based p13n files that WebLogic Integration domain provisioning requires.

Platform: All

Workaround: Do not uninstall WebLogic Portal.


A harmless warning is thrown by Message Driven Beans once during deployment in the WebLogic Portal Sample Application.

The Message Driven Beans throw the following warnings when the deployer can't obtain distribute destination information:

Message-DrivenEJB: MessageBufferTopicBean is unable to connect to the JMS destination: weblogic.portalApp.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC. The Error was:Can not get distribute destination information. The destination JNDI name is weblogic.portalApp.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC, the provider URL is null

This warning is thrown only once and can be safely ignored.

Platform: All

Workaround: At the time of publication of release notes, no workaround is available for this issue.

1.5.2 WebLogic Portal and Oracle Enterprise Pack for Eclipse Upgrade

Table 1-3 lists known limitations and workarounds for upgrading WebLogic Portal and Oracle Enterprise Pack for Eclipse.

Table 1-3 Known Limitations and Workarounds for WebLogic Portal and Oracle Enterprise Pack for Eclipse Upgrade

Problem ID Description


The location of WLP upgrade wizard.

The location of WLP upgrade wizard has changed. The script is located at WLPORTAL_HOME/common/bin instead of WEBLOGIC_HOME/common/bin.

Note that the upgrade wizard link from the Windows Start Menu, Oracle Products > WebLogic Server 10.x > Tools > Domain Upgrade Wizard does not start the WLP Upgrade Wizard. It points WEBLOGIC_HOME\common\bin and starts the WLS Domain Upgrade Wizard. To use the WebLogic Portal upgrade wizard, locate WLPORTAL_HOME\common\bin\upgrade.cmd and double click on it.

Platform: All platforms

Workaround: cd to WLPORTAL_HOME/common/bin and execute the upgrade.cmd/.sh script.


Possible build errors after upgrading a web project that depends on an EJB project.

After upgrading some web project which depend on classes from an EJB project in an EAR, the EJB classes will show as unresolvable in the web project in the Problems view.

Platform: All


  1. Open the web project properties and go to J2EE Module Dependencies.

  2. Go to the Web Libraries tab.

  3. Check the EJB project(s) and click OK.

That triggers a rebuild and the classes should be found.


Changes to public XmlDisassemblerContext methods.

The class com.bea.netuix.application.transform.disassembler.XmlDisassemblerContext had several methods that used methods from JDOM version 0.9. This version of JDOM turned out to be incompatible with new releases of JDOM. The 0.9 version of JDOM was repacked into* classes, and the methods in XmlDisassemblerContext have been updated accordingly. Users of these methods will have to change their code.

Platform: All

Workaround: Replace all references to methods of XmlDisassemblerContext that use org.jdom.* with*.


Potential when upgrading an application from JDK 1.5.0_06 or prior to JDK 1.5.0_07.

If you upgrade an application originally built with JDK 1.5.0_06 or earlier to WebLogic Portal 10.2, you may see an exception similar to the following when starting the server: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID=4418622981026545151, local class serialVersionUID=-9120448754896609940

The problem is actually with the 1.5.0_07 version (and later) of the JDK, in which there is an incompatible change of the serialVersionUID of the javax.xml.namespace.QName class.

Platform: All

Workaround: Set the old compatibility value by setting the system property:

com.sun.xml.namespace.QName.useCompatibleSerialVersionUID = 1.0

Or you can add the following option to the Java command in the script you use to start WebLogic Server:

- Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID = 1.0


After upgrading a 9.2.2 domain, the Portal Administration Tools' Portal Management page and Content Management page may display an Unable to Render error.

After upgrading a 9.2.2 domain, accessing the Portal Administration Tools' Portal Management page or Content Management page may result in a browser error, such as "Unable to render /framework/skeletons/wlp-tools/tree_header.jsp." Additionally, the server log contains a java.lang.NoClassDefFoundError: javelin/jsp/JspContextWrapper error. These errors occur when the pages have been first accessed in a 9.2.2 domain, and then accessed again in the upgraded 10.2 domain.

Platform: All

Workaround: Search for and delete the jsp_servlet directory under the <DOMAIN_HOME>\servers\MyServer\tmp\_WL_user\MyApp directory, where MyServer is the name of your server and MyApp is the name of the affected application.


An SQLException may occur when migrating RDBMSAuthenticator data if the data contains WebLogic Portal system user or group names during domain upgrade.

When a domain with an RDBMSAuthenticator is upgraded to 10.2 and its data is migrated to SQLAuthenticator during the upgrade, an SQLException may occur if certain WebLogic Portal system user or group names exist in the RDBMSAuthenticator. Specifically, if the RDBMSAuthenticator has the users "weblogic" or "portaladmin", or has the groups "Administrators", "AppTesters", "Deployers", "Monitors", "Operators", or "PortalSystemAdministrators", an SQLException similar to the following will occur:

SQLException when executing file:/C:/<WL_HOME>/common/p13n/db/<DATABASE>/upgrade_fromdbmsauth_towlssqlauth.sql

Platform: All

Workaround: To avoid this error, edit the file <MW_HOME>/wlserver_10.0\common\p13n\db\data\required\p13n9_insert_system_data.sql prior to running the domain upgrader. Remove from this file any INSERTs that correspond to users, groups, or group memberships that already exist in the RDBMSAuthenticator. For example, if the user "weblogic" exists in the RDBMSAuthenticator, remove the "INSERT INTO USERS" statement that applies to "weblogic".


Confusing informational message about running SQLAuthenticator.sql displayed when domain is created with "Customize Environment and Services Settings" set to Yes.

The following error message is displayed by the Configuration Wizard after domain creation:

Before booting this domain, it is necessary to run the SQL file located at <DOMAIN_DIR>\security\SQLAuthenticator.sql in order to initialize a domain security admin user in the database.?

If Run Scripts were not selected on the Run Database Scripts panel, the database objects needed to execute SQLAuthenticator.sql and other components will not exist in the database.

Platform: All

Workaround: Create a new domain and execute Run Scripts from the Run Database Scripts panel.


Deployment of an 8.1.6 application that has been upgraded to 10.3 may fail due to NoClassDefFoundErrors.

Deployment of an 8.1.6 application that has been upgraded to 10.3 may fail due to NoClassDefFoundErrors if the application was imported and upgraded in the default workspace or a workspace that had contained previously imported applications that have been deleted.

Platform: Windows 2003

Workaround: Import and upgrade all 8.1.6 applications to 10.3 using a new custom workspace that is clean.


Shared library build errors after upgrading 8.1.x application.

After upgrading, numerous build errors will display in the Problems view about issues with share libraries, such as:

'beehive-controls-1.0.1-10.0' library is on the class path of this project but is not in the weblogic-application.xml file of the EAR project

Platform: Linux

Workaround: In the EAR project, make a minor change to the EarContent/META-INF/weblogic-application.xml file (e.g. add a space or empty line) and save the file. After a build, the build error should go away.


Build and runtime error with page flow strutsMerge annotation after upgrading and application on Linux.

In an upgraded web application that uses the strutsMerge functionality in a Page Flow, a build error appears in the Problems view similar to:

File 'struts-config-merge.xml' could not be found in the web application.

If the projects are published to a server even with the error, a org.apache.beehive.netui.pageflow. UnresolvableForwardException from the Page Flow will occur at runtime.

Platform: Linux

Workaround: Create new projects in Oracle Enterprise Pack for Eclipse and import the source artifacts.


Domain Configuration Wizard fails DB connection tests for Derby

The Domain Configuration Wizard will fail the database connection tests when the datasources are configured to use Derby.

Platform: All

Workaround: The test failures occur when the Derby database that is configured for the datasources is not currently running (which is the default state for Derby configurations). This can be avoided by manually starting the Derby database prior to executing the connection tests. Otherwise, these failures can be ignored.


Domain Configuration Wizard Misleading Popup Message

A confusing and misleading popup message is displayed from the domain configuration wizards after a new WLP domain is created. This occurs when the datasources are configured to use Derby (the default configuration), and the "Run Scripts" button in the "Run Database Scripts" step of the wizard is not clicked during the creation process.

Platform: All

Workaround: Execute create_db.cmd or after creating domain. This will ensure that the misleading message will not be displayed.


NameNotFoundException thrown when using EJB control with EJB Link in Pageflow application

There is currently a problem experienced while executing a web application pageflow containing an EJB control that was defined using the EJB Link reference to the associated EJB instead of using the explicit JNDI name of the EJB. This can occur for new web applications as well as upgraded applications. The following exception will be thrown when executing the pageflow containing the EJB control:

javax.naming.NameNotfoundException: While trying to lookup 'pathName.controlName.jcx' ...

Platform: Windows, Linux

Workaround: To resolve the problem, manually edit the web application project's WEB-INF/web.xml file and add the following <ejb-ref> element template for each EJB link used by an EJB Control within the web application:

         <!-- substitute your dotted Web project relative path and EJB Control
 name -->
         <!-- EJB type can be Session or Entity as appropriate-->
         <!-- substitute your dotted EJB project relative path and EJB Home
 Interface name -->
         <!-- substitute your dotted EJB project relative path and EJB Remote
 interface name -->
         <!-- substitute your EJB jar name and EJB name in link -->

For example:


1.5.3 Oracle Enterprise Pack for Eclipse Framework and Development

Table 1-4 lists known limitations and workarounds for Oracle Enterprise Pack for Eclipse framework and development.

Table 1-4 Known Limitations and Workarounds for Oracle Enterprise Pack for Eclipse Framework and Development

Problem ID Description


The following NullPointerException occurs intermittently when deploying applications from OEPE (Eclipse).

java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.

at (

at (

at (





at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(

at org.eclipse.wst.server.core.internal.Server.publishImpl(

at org.eclipse.wst.server.core.internal.Server$

at Caused by: weblogic.application.ModuleException: [HTTP:101216]Servlet: "wsrp-1.0-ServiceDescriptionPortComponent" failed to preload on startup in Web application: "struts13". java.lang.NullPointerException

at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregisterPorts(

at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregister(

at weblogic.wsee.monitoring.WseeV2RuntimeMBeanImpl.unregister( (attached full error - unregPorts.txt)

Platform: All

Workaround: Stopping and restarting the server fixes this issue. Also, if you are redeploying the application, first remove the EAR from the server, and then publish it again.


Using the Eclipse Help > Check for Updates menu item breaks WebLogic Portal functionality in Eclipse.

The default behavior for Eclipse's "Check for Updates" menu item will upgrade WLP's Eclipse to 3.6.2 and Oracle Enterprise Pack for Eclipse to the line. The OEPE line is not compatible with the WebLogic Portal Eclipse plugins. It will cause various NoClassDefFoundErrors and NoSuchMethodErrors in Eclipse, particularly when creating projects, modifying project facets, and during upgrade; the Run > Open Portal Administration Console will not work.

Platform: All

Workaround: Do not use Check For Updates to update Oracle Enterprise for Eclipse or any of the related plugins.


JRockit JVM is the recommended JVM for iterative development.

JRockit JVM is the recommended JVM for iterative development. Using other JVMs may result in significant errors after a number of application redeployments.

Platform: Windows and Linux.

Workaround: Use JRockit JVM as the default JVM for all iterative development.


Opening WebLogic Portal Administration Console may fail to publish projects.

If your Portal EAR project has been published, untargeted, and subsequently retargeted on a server instance, the open WebLogic Portal Administration Console menu action may fail to republish your application when invoked. This will manifest itself as a 404 response code upon access to the WebLogic Portal Administration Console.

Platform: All

Workaround: Manually publish your Portal EAR Projects by right-clicking the appropriate server entry in the Servers view, and selecting Publish. The open WebLogic Portal Administration Console menu item will then work properly.


Application deployment in a domain with a DB2 database may result in a warning message regarding the privilege to perform SELECT on table SYSIBM.SYSDUMMY1.

When an application is deployed in a domain that uses a DB2 database, a harmless warning message may be displayed such as:



Platform: All

Workaround: To prevent this message, grant the privilege to perform SELECT on the table SYSIBM.SYSDUMM1 to PUBLIC. For example, GRANT SELECT ON SYSIBM.SYSDUMMY1 TO PUBLIC;


Some Oracle Enterprise Pack for Eclipse JSF tooling features are suppressed in order to support both JSF and NetUI.

When developing a Portal-enabled web application that uses JSF, some of Oracle Enterprise Pack for Eclipse's JSF tooling features are suppressed in order to support both JSF and NetUI including:

  • The button that launches the Select Navigation Case Chooser dialog does not appear in the Oracle Enterprise Pack for Eclipse property sheet.

  • Validation warnings for referencing non-existent actions are suppressed.

  • Oracle Enterprise Pack for Eclipse does not support the Ctrl+hover gesture used to click-through to navigation cases in faces-config.xml.

Platform: All

Workaround: At the time of publication of release notes, no workaround is available for this issue.


Deployed applications not visible in WebLogic Portal Administration Console

Oracle Enterprise Pack for Eclipse deploys projects as virtual applications by default. While deploying an application, if the default option Publish as a virtual application is retained, the application does not appear in WebLogic Portal Administration Console.

Platform: All

Workaround: Select Publish as an exploded archive as the publishing mode while deploying your applications using Oracle Enterprise Pack for Eclipse.


Cluster deployed application not accessible from some of the managed servers

After deploying EAR files to a cluster, the application is not accessible from some of the managed servers. Also, the status of the application is shown as failed on some of the managed servers.

Platform: All

Workaround: Restart the managed servers from where the application is not accessible.


Cannot move forward in the New Server wizard when defining a new WebLogic Runtime

When attempting to create a new server in the New Server wizard, the Next and Finish buttons appear grayed out. For a new Weblogic Runtime, these buttons may appear grayed out on the first attempt to define a new runtime.

Platform: Linux

Workaround: When adding the new server runtime, click Add Configure runtime, change the default name from Oracle WebLogic Server 11gR1 (10.3.5) (3) to the required value, and then choose the new Weblogic Home, Java Home and complete the Server runtime environment creation.


IllegalMonitorStateException thrown when connecting to a content repository

On server startup, IllegalMonitorStateException is thrown when connecting to a content repository.

Platform: All

Workaround: None

1.5.4 WebLogic Portal Framework and Development

Table 1-5 lists known limitations and workarounds for WebLogic Portal framework and development.

Table 1-5 Known Limitations and Workarounds for WebLogic Portal Framework and Development

Problem ID Description


The Export/Import Utility creates an additional locale for artifacts imported in a non-English locale.

This problem occurs in the situation where the user localizes a book in the library to a non-en_US locale, and then exports the book as a .pinc and imports the .pinc to a destination in the non-en_US locale. Upon importing the resource, scoped to the Library level, the Export/Import Utility creates an entry in the L10N_LOCALE table for all pages and books in the library rather than only in the main book, even though the other library artifacts were not localized.

Platform: All

Workaround: Avoid using the Library scope when importing the .pinc resource in a non-en_US locale.


When async rendering is enabled for a portlet, portlets cannot directly change window modes or states.

WebLogic Portal allows portlets to change the current window state and/or mode of a portlet either programmatically, or via parameters added to URLs. When async rendering (either via AJAX or iframes), these mechanisms will not provide a consistent view to the end user. Particularly, the title bar rendered above the portlet will not reflect the change in the mode or state immediately.

Platform: All

Workaround: None


Proxy portlet state management: 8.1.x consumers do not properly recover producer session timeouts.

For a federated configuration in which the consumer is running 8.1.x, the consumer may not recover properly from producer session timeouts.

Platform: All


  1. The consumer session timeout must be strictly less than the smallest positive session timeout of all producers. For example, suppose a consumer portal has three proxy portlets PP1, PP2 and PP3 corresponding to three remote producers RP1, RP2 and RP3. RP1 has no sessions (session timeout = 0), RP2 has a session timeout of 5 min. and RP3 has a session timeout of 2 minutes. Then the session timeout for the consumer must be less than 2 minutes.

  2. Assign all proxy portlets to a different group. The downside of this option is that remote portlets that wish to share state cannot.

  3. Finally, if (1) and (2) are not viable options, the user will need to close his or her browser and reopen the portal in the event of a producer session timeout.


Uncompressed URL templates must be used when generating off-site URLs.

When using GenericURL, its subtypes or the corresponding JSP tags to generate off-site URLs (i.e.: URLs to resources that are not hosted in the web application of the code generating the URL) in a web application that has compression enabled, a URL template with compression disabled must be specified.

For example,

GenericURL redirectURL = GenericURL.createGenericURL(request, response);





where "no_compression_template" is the name of a URL template that excludes the {url:compression} pseudo-token.

Platform: All

Workaround: Do not use URL compression, or do not use GenericURL to construct URLs to off-site resources.


Server port changes that are made to a running server require a portal application restart.

If a server port (HTTP or HTTPS) is made to a running server, any affected portal applications need to be restarted for the changes to be picked up.

Platform: All

Workaround: Redeploy the EAR.


WebLogic Portal does not support changing the context-root of an existing portal web application with customized portal objects.

Once a .portal file has been customized, or if entitlements have been created for a desktop, the context-root of the web application cannot be changed without losing the customizations and the entitlements.

Platform: All

Workaround: Do not change the context-root value:


The onInit events are not supported for remote portlets.

Portlets can optionally register an event handler to get notified when portlets gets initiated by registering a handler of type "onInit". This feature is not currently supported for remote portlets.

Platform: All

Workaround: In general, portlets can run onInit logic lazily either when a user interaction occurs, or when another event is handled.


Expression-based visitor roles, which use multiple-user property-set values, may return a false negative, preventing a visitor from correctly assuming the role.

If a visitor role has multiple property-based conditions OR'd together, and if any of the input values (supplied via UUP impl or the default property manager) to a condition are null, the result (and therefore the role) is indeterminate because null is not explicitly checked for.

Platform: Occurs only in XACML security providers.

Workaround: Always include a default value for property set attributes, so a null is never used during comparisons.


Portlet render dependencies do not support fully-qualified URLs to reference HTTP addressable resources.

A portlet's render .dependencies file does not support using fully-qualified URLs to reference script, style, and other HTTP addressable resources. For example, a script reference to Google Maps that is defined in a .dependencies file will result in an error such as "The look and feel resource at base path <path> could not be found."

Platform: All

Workaround: Two workarounds are available:

The com.bea.netuix.laf.DynamicHtmlRenderDependencies class programmatically supports adding script, link, and style references to a portal during rendering via its "add" methods. This class can be used in a backing file to ensure that the resources for a portlet are correctly defined.

  • Add dependencies from a portlet's view.


Note: Use of this approach is limited if multiple portlets attempt to load the same resource. If this is the case loading duplicated resources in this way should be protected against in JavaScript or should be avoided.


REST requires fine granularity to determine who can create new library portlets.

REST requires a fine granularity to control the ability for end users to create new library portlets.

Platform: All

Workaround: Use the rest-config.xml or web.xml file as follows:

  • Disable the REST servlet.

  • Disable the create portlet REST command via rest-config.xml.

  • Implement a version of to perform custom access checking and configuring via rest-config.xml.


Default polling changed from 3 to 5 seconds.

The default polling interval has been increased. This interval is set in the system property:

Platform: All

Workaround: None.


Icons do not to render in Portal Administration Console tools when a space exists in the name of a Portal EAR project.

For example, if there is a space in the name of a Portal EAR project, icons in the console do not appear in the Create Desktop wizard and the administration console displays missing icon errors:

<Aug 30, 2007 1:33:00 PM MDT> <Error> <netuix> <BEA-423139> <The look and feel resource wlp-help-16.gif could not be found in the path /framework/skins/default/images.>

Platform: All

Workaround: Remove any spaces in the Portal EAR project name.


JSF validation does not work with the portal namingContainer tag and causes IllegalStateException: Client-id.

A known problem exists in some versions of JSF 1.1, where the sequence number used to generate IDs for components that do not specify their own client ID is not reset. This eventually results in the IllegalStateException in cases where a MyFaces page is re-rendered and there is no navigational rule defined.

Platform: All

Workaround: Several workarounds are available:

  • JSF 1.2, where the generated ID sequencing is handled differently.

  • Use a version of JSF 1.1 where the issue has been fixed (currently no such versions ship with 10.2).

  • Surround the namingContainer component with an f:subview component, which serves to reset the sequence generation.

Note: No portal behavior changes due to this problem.


Cannot remove title bar from Java Portlets (JSR-168).

The title bar cannot be removed from Java Portlets (JSR-168).

Platform: All

Workaround: Use the borderless theme on your portlet to remove the title bar.


Different bean instances are used for JSF than for JSTL tags using jsp:useBean.

If a JSF portlet attempts to integrate JSTL tags with JSF managed beans using jsp:useBean, different bean instances are used for JSF than for the JSTL tags.

Platform: All

Workaround: This is due to the fact that jsp:useBean is not aware of the managed bean environment used by JSF. To work correctly, the bean instances referenced by jsp:useBean must first be "primed" by either accessing them from within JSF or explicitly calling to the variable resolver with something like:

   getCurrentInstance(), 'myVar');


When an Apache MyFaces is the underlying JSF implementation provider, invalidating the session results in an IllegalStateException.

In a JSF portlet that uses Apache MyFaces as the underlying JSF implementation provider, invalidating the session in JSF application logic results in an IllegalStateException following the processing of the JSF action.

Platform: All

Workaround: Use one of the following methods:

  • Do not invalidate the session on logout.

  • Use a different JSF implementation, such as Sun RI.

  • Use a different version of MyFaces, where the installed NavigationHandler checks to see if the request is for a MyFaces JSF bridge, checks the session validity, or catches IllegalStateExceptions when the session has been invalidated.

  • Perform the session invalidation in a backing file.

  • Redirect to an intermediate non-JSF portlet, such as a servlet or .jsp, that invalidates the session and forwards to the login page.


<f:param> JSF tag does not work with WSRP.

The <f:param> tag will not work when using WSRP. This is due to request parameters being unavailable during the pre-render and render life cycle stages. This is true for all portlet types consumed via WSRP. See "Avoid Accessing Request Parameters in Rendering Code" in Oracle Fusion Middleware Federated Portals Guide for Oracle WebLogic Portal.

Platform: All

Workaround: Parameters should be placed in a container managed bean or processed during the handlePostbackData.


Portlets must have title attribute specified to be disassembled into the database.

The .portlet XML schema allows for portlets to not specify the <title> attribute. However, titles are required for successful disassembly of a portlet into the database. Attempting to disassemble a portlet that has no <title> attribute set will produce an XmlDisassemblerException.

Platform: All

Workaround: Add a <title> attribute to your .portlet file to ensure successful disassembly.


When publishing a portlet, publishing service does not properly reflect themes from publishing contexts.

If a portlet instance is influenced by a theme, render dependencies may not properly reflect the influence of the theme. Subsequently, the published version of the portlet will not correctly render the theme. This applies to portlets published in API and URL modes.

Portlets published in full URL mode will not include visual aspects of the theme.

Platform: All

Workaround: There is no known workaround for this issue.


Harmless error message logged by Lease Manager.

The following error message is logged by Lease Manager, which is harmless and can be ignored.

<BEA-403302> <An unexpected SQL exception occurred java.sql.SQLException: Data exception -- row already exist in index PK_LEASE on table P13N_LEASE.

The error is logged only in cluster environment when two or more nodes are concurrently trying to acquire the same lease.

Platform: All, in a clustered environment.

Workaround: None, not required.


Asynchronous JavaScript imports via XIE may cause Internet Explorer 7 to hang if referenced script does not exist.

If portlet content or render dependencies are loaded via XIE that refer to an external JavaScript resource that does not exist, or may otherwise fail to load, XIE lifecycle processing in Internet Explorer 7+ will hang. This is because XIE attempts to mimic initial browser loading behavior by executing scripts serially, even when such scripts are fetched asynchronously by the browser, as with IE7+. If the attempt to load the script fails (typically because it does not exist), IE7+ halts advancement of the readyState field for that script at "loading" and produces no error message.

Platform: All

Workaround: Ensure that .js files referenced in this way exist at the specified path.


Content Presenter Preview Mode will not show Theme changes.

Content Presenter's Preview Mode shows the current user a preview of how the portlet will render with the current wizard settings. However, in this release the Preview Mode will not show changes to the Theme setting. To see the effect of your Theme selection, please save the changes made in the wizard.

Platform: All

Workaround: Save your changes to see your Theme applied.


Problems on Linux platform when using drag and drop operations in portal editors.

There are known problems dragging and dropping components when multiple portal (or other associated portal artifact) editors are opened simultaneously. This problem is only applicable to the Linux platform. Drag and drop operations targeting the active (visible) portal editor will be mishandled and incorrectly delivered to the underlying inactive (not visible) portal editor tab. This problem has been noted both when dragging components from the workshop design palette over to a portal editor or when using drag and drop to reposition components within a portal editor.

Platform: Enterprise Linux 5

Workaround: Close other inactive open editor tabs such that you are only working with ONE open portal (or other associated portal artifact) editor at a time.


Non-web facets are displayed when modifying the facets of a project that had facet install failures during creation.

During project creation, if a facet failed to install, the wizard for modifying the project's facets available from the project properties will show non-web facets which are not valid for the project. The wizard won't let you select those facets and their appearance is harmless.

Platform: All

Workaround: Ignore the additional facets.


No JSP created when a Page Flow Portlet is created via the Portlet Wizard.

If you use the Portlet Wizard to create a Page Flow portlet, the appropriate home jsp is not created. For example, if you create a page flow /my/Flow.jpf, then that page flow will point to a default JSP at /my/flow.jsp. However, the wizard will not create this JSP file.

Platform: All

Workaround: Manually create the jsp. Or, create the page flow first, using the page flow creation wizard, and then create the portlet from the page flow.


Inlined portlets are not automatically disassembled into the database, so inlined portlets should not be used in a portal that will be used to create a streaming desktop.

An inlined portlet is a portlet whose markup is included directly in the placeholder element of a .portal file., as opposed to a non-inlined portlet that is included in the placeholder through the use of the <netuix:portletInstance> tag. You can use the XML viewer in the IDE to see the markup for your .portal. The most common use case for inlined portlets is via remote pages. When you use the IDE to create a remote page then a .page file is built that includes remote portlets as inlined portlets.

Platform: All

Workaround: Do not use .portals with inlined portlets as templates for streaming desktops. For the use case of remote pages you will need to create your own local page, create a remote portlet for each portlet from the producer, and place the remote portlets on your page. This can be done automatically by viewing the page in the IDE, right-clicking on the portlet and selecting "Extract Portlet to New File...". This will create the .portlet file and modify your .page file to reference the .portlet file.

If your desktop is already created then you can fix the missing inlined portlets by creating a portlet file for each missing inlined portlet (using the IDE) and then add them to your desktop in the Web based Portal Administration Tools.


Struts sample app doesn't work in portal web project.

By default, when you add the Struts facets to a web project, it creates a sample index.jsp, pages/welcome.jsp, and WEB-INF/config/struts-config.xml file. After you add the Portal Framework Struts facet, those jsps and struts configuration will return a server 500 server, and a stacktrace similar to the following will show:

javax.servlet.jsp.JspException: Cannot create redirect URL: Cannot retrieve ActionForward named welcome





at jsp_servlet.__index._jsp__tag0(

at jsp_servlet.__index._jspService(

at weblogic.servlet.jsp.JspBase.service(

Truncated. see log file for complete stacktrace

Platform: All

Workaround: Don't use the sample struts files. They can safely be deleted and new struts modules created.


Serialization exception from ClipperSourceProxyServlet$WrappedServletConfig after building project.

It is possible to receive an error message in the server console like the following:

<Jan 8, 2010 11:16:58 AM MST> <Error> <HTTP> <BEA-101002> <[ServletContext@24337993[app:pEar module:perfWebJava path:/perfWebJava spec-version:2.5]] Could not deserialize the context attribute. com.bea.netuix.clipper.ClipperResourceProxyServlet$WrappedServletConfig

If you modify a .class file in a web project and access the webapp without redeploying. This will typically occur when using Eclipse after a build finishes, if you access the webapp in a browser without republishing or use the Run On Server functionality.

Platform: All

Workaround: Redeploy the webapp. In Eclipse, use the Run As|Run On Server option to access the webapp, or publish the application from the Servers view.


Extra Sessions are created on the producer.

Extra HTTP sessions are created on the producer when fetching the WSDL, getting the service description and managing proxied portlets and when releasing sessions. Customers have reporting seeing between 16 and 250 extra sessions on their producers. While these sessions are small and will time-out they may cause performance degradation.

Platform: All platforms.

Workaround: Add /producer/ to the PortalServletFilters in your web.xml as follows:

               Skip over these type of requests (no
               profile manipulation).  Pattern is glob-style. This entry 
               defaults to the above pattern.
            <param-value>/css/, /js/, /image*/, /wlwdir, /ensureAppDeployment,
           <description>Option to fire SessionLoginEvent ,
           defaults to false if not set</description>
             <description>Filter will create an anonymous profile
             for every session. Defaults to true if not set</description>
              <description>Option to track anonymous users, defaults to false if
              not set.  'createAnonymousProfile' is ignored if this is
           <description>Length in seconds visitor must be on
             site before we start tracking them . Defaults to 60 seconds if not


Pageflow portlets using JSF pages do not render content.

If a pageflow uses JSF pages for its content, these pages might not render when the pageflow is used as a portlet.

Platform: All

Workaround: Don't use JSF pages for pageflows. By default, JSF pages are created when using the New Page Flow wizard in a JSF-enabled web project. If you do not need JSF in your webapp, do not enable the JSF project facet when creating the project via the Modify facets button; alternatively, use the "WebLogic Portal Beehive Web Project Facets" preset when creating web project. If the JSF facets is already enabled in the project, it can disabled via the Project Facets Properties page on the project. If JSF is required in other parts of the project, create the pageflow via the New Portlet wizard when you create the pageflow portlet. Or, you can edit the forward path in the pageflow to point directly to the JSP and edit the generated JSP to not use JSF.


Portlet titlebar buttons do not work for IFramed portlets running in async desktop.

Portlets with an async content-type of "iframe_unwrapped", including JSR286 portlets using the container runtime option "requiresIFrame", do not work properly on an asynchronous desktop. Specifically, the titlebar buttons to allow portlet mode or state changes do not work.

Platform: All platforms. WLP 10.3 through 10.3.2, where the iframe_unwrapped content-type is supported.

Workaround: If an IFrame is required around a portlet on a desktop, do not use the asynchronous desktop feature on the desktop, or do not have the portlet's titlebar buttons displayed.


PageFlow settings do not get added to web.xml when facelets also added.

In Oracle Enterprise for Eclipse, if the Facelet facet is added to a web project that also has Beehive NetUI and Dynamic Web Module 2.5 facets, the pageflow web.xml settings will be lost. This will make PageFlows not run correctly.

Platform: All

Workaround: Follow the procedure outlined in Section, "Workaround for 9105747."


Ctrl+C, Ctrl+X, Ctrl+V (Copy, Cut, Paste) keyboard shortcuts don't work in Weblogic Portal IDE dialogs that are implemented using Swing/AWT.

There has been an Eclipse bug filed against Eclipse 3.5 (Galileo) which states that Swing text components hosted over the Eclipse SWT_AWT bridge do not receive the proper key event sequence when the Ctrl+C, Ctrl+X, Ctrl+V (Copy, Cut, Paste) keyboard shortcuts are used. To be more specific, the KEY_PRESSED and KEY_TYPED events are not being fired during the key sequence. As a result the key bindings for (Copy, Cut, Paste) operations are ignored. This does not affect text components implemented natively in the Eclipse SWT technology. For further details please refer to the following Eclipse bug report:

Platform: Windows, Linux

Workaround: Manually type text entries in all Swing/AWT dialogs hosted over the Eclipse SWT_AWT bridge. The(Copy, Cut, Paste) keyboard shortcuts cannot be used.


User must be logged in to view WebCenter portlets when SAML is enabled.

Anonymous users who try to view a WebCenter portlet when the producer has SAML enabled will see an exception.

Platform: All

Workaround: Entitle the proxy portlet so only authenticated users may view WebCenter portlets.


Served resources functionality over WSRP using local proxy contains outages.

JSR286 portlets that have serve resource functionality (implement the serveResource method) may see outages when run over WSRP via local proxy. These outages include the use of URL parameters on the ResourceURL during file upload and ResourceURL.setSecure(). In the case of the URL parameters, if the serveResource() call is uploading a file and parameters are set on the ResourceURL, the parameters are not sent to the producer as expected. For ResourceURL.setSecure(), if the serveResource request is sent over local proxy, a new session is created, which causes the producer to return an InvalidSession fault to the consumer.

Platform: All platforms

Workaround: Run WSRP JSR286 portlets with serveResource implementations through remote proxy.


Re-logging to a portal consuming the WebCenter Services producer returns InvalidCookieException.

When you log out, and then log in again to a portal consuming the WebCenter Services producer, it returns InvalidCookieException.

Platform: All

Workaround: Clear the browser cookies and then log in to the portal.


Document Explorer task flow of WebCenter Portal not working in WebLogic Portal when consumed as a remote portlet.

In a portal consuming the WebCenter Portal Services producer, from the tag cloud portlet, users cannot add or edit wiki documents. When the Document Explorer task flow of WebCenter Portal is consumed in WebLogic Portal, the functionality does not work as desired.

Platform: All

Workaround: None


Content selector tags are not retrieving content.

Content selector tags do not retrieve content when used either in a Content Presenter portlet or a content selector tag.

Platform - All

Workaround - Use contentQuery or content search tags. Workaround for 9105747

To perform the workaround for Bug 9105747, add the pageflow settings to the web.xml file as follows:

  1. Replace the action <servlet> entry with:

  1. Add the following entries to the web.xml file:

             <servlet-name>Faces Servlet</servlet-name>

1.5.5 Content Management and Search

Table 1-6 lists known limitations and workarounds for content management and search.

Table 1-6 Known Limitations and Workarounds for Content Management and Search

Problem ID Description


Renaming nodes in a library services-enabled repository can cause the version name to become out of sync with the node's name.

When library services are enabled, nodes should not be renamed. This can cause incorrect search results to be returned.

Platform: All

Workaround: None.


JSR-170 JNDI provider logs misleading error messages due to improper classloading configuration.

After configuring the JSR-170 JNDI content repository provider, users may encounter a misleading error message indicating that the object bound in JNDI did not implement the javax.jcr.Repository interface:

com.bea.content.RepositoryException: Object bound not of type javax.jcr.Repository: found a (org.apache.jackrabbit.jca.JCARepositoryHandle)

Platform: Jackrabbit Content Repository with JSR-170 JNDI provider

Workaround: Ensuring that the javax.jcr.Repository is visible within the same classloader as the content repository application and the JSR-170 adapter may resolve this issue.

For more information regarding application classloading, see:


Unclear exception when using CM versioned repository API.

The following cryptic message is displayed:

Caused by: The operation completed successfully when running code in the versioned repository. This error message originates from the JVM, and generally means that a user is trying to pass in an InputStream which has already been consumed.

Platform: All Sun JVM

Workaround: Ensure that the InputStream being passed to content management has not already been consumed or read.


Filtering on search results from is not available on the modifiedDate property.

The API ISortableFilterablePagedList.getAllFilterableProperties() indicates for the result of the that the caller may filter on the modifiedDate property. This is not currently functional as a FilterCriteria or via the ISortableFilterablePagedList.reFilter() call.

Platform: All

Workaround: Specify the modifiedDate in the search expression and filter when initially executing the search.


Delegated Administration users who can publish content need DA rights to view the Default workflow to use the Bulk Update tool.

A Delegated Administration (DA) user who has Publisher capabilities for a content repository will also need the View capability on the default workflow. An example of Publisher capabilities would be View, Update, and Publish capabilities on a content repository. If the DA publisher does not have View capabilities on the default workflow, users will encounter com.bea.content.AuthorizationException: "User does not have view privileges to view this workflow or its properties" when they attempt to use publish content using the bulk update in the Workspace View in the Content Management Administration tools.

Platform: All

Workaround: Assign the View capability for the default workflow. It is not required to assign the View capability for any other workflows, even if the content that is being published uses a custom workflow instead of the default workflow. The bug is around the validation code that mistakenly retrieves the default workflow, no matter what.


WebDAV users need read access to the default workflow.

The WebDAV code needs access to the default workflow to perform CRUD operations on any given resource in a managed WLP repository. If the logged-in user does not have the View capability on the default workflow, it could throw a (403) error message to the client.

Platform: All

Workaround: Make sure that all users accessing content management via WebDAV have the View capability on the default workflow.


CR Bridge: JCR property value constraints not visible in WebLogic Portal property choices.

When using the CM JCR Bridge, JCR property value constraints are not currently exposed in WebLogic Portal property choices. This limitation is present because some property value constraints, such as regular expressions and built-in repository constraints, cannot be resolved to a specific value.

Platform: All

Workaround: If a validation exception occurs when creating or updating a JCR property value, manually consult the JCR repository's property value constraints for the appropriate type to ensure a value meets all constraints.


Sample domains are pre-populated with ObjectClasses that do not necessarily conform to file system repository data types.

When using a file system repository, ObjectClasses are limited to only a single binary property. Some of the available out-of-the-box ObjectClasses have multiple binary properties, such as book. This makes it appear that it is possible to create a node in the file system repository of that type. However, internal validation code in the file system repository prevents this.

Platform: All

Workaround: None. When using the file system repository, nodes cannot be assigned an ObjectClass having multiple binary properties.


Error retrieving empty InputStreams from Sybase.

Whenever a user tries to store an empty input stream or a zero-byte file via WebDAV in content management, the code converts it into a zero-byte input stream and stores it in the database. However, when the data is retrieved, the database does not return an empty input stream, but returns a null. Content management then traps that null and throws an error to the user.

Platform: This problem has been known to occur in Sybase drivers.

Workaround: Do not store zero-byte input streams into content management or zero byte files via WebDAV in a Sybase database.


Copy/Paste not working with nested properties when library services are enabled.

Copy/Paste for a content item that has a nested property containing a file upload property value doesn't work and throws the following exception: flow.UnresolvableForwardException: Unable to find a forward named 'VIEW_RENDERER' on action view in page flow /content/popupsAndButtons/PopupButtonController.jpf.

To reproduce this problem:

  1. Create a new content type.

  2. Add a nested property to the content type that contains a file upload property value.

  3. Create a new content item of that new type and upload a file.

  4. Save and check in the node.

  5. Create a new folder or use an existing one and try to copy/paste the content item to the new folder by using either right click or the context sensitive button feature.

Platform: WLP 10.2 and 10.3


Don't upload any file content in a nested property until after the node is copy/pasted or clear the nested property values and re-add them after the copy/paste operation.

To allow copy:

  1. Click on the new content node

  2. Select the properties tab.

  3. Click Checkout

  4. Select the nested property's clear value checkbox

  5. Select the Clear Values button.

Caution: This will clear all your nested properties so the user must write them down or take a screenshot.

  1. Click checkin.

  2. The user is now free to copy and paste the node.


Multibyte characters in EAR names create 404 errors in Admin Tools when copying, pasting, or moving items in Content Management.

There is support in the Portal Admin Tools for copying, pasting, and moving of folders and content nodes. However, this feature returns a 404 error when the associated enterprise application name contains multibyte characters.

Platform: All

Workaround: Do not use multibyte characters in your EAR names. There are other issues with described in these Release Notes that also apply when using EARs with multibyte characters.

1.5.6 Federation

Table 1-7 lists known limitations and workarounds for federation.

Table 1-7 Known Limitations and Workarounds for Federation

Problem ID Description


MsgHeaderException thrown when accessing portlets over WSRP.

In some cases, such as when creating a new session during a WSRP PerformBlockingInteraction portlet phase, a WSEE exception is thrown:

weblogic.wsee.message.MsgHeaderException: SoapMsgHeaders already contains header of type {}WorkContext. Cannot add another one.

Platform: All

Workaround: Add a property definition to the WLS command line: -Dweblogic.wsee.workarea.skipWorkAreaHeader=true


WSRP: Portlet Preference description is not passed from the producer portlet to the proxy portlet.

When an administrator views portlet preferences for remote portlets, WebLogic Portal Administration Console does not provide a description of preferences.

Platform: All

Workaround: Use more descriptive names for preferences.


WSRP LocalProxy depends on client to send producer (session) cookies.

When LocalProxy is enabled for WSRP, the client becomes responsible for sending cookies, especially the session cookie.

In general, this is fine except in cases where the path parameter for the cookies of the producer is not the same as or a prefix of the path parameter for the cookies of the consumer. In these cases, the client will not necessarily send the producer cookies.

Platform: All

Workaround: Ensure that the session path parameter for cookies from the producer is the same as or a prefix of the path parameter for cookies from the consumer.


Registration Properties do not contain default values.

This is due to calling EntityPropertyManager.getProperties() which does not return default values.

Platform: All

Workaround: Do not use default values in registration properties. The consumer should send all values when registering.


Remote portlets' minimized title is not preferred title.

When a remote portlet sets the title programmatically, WebLogic Portal will use that title in the titlebar.This functionality is not supported when the remote portlet is minimized. When a remote portlet is minimized, WebLogic Portal will not contact the producer to render the portlet, and hence loses the dynamically set title.

Platform: All

Workaround: None


WSRP Security signatures and encryptions do not work.

Encryption (Confidentiality) and Signatures (Integrity) are not currently supported policy elements and are not currently supported for WSRP messages.

Platform: All

Workaround: Only use Identity elements in the policy


WSRP local proxy mode does not support default context path or context path containing slash (/).

If WSRP local proxy is enabled and the consumer accesses a producer with the default context path or a context path containing a slash (/), then the consumer request will fail.

Platform: All


  1. Do not configure producers that will be accessed via local proxy to have the default context path or a context path containing a slash (/), OR

  2. Do not enable WSRP local proxy mode if any of the producers that could be accessed with the local proxy are configured to have the default context path or a context path containing a slash (/).


WebLogic Portal does not support using Content Presenter in WSRP environments.

Content Presenter and its portlet instances cannot currently be used as WSRP producers in WebLogic Portal 10.2.

Platform: All

Workaround: To access Content Presenter instances remotely, use Portlet Publishing.


An "unparsable date error" occurs in the Search Versions part of the Version History tab of a content item when the browser locale is changed between searches.

Platform: All

Workaround: One way around this problem is to click Clear Search, then reset the date and perform the search again; however, the recommended best practice is to always log out of the Administration Console before changing the browser's locale setting. Changing the browser's locale during a user's session in the Administration Console is not supported.


WLP Consumer does not automatically recover when an IBM WebSphere producer's session timesout.

When consuming portlets from an IBM WebSphere producer the producer's session may timeout. When this happens the user will see an error in the portlet(s).

Platform: WLP Consumer (all versions) with IBM WebSphere Producer (all versions)


  • Set the WebSphere's producer's HTTP Session timeout to sufficiently longer than the WLP's consumers session timeout. This may be 2-4 times longer depending on your users' usage patterns.

  • Logout of the WLP consumer and log back in.

  • Write an interceptor to handle the exception and/or fault.

1.5.7 Collaboration

Table 1-8 lists known limitations and workarounds for collaboration.

Table 1-8 Known Limitations and Workarounds for Collaboration

Problem ID Description


Using external utilities to populate collaboration repository data will cause metadata corruption.

The collaboration portlets (Discussion, Tasks, Calendar, etc.) manage a separate database table to track contents of their containers and content repository items. This table can get out of sync when the repository is populated using external tools such as Propagation or Admin Tools. The following symptoms indicate that the table needs to become synchronized with the repository:

  • Error message that is logged to the server console: <Error> <Content Collaboration API> <BEA-000000> <[No count metadata could be found for node with id 'XXXX'.] >

  • - Discussions portlet shows inaccurate counts of items within categories and/or forums.

Platform: All

Workaround: Customers that experience this behavior will be instructed to download a supporting JSP that will synchronize the metadata table with the repository.

1.5.8 Production Operations

Table 1-9 lists known limitations and workarounds for Production Operations.

Table 1-9 Known Limitations and Workarounds for Production Operations

Problem ID Description


The Export/Import Utility provides limited support for localization of portlet instances at an admin level scope.

Scoping a book or page with a new locale to the library level is working. When the .pinc is exported/imported in the new locale, the new locale with new title is picked up by the WebLogic Portal Administration Console and L10N tables are updated in the database. However, this is not working for localizing a portlet instance scoped to the admin level. The imported locale is not reflected in the WebLogic Portal Administration Console for the portlet, but the L10N database tables are updated.

Platform: All

Workaround: Avoid using the admin level of scoping if you want to localize portlet instances.


In the Export/Import Utility, locale resource descriptions are not being propagated to the .pinc file.

The locale description of a book or page is not getting output to the .pinc file. Thus, an administrator is able to localize only the artifact's title and not it's description.

Platform: All

Workaround: Manually add the locale description after exporting/importing the book or page.


In the Export/Import Utility, new resources are not imported correctly when first importing in a foreign locale.

For example, if you do not have all you resources localized to a specific locale (for example, "es") and you export a desktop in locale "es", then the resources that do not have a resource (title) in "es" will do a best match algorithm. That best match could be a title in "en" (English)

Upon re-import to the destination you are telling the XIP utility that everything is in "es" and therefore it erroneously added 'en' titles in "es".

Platform: All

Workaround: Make sure all your resources have been localized in the locale you want to export. For example, first re-import the modified .portal file in the default en (English) locale and then import the modified .portal file again in the "es" (Spanish) locale.


A placeholder lock is propagated only for the current "page view" of the layout.

The Propagation Utility can track only the placeholders of the currently selected layout from the page "view." Due to this, only the locks (set using Entitlements) on the placeholders in the currently selected layout can be propagated. Propagation of locks on other layouts is not possible.

Platform: All

Workaround: Review propagation results and manually update any necessary placeholder locks.


WebLogic Portal Analytics reports for Desktop, Pages, and Portlets with the same title but from different web applications are indistinguishable.

Analytic reports do not identify which WebLogic Portal web application sourced a particular usage event. This means that if the same title is used in multiple web application portlets, multiple reports of that title will exist and there is no way to know which web application is associated with each report.

Platform: All

Workaround: Use unique title names.


Large Content Exports via Propagation May Throw TimeOutExceptions.

When exporting content, if a parent (folder) contains a large number of children (greater than 2000), a weblogic.transaction.internal.TimedOutException can appear.

Platform: All

Workaround: Reorganize the content data so that a parent does not contain thousands of children. If that is not possible, increase the JTA timeout value from the Weblogic Console from the default 30 seconds to a higher value.


Analytic report on a selected web application that has never been accessed shows activities of other non-selected web applications.

When multiple web applications in an enterprise application exist and there are activities in all the web applications except one, the Analytics report on the web application that does not have any activities shows results of the all other web applications that do have activity. After the web application is accessed, the Analytics report on the web application shows only its own activities.

Platform: All

Workaround: Make sure a web application is accessed before selecting it for the Analytics report.


ScenarioService error message observed during propagation of content management resources.

While propagating content management resources, the following error message may be observed in the console or server log files:

<ScenarioService: Error getting user profile wrapper: weblogic>

This error is caused by a campaign event firing when a content management resource, such as a node or type, is saved by propagation. The scenario service attempts to fetch the profile of the current user (the propagation user) when it does not exist. Propagation of the content resource should still complete successfully. However, it is likely that the event logic is failing to complete successfully.

Platform: All

Workaround: Disable event handling during propagation.

1.5.9 WebLogic Portal Administration Console

Table 1-10 lists known limitations and workarounds for WebLogic Portal Administration Console.

Table 1-10 Known Limitations and Workarounds for WebLogic Portal Administration Console

Problem ID Description


Portal Admin Console webapp not found at correct url without application.xml in .ear.

None of the WLP webapps deployed from library modules (i.e. admin tools, cmis rest, propagation, webdav, tool-support) are deployed to their app-scoped context-paths (i.e. ${appname}Admin, ${appname}CMISRest, etc.) from a .ear generated in Eclipse via Export|EAR.

Platform: All

Workaround: Generate an application.xml deployment descriptor for the EAR project prior to exporting the .ear file. During ear project creation, there is an option in the wizard on the Enterprise Application page to "Generate application.xml deployment descriptor". If the project already exists, you can right-click the EAR project and select Java EE Tools > Generate Deployment Descriptor Stub.


User profile update may not be seen by federated portlets.

If an administrator updates a user's profile, the user may not see the updates until they log out and log back in. This includes properties sent via WSRP to remote producers.

Platform: All

Workaround: The user must log out and back in to see the update profile.


Changes to a User Profile in Visitor Tools are not displayed in UM Tools.

Changes made outside the WebLogic Portal Administration Portal to a user profile in Visitor Tools are not displayed in the WebLogic Portal Administration Console: User Management - User Profile after a refresh. The changes are only displayed after logging out and logging back in.

Platform: All

Workaround: To see an updated user profile, log out and log back into the WebLogic Portal Administration Portal.


Content Management: Cannot clear individual values or properties for nested property types.

Nested property types are properties that have the structure of another user-defined type. For nested type properties that allow multiple values, it is not possible to clear individual values (reset them to empty or default values).

Platform: All

Workaround: To clear an individual value of a multi-valued nested property you must select the multi-valued nested property for edit and then delete the individual value using the trash can icon. You should then add it again with the same name, but with all empty values.


IM editors don't support content queries that reference user, request, and session properties.

IM editors don't support content queries that reference user, request, session properties.

Platform: All

Workaround: Use the IDE to edit content queries that reference user, request, session properties.


IM editors don't support content expression syntax.

IM editors don't support content expression syntax.

Platform: All

Workaround: Use the IDE to edit content queries that use content expression syntax.


IM editors don't support IM rules multiple actions or conditions of the same type.

IM editors don't support IM rules multiple actions or conditions of the same type.

Platform: All

Workaround: Use the IDE to edit IM rules that have multiple actions or conditions.


Administration Tools do not use wsrp-consumer-security-config.xml.

If you created a wsrp-consumer-security-config.xml in a consumer's WEB-INF directory, Administration tools will not use it when adding or editing producers or when viewing or setting proxy portlet preferences. This may result in incorrectly sending SAML or the following exception:

weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token.

Platform: All

Workaround: Set up your producer to work with the consumer's default configuration.


WebLogic Portal Administration Console does not provide a way to re-register if InvalidRegistration is returned by a producer.

The WebLogic Portal Administration Console does not provide a way to re-register if InvalidRegistration is returned by a producer.

Platform: All

Workaround: Delete the producer using the Administration Console and then recreate the producer.


No way to modify an invalid registration from the WebLogic Portal Administration Console.

If a consumer registers with a producer, and then the producer later requires additional information from the consumer, the producer will return a fault to the consumer. If you try to modify the registration properties for a producer with an invalid registration using the Administration Console, you receive an error and stack dump from whatever fault was returned by the producer.

Platform: All

Workaround: Delete the producer using the Administration Console or, manually delete the producer from the wsrp-producer-registry.xml file and then manually recreate a new producer entry.


The WebLogic Portal Administration Console displays the Add/Delete portlet preference for non-WLP producers.

The Administration Console displays UI for adding and deleting portlet preferences for remote WSRP producers. However, non-WLP WSRP producers generally have no way of supporting this functionality.

Platform: All

Workaround: WLP PAT users shouldn't try to add or remove portlet preferences from non-wlp remote wsrp portlets.

1.6 Known WebLogic Server and Platform Limitations

This section lists WebLogic Server (WLS) and other platform limitations.

Table 1-11 Known WLS and Platform Limitations

Problem ID Description


Shared library classes in web.xml not found on deployment to cluster.

If a webapp's web.xml references a class (e.g. a servlet, a filter, etc.) from a shared library, a ClassNotFoundException will be thrown when deployed to a cluster, for example:

java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet

at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(

at weblogic.utils.classloaders.GenericClassLoader.findClass(

at java.lang.ClassLoader.loadClass(

at java.lang.ClassLoader.loadClass(

at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.ja


at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnota

at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(

at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(

at weblogic.application.compiler.WARModule.processAnnotations(


Platform: All

Workaround: Target the shared library containing the class to the AdminServer as well as the cluster.


When creating a WLP domain, the Config Wizard assumes a Derby database and a default username.

Platform: All

Workaround: While running the Config Wizard, navigate and modify 'RDBMS Security Store' settings under 'Select Optional Configuration', and provide the appropriate connection parameters.


Run Scripts button in domain configuration wizard doesn't work for Derby database connections.

In the config wizard, the Run Scripts button doesn't work to initialize the Derby database for WLP domains.

Platform: All

Workaround: After creating the domain, run the create_db.cmd script on windows or script on unix and linux to create the database before starting the server.


WLP Domains created with Configuration Wizard provides wrong JDBC Pool test table names

For certain databases, WLP domains created with Configuration Wizard will generate the wrong JDBC Pool test table name in the config/jdbc/datasource.xml configuration files.

A non-fatal JDBC <Error> will be logged prior to the server reaching a RUNNING state.

Workaround: Change the connection test SQL clause in the server console as follows:

  1. After the server is started login to the server console.

  2. In the "domain structure" panel go to domain_name/services/JDBC/DataSources

  3. Click each data source name, then the "connection pool" tab, and then "Advance" at the bottom of the page.

  4. In the "Test Table Name" text box changed the sql clause according to the type of db:



    MS SQL Server: SQL SELECT COUNT(*) FROM sysobjects

    Sybase: SQL SELECT COUNT(*) FROM sysobjects

    My Sql: SQL SELECT 1

    Derby: No change.

  5. Save the changes. No server restart is needed.


See 8086654

1.7 Key Limitations Fixed in WebLogic Portal

This section lists limitations that were fixed in WebLogic Portal. See Table 1-12.

Table 1-12 Key Limitations in WebLogic Portal

Problem ID Description


Upgrade causing too many DB calls for a content selector.


Cannot copy/paste text inside any portlet in Internet Explorer 8 when using DVT.


Propagation tool changes order of pages of books which are not in scope.


Hidden flag of the desktop book is not propagated.


Propagation of changes to hidden property fails to propagate.


CMIS Rest issue with the TypeById class.


Threads stuck on RepositoryManagerDelegate with ReentrantReadWriteLock after upgrade.


Search results disappear when running bulkloader.


Page propagation removes other target pages when desktops do not match.


cm:GetProperty returns a URL to download a node rather than returning the node.


Integrating with Coherence - slowness due to multicast.


Integrating with Coherence - severe performance degradation upon invoking flush.


Duplicate portlets observed in target environment after propagation.


Content not displaying for Read Only WLP repository while using cm tags.


NullPointerException when attempting to change preference of a page in PAT.


Propagation overwrites the producer property with the source producer information.