Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for AIX Based Systems (64-Bit)

Part Number E14771-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

25 Oracle User Messaging Service

This chapter describes issues associated with Oracle User Messaging Service. It includes the following topics:

25.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

25.1.1 XML File Handle Left Open after Upload Fails

If an error occurs when uploading a user messaging preferences XML file using the WLST manageUserMessagingPrefs command, the XML file handle is left open. On the Microsoft Windows platform, this file cannot be deleted until you exit the WLST shell.

25.1.2 Messages Metrics Rendered as Unavailable in the Performance Page for User Messaging Server

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.

25.1.3 UMS URLs Unavailable After Restart

Upon restarting the UMS 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 UMS 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 UMS server again (two or more restarts may be required).

  • If multiple UMS server restarts are not sufficient, then restart the entire Oracle WebLogic Server instance.

25.1.4 User Preferences User Interface Renders Improperly

Intermittent UI rendering errors have been reported in some languages, due to the generation of a corrupted .css file. If you experience problems, follow these steps to work around the issue:

  1. Delete the cached, auto-generated .css file for the affected locale (or simply, all locales) on the server located at DOMAIN_HOME/servers/<server_name>/tmp/_WL_user/usermessagingserver/<random_name>/public/adf/styles/cache and restart the usermessagingserver application using Oracle Enterprise Manager Fusion Middleware Control. Have all users clear their browser caches.

    The next time the UI is accessed from a browser, a new .css file will be generated for the desired locale, and it is very likely that it will be a valid .css file. If not, repeat this process a couple of times.

  2. If the previous solution does not work, disable content compression in the web.xml file of the User Preferences Web Module located at DOMAIN_HOME/servers/<server_name>/tmp/_WL_user/usermessagingserver/<random_name>/sdpmessaginguserprefs-ui-web.war. In particular, extract web.xml, add the following <context-param/> to it:

    <context-param>
      <param-name>org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION</param-name>
      <param-value>true</param-value>
    </context-param>
    

    Then, re-archive it to the war module.

    Finally, restart the usermessagingserver application using Oracle Enterprise Manager Fusion Middleware Control.

25.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

25.2.1 Configure VoiceXML Driver Receive URLs Correctly

In a clustered (high-availability) environment with Oracle HTTP Server (OHS) configured, do not use the OHS port to configure the VoiceXML Driver Receive URLs. Using the OHS port to configure the VoiceXML Driver Receive URLs will cause a conflict with the drivers.

Each Voice XML Driver must be configured with its own WLS server's port (as described in the parameters' documentation).

25.2.2 UMS Driver Configuration Changes Not Immediately Effective

When you change a driver's configuration and then restart the driver, the changes will not take effect until all managed connections in the pool are destroyed (900 seconds [15 minutes] by default). Take one of these actions to ensure that the connections are destroyed:

  • When performing driver configuration changes, stop the driver application and wait for 15 minutes. Then re-start the driver application.

    Note:

    If you follow this recommendation and the wait time of 900 seconds (15 minutes) is too long, you can reduce the time using the Oracle WebLogic Server Administration Console as follows:
    1. Click Deployments.

    2. Select the desired UMS Driver deployment.

    3. Click the Resource Adapter Type module.

    4. Click Configuration > Outbound Connection Pools.

    5. Click the DriverConnectionFactory group.

    6. Click Connection Pool.

    7. Edit the value of Shrink Frequency Seconds (for example, set to 120 seconds).

    8. Click Save, and save the changes to a deployment plan file when prompted.

    9. Restart the UMS driver deployment to include the new plan.

    Remember that if Shrink Frequency is reduced to a short interval, it may eventually have a negative impact on the performance of the driver as idle connections will be recycled frequently.

    OR

  • Restart the entire Oracle WebLogic Server after performing driver configuration changes. The new changes will take effect immediately upon server re-start.

25.2.3 JavaMail Truncates Attachments

UMS and Oracle Fusion Middleware use Sun's JavaMail (http://java.sun.com/products/javamail/) for various mail and messaging operations. JavaMail is used extensively in the UMS email driver, as well as in Oracle Fusion Middleware Webservices (including the UMS Parlay X API) to handle MIME-encoded content.Oracle Fusion Middleware Release 11gR1 includes JavaMail version 1.4. This version of JavaMail has a bug that may cause multipart web service content (SOAP attachments) larger than 8kb to be truncated. This behavior will occur when using the UMS Parlay X SendMessage interface; if the message content is a multipart object, the content beyond 8kb may either be truncated silently, or the operation may fail if the truncation causes a decoding failure.This issue is resolved in JavaMail version 1.4.1. In order for the new JavaMail library to take effect, it must be made available in the Oracle WebLogic Server system classpath so it is available to the web service infrastructure.

To accomplish this, use the PATCH_CLASSPATH environment variable. Libraries and directories listed in this classpath are prepended to the system classloader's classpath. You can either set this environment variable manually in your environment each time you start a server where UMS is running, or editDOMAIN_HOME/bin/setDomainEnv.sh (UNIX) or DOMAIN_HOME/bin/setDomainEnv.cmd (Windows), updating the line where PATCH_CLASSPATH is set, making sure to include the path to the JavaMail 1.4.1 library.

25.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

25.3.1 Finding User Messaging Preferences URL

The User Messaging Service documentation (in both the Developer's and Administrator's guides) did not list the location of the User Messaging Preferences UI. The standalone user interface is available at:

http://<host>:<port>/sdpmessaging/userprefs-ui

The User Messaging Preferences UI is also embedded in the SOA Worklist application. You can access it from the Worklist application by choosing Preferences > Notification.