This chapter describes the issues associated with Oracle Platform Security Services:
Node Manager Fails to Start After Configuring Oracle User Messaging Service and Oracle HTTP Server
Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server
Exceptions Occur while Registering Multiple Drivers and Access Points
User Messaging Service schema does not have connect button in the Upgrade Assistant
Issue
Impacted Platform: Generic
In Oracle Enterprise Manager Fusion Middleware Control 12c, the User Messaging Service Extension driver will be displayed under the User Messaging Service folder, instead of the Application Deployments folder in the left navigation pane. The driver performance data is also available for the extension driver. This is an expected behavior.
Workaround
No workaround available.
Issue
Impacted Platform: Generic
In a cluster environment, the node manager may fail to start if you have configured Oracle User Messaging Service (UMS) and Oracle HTTP Server in a domain with Oracle Real Application Clusters (RAC) multi data sources.
Workaround
In a clustered environment with RAC setup, you may have to increase the maximum number of connections allowed on the database server. Set this value to the sum of maximum number of connections per data source for each WebLogic Server. For example, when Oracle RAC is used with three nodes, that is two WebLogic Servers with three Oracle RAC data sources, set the maximum number of connections to 600 (2 x 3 x 100).
Issue
Impacted Platform: Generic
When no metric data is found (for example when no messages have been sent or received after server setup), the Metrics Performance page will display Unavailable. This is not a problem with the software, and the Performance reporting is operating properly. As soon as Send and Receive traffic exists, the Performance page will display results normally. The UMS server home page may also display the message counts (in Statistics section) as Unavailable.
Workaround
No workaround available.
Issue
Impacted Platform: Generic
Upon restarting the User Messaging Service server (usermessagingserver) from Oracle Enterprise Manager Fusion Middleware Control or through Oracle WebLogic Console, you may get an error: Error 503--Service Unavailable when attempting to access any URLs served by the User Messaging Service server, such as the User Preferences UI (/sdpmessaging/userprefs-ui) or the various Web Services endpoints. This error occurs intermittently in cases when the Oracle WebLogic Server is heavily loaded (such as with a SOA instance).
Workaround
To work around this issue:
Restart the User Messaging Service server again (two or more restarts may be required).
If multiple User Messaging Service server restarts are not sufficient, then restart the entire Oracle WebLogic Server instance.
Issue
Impacted Platform: Generic
In some scenarios, while upgrading UMS from 11g to 12c, the upgrade may fail with the following error:
[2014-04-10T20:38:14.915-07:00] [UCSUMS] [ERROR] [] [upgrade.UCSUMS.UCSUMS_CONFIGURATION_PLUGIN] [tid: 70] [ecid:435559f9-7615-48f8-8e80-950a7f10e152-00000001,0] [[com.jcraft.jsch.JSchException: verify: false
Workaround
The com.jcraft.jsch.JSchException: verify: false
exception is intermittent. As a workaround, try to upgrade again.
Issue
Impacted Platform: Generic
Each time the Twitter driver is restarted, the last 20 tweets are fetched for the configured user. This means, that the first receive attempt after restarting the application might return some messages that have already been seen previously.
Workaround
As a workaround, if you want to handle every tweet only once, you can use the header containing the Twitter Id.
Issue
Impacted Platform: Generic
Access Points are registered in a new transaction meaning that if the client application registers Access Points in a transaction that is roll-backed, the Access Points are still stored.
Workaround
If the Access Points must be removed, deregister the Application as described in 5.1.2 Deregistering Messaging Client Applications at https://docs.oracle.com/middleware/1213/ums/administer/ns_monitor.htm#UMSAG37181.
Issue
Impacted Platform: Generic
While upgrading the UMS schema using Oracle Fusion Middleware Upgrade Assistant, if the Individually Selected Schemas option is chosen, the connect button that is used to obtain connection to the database, and the drop-down list that is used to populate the available UMS schema names will not be present.
Workaround
The workaround is to manually enter the value for schema name.
Issue – Resend for deployment with unclustered managed servers
Impacted Platform: Generic
In a domain with UMS deployed in multiple unclustered managed servers, the Message Status page in EM for one UMS server can display messages sent through another server in the domain. Resending a message that was originally sent from another server will result in a resend failure. A resend operation must be attempted from the same server through which the message was originally intended to be sent.
Workaround
To resend the message through another server, navigate to the Message Status page of the right UMS server target in the domain and resend. For example, in a domain with two managed servers (a_ums_server and b_ums_server), perform the following steps for a proper resend:
Select target "usermessagingserver (a_ums_server)" from the left navigation tree, and click on the Message Status menu item. The page displays all messages in the message status table, based on the default search criteria.
Click on a message in the table, and view the Message Details of the message to determine the UMS server used for the original send of the message.
For instance, if the value of the Engine parameter for the selected message is "/unclustered_base_domain/base_domain/b_ums_server/usermessagingserver", the current target server (a_ums_server) does not match the server in the Engine parameter (b_ums_server). Clicking on Resend button for this selected message will result in the following error: Invalid server selected for resend message operation.
To resend this message, navigate to the "usermessagingserver(b_ums_server)" in the left navigation tree, click on the message, verify that the target name and server name in the Engine details match, and click on Resend.
Issue – Resend for deployment with multiple clusters
Impacted Platforms: N/A
In a domain with UMS deployed in multiple clusters, the Message Status page in EM for one UMS server (belonging to a cluster) can display messages sent through another server in the domain. Resending a message that was originally sent from another server (belonging to a different cluster) will result in a resend failure. A resend operation must be attempted from the same cluster through which the message was originally intended to be sent. To resend the message through another cluster, navigate to the Message Status page of the right UMS server target (one of the UMS servers in the right cluster) in the domain and resend.
Workaround
For example, in a domain with two clusters (a_ums_cluster and b_ums_cluster) with each cluster containing two managed servers (a_ums_cluster with a_ums_server1 and a_ums_server2, b_ums_cluster with b_ums_server1 and b_ums_server2), perform the following steps for a proper resend:
Select target "usermessagingserver (a_ums_server1)" from the left navigation tree, and click on the Message Status menu item. The page displays all messages in the message status table, based on the default search criteria.
Click on a message in the table, and view the Message Details section of the message to determine the UMS server used for the original send of the message.
As seen in the sample, the value of the Engine parameter for the selected message is "/cluster_base_domain/base_domain/b_ums_server1/usermessagingserver".
Since the target server (a_ums_server1) and the server in the Engine parameter (b_ums_server1) do not belong to the same cluster, clicking on Resend button for this selected message will result in the following error: Invalid server selected for resend message operation.
To resend this message, navigate to the "usermessagingserver (b_ums_server1)" in the left navigation tree, click on the message, verify that the target name and server name in the Engine details match (or are in the same cluster), and click on Resend.
Issue
Impacted Platform: Generic
The function of WebLogic Scripting Tool (WLST) command manageUserCommunicationPrefs has changed. The WLST command no longer connects to the managed server during command execution. Instead, the WLST command now reuses the MBeanServer connection to connect to the managed server. Due to this, the connecting URL, username, and password are deleted from all variants of the manageUserCommunicationPrefs command.
Workaround
No workaround available.
Issue
Impacted Platform: Generic
When upgrading Business Process Management (BPM) projects from Oracle 11g to 12c, invalid objects from Oracle Service Delivery Platform Messaging (ORASDPM) schema appear in the database.
Workaround
No workaround available.
This section describes the configuration issues and their workarounds.
Issue
Impacted Platform: Generic
Before configuring any User Messaging Service Driver (such as the Email Driver), to connect to a remote gateway using SSL, ensure that the SSL Trust Store is properly configured as described in Configure keystores in Oracle WebLogic Server Administration Console Online Help.
Ensure that the value of the JVM system property (javax.net.ssl.trustStore), if set in $DOMAIN_HOME/bin/setDomainEnv.sh (or Windows equivalent file), points to the correct trust store that you want to use. The Java Standard Trust Store is located at:
$JAVA_HOME/jre/lib/security/cacerts
or $BEA_JAVA_HOME/jre/lib/security/cacerts
With the default out-of-the-box configuration of SSL trust store, that is with the Java Standard Trust Store, the UMS driver will be able to connect to the Oracle Beehive Email Server over SSL. Note that in some installations, for example, when you have SOA installed, the Java Standard Trust Store is replaced by a Demo Trust Store. In such situations, the Trust Store may not contain the valid root certificate needed by Oracle Beehive Email Server.
Workaround
To resolve this issue, follow the instructions for using the correct SSL trust store. Replacing the DemoTrustkeystore
in the setDomainEnv.sh
file (or Windows equivalent file) with the Java Standard SSL trust store will enable UMS email driver to connect successfully over SSL to the Oracle Beehive Email Server.
Issue
Impacted Platform: Generic
The WebLogic administrator does not have the permission to edit the User Messaging Service (UMS) configuration in the Enterprise Manager for multi-tenancy. Therefore, the add, edit, and delete buttons for the driver configuration page as well as the user preference configuration page are disabled for the WebLogic administrator.
Workaround
To edit the UMS configuration, you need to log in as a partition administrator.