It includes the following topics:
This section describes general issue and workarounds. It includes the following topics:
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.
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).
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.
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). 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.
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
The com.jcraft.jsch.JSchException: verify: false exception is intermittent. As a workaround, try to upgrade again.
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. As a workaround, if you want to handle every tweet only once, you can use the header containing the Twitter Id.
Issue and Workaround
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. 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.
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. The workaround is to manually enter the value for schema name.
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. 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:
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.
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:
This section describes configuration issues and their workarounds. It includes the following topics:
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. To resolve this issue, follow the instructions for using the correct SSL trust store. Replacing the DemoTrust keystore 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.