[Enterprise Extensions only]

Resolving problems with the extended messaging service

Use this overview task to help resolve a problem that you think is related to the extended messaging service.

The extended messaging service uses the standard WebSphere Application Server RAS facilities. If you encounter a problem that you think might be related to the extended messaging service, complete the following stages:

  1. Check for extended messaging service messages in the admin console.
    If the extended messaging service fails to initialize, parse its configuration file, or encounters some runtime error an error message labelled with WMSG is sent to the admin console. The error message indicates the nature of the problem and provides some detail.
  2. Check for more messages in the server's stdout.log.
    For more information about a problem, check the stdout.log file for the application server, which should contain more error messages and extra details about the problem.
  3. Optional: Get a detailed exception dump for extended messaging.
    If the information obtained in the preceding steps is still inconclusive, you can enable the application server debug trace for the "Messaging" group to provide a detailed exception dump.