《Oracle BPM 10.3》.pdfVIP

Oracle BPM 10gR3 Troubleshooting JMS Issues for Weblogic Oracle BPM 10.3 Troubleshooting JMS Issues with Weblogic. Author: BPM Sustaining Engineering Last Updated: April 29, 2010 Oracle Corporation – Proprietary and Confidential Oracle BPM 10gR3 Troubleshooting JMS Issues for Weblogic Table of Contents Affected BPM versions3 Troubleshooting JMS Issues 3 Introduction3 Collecting the necessary information3 Analyzing Topic Logs4 Analyzing Queue Logs4 Analyzing Weblogic Logs5 Putting all this information together5 Oracle Corporation – Proprietary and Confidential Oracle BPM 10gR3 Troubleshooting JMS Issues for Weblogic Affected BPM versions This document applies from BPM 10.3 MP 1 and so on. Troubleshooting JMS Issues Introduction This document explains how to troubleshoot JMS issues related with the internal engine queue or topic. This document does not cover troubleshooting customer JMS resources. After reading this document, the reader will be able to collect the appropriate information and Collecting the necessary information The first step is to configure the logging settings so as to get the necessary information. To troubleshoot a Topic issue, you have to do the following: 1. Set the BPM Engine log severity to DEBUG 2. Set the workspace log severity to ALL 3. Add the system property “fuego.papi.news.debug=true” to the engine and workspace JVM’s. 4. Configure the JMS Topic logging a. For a Topic: /docs/cd/E12839_01/apirefs.111 1/e13952/taskhelp/jms_modules/topics/ConfigureTopicLogg ing.html b. For a Uniform Distributed Topic: /docs/cd/E12839_01/apirefs.111 1/e13952/taskhelp/jms_modules/distributed_topics/Configu reUDTLogging.html To troubleshoot an E