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 (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 are sent or received after server setup), the Metrics Performance page displays 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 displays 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

• 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

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 Administering Oracle User Messaging Service.

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

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:

1. Select target "usermessagingserver (a_ums_server)" from the left navigation tree, and click the Message Status menu item. The page displays all messages in the message status table, based on the default search criteria.

2. Click 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 Resend button for this selected message results in the following error: 

   Invalid server selected for resend message operation.

3. To resend this message, navigate to the "usermessagingserver(b_ums_server)" in the left navigation tree. Click the message, verify that the target name and server name in the Engine details match, and click 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:

1. Select target "usermessagingserver (a_ums_server1)" from the left navigation tree and click the Message Status menu item. The page displays all messages in the message status table based on the default search criteria.

2. Click 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 Resend button for this selected message will result in the following error: 

   Invalid server selected for resend message operation

3. To resend this message, navigate to the "usermessagingserver (b_ums_server1)" in the left navigation tree, click the message, verify that the target name and server name in the Engine details match (or are in the same cluster), and click 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. 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.