Troubleshooting messaging

Use this overview task to help resolve a problem that you think is related to JMS messaging in WebSphere® Application Server.

About this task

Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。

To identify and resolve problems that you think are related to messaging, you can use the standard WebSphere Application Server troubleshooting facilities. Some problems are specific to a particular messaging provider; that is the default messaging provider (service integration), the WebSphere MQ messaging provider, or a third-party messaging provider.

Procedure

  1. Check for error messages about messaging:
    1. Check for error messages that indicate a problem with JMS resources.

      [AIX Solaris HP-UX Linux Windows][IBM i]Check in the application server SystemOut log at was_home\logs\server\SystemOut.

      [z/OS]Check in the SYSPRINT or SYSOUT log.

      The associated message reference information provides an explanation and any user actions to resolve the problem.

    2. Check for other informational and error messages that might provide a clue to a related problem. For example, if you have problems accessing JMS resources, check for more error messages and extra details about any problem associated with the JMS provider or with the service integration technologies that the default messaging provider uses.

      For messages related to the resource adapter (JMS) of the default messaging provider, look for the prefix: CWSJR. For messages related to service integration technologies, see the related reference topics.

  2. If you suspect that problems might be related to use of message-driven beans, see Troubleshooting message-driven beans.
  3. If you are using the default messaging provider, use the following administrative console panels to inspect the configuration of your applications and JMS resources:
  4. Go to the WebSphere Application Server support page to search for information about specific problems and solutions.
  5. Check your JMS resource configurations.
    If the messaging services seem to be running properly, check that the JMS resources have been configured correctly. For information about configuring JMS resources for each of the available messaging providers, see the following topics:
  6. Get a detailed exception dump for 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.


指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:16
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tmj_prob0
檔名:tmj_prob0.html