JMS Debugging Scopes Debugging JMS
10.2.2 JMS Debugging Scopes
The following are registered debugging scopes for JMS: ■ DebugJMSBackEnd scope weblogic.jms.backend – prints information for debugging the JMS Back End including some information used for distributed destinations and JMS SAF. ■ DebugJMSFrontEnd scope weblogic.jms.frontend – prints information for debugging the JMS Front End including some information used for multicast. ■ DebugJMSCommon scope weblogic.jms.common – prints information for debugging JMS common methods including some information from the client JMS producer. ■ DebugJMSConfig scope weblogic.jms.config – prints information related to JMS configuration backend, distributed destinations, and foreign servers. ■ DebugJMSBoot scope weblogic.jms.boot – prints some messages at boot time regarding what store the JMS server is using and its configured destinations. ■ DebugJMSDispatcher scope weblogic.jms.dispatcher – prints information related to PeerGone occurrences. ■ DebugJMSDistTopic scope weblogic.jms.config – prints information about distributed topics, and primary bind and unbind information. ■ DebugJMSPauseResume scope weblogic.jms.pauseresume – prints information about backend pauseresume destination operations. ■ DebugJMSModule scope weblogic.jms.module – prints a lot of information about JMS module operations and message life cycle. ■ DebugJMSMessagePath scope weblogic.jms.messagePath – prints information following a message through the message path client, frontend, backend, including the message identifier. ■ DebugJMSSAF scope weblogic.jms.saf – prints information about JMS SAF store-and-forward destinations. ■ DebugJMSCDS scope weblogic.jms.CDS – prints detailed information about JMS Configuration Directory Service used by various sub-systems to get the notification of configuration changes to the JMS resources configured in the server from within a cluster as well as across the clusters and domains. ■ DebugJMSWrappers scope weblogic.jms.wrappers – prints information pooling and wrapping of JMS connections, sessions, and other objects, used inside an EJB or servlet using the resource-reference element in the deployment descriptor. Troubleshooting WebLogic JMS 10-510.2.3 Messaging Kernel and Path Service Debugging Scopes
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to This Document
» Enterprise-Grade Reliability WebLogic Server Value-Added JMS Features
» Enterprise-Level Features WebLogic Server Value-Added JMS Features
» Performance WebLogic Server Value-Added JMS Features
» Tight Integration with WebLogic Server Interoperability With Other Messaging Services
» What Is the Java Message Service? WebLogic JMS Architecture and Environment
» Related Documentation Domain Configuration
» JMS Server Behavior in WebLogic Server 9.x and Later
» JMS System Modules JMS Application Modules
» Comparing JMS System Modules and Application Modules Configurable JMS Resources in Modules
» Persistent Stores JMS Store-and-Forward SAF Path Service
» What Are JMS Configuration Resources? Methods for Configuring JMS System Resources
» JMS Server Configuration Parameters
» JMS Server Targeting JMS Server Monitoring Parameters Session Pools and Connection Consumers
» Default Targeting Advanced Subdeployment Targeting
» Using a Default Connection Factory
» Connection Factory Configuration Parameters Connection Factory Targeting
» Advantages of JMS Clustering
» Configuration Guidelines for JMS Clustering What About Failover?
» Path Service High Availability Implementing Message UOO With a Path Service
» How WebLogic JMS Accesses Foreign JMS Providers Sample Configuration for MQSeries JNDI
» Targeting Uniform Distributed Queues and Topics
» Load Balancing Options Load Balancing Messages Across a Distributed Destination
» Consumer Load Balancing Producer Load Balancing Defeating Load Balancing
» Distributed Destination Load Balancing When Server Affinity Is Enabled
» Distributed Destination Migration Distributed Destination Failover
» Configure Shared Subscriptions Oracle Fusion Middleware Online Documentation Library
» Methods for Configuring JMS Application Modules
» Sample of a Simple Standalone JMS Application Module Deploying Standalone JMS Application Modules
» How to Create JMS Servers and JMS System Module Resources
» Using AQ Destinations as Foreign Destinations Driver Support Transaction Support
» Create Users and Grant Permissions Create AQ Queue Tables
» Configure a WebLogic Data Source
» Configure AQ JMS Foreign Server Destinations
» Message Driven Beans AQ JMS Extensions
» Resource References JDBC Connection Utilization Oracle RAC Support Debugging
» Controlling Access to Destinations that are Looked Up using the JMS API
» WebLogic Messaging Bridge Advanced Topics
» Monitoring Queues Monitoring Topics Monitoring Durable Subscribers for Topics
» Monitoring Message Runtime Information Querying Messages
» Moving Messages Deleting Messages Creating New Messages
» JMS Message Management Using Java APIs Managing Transactions
» Managing Durable Topic Subscribers
» Configure JMS Servers and Persistent Stores.
» Configure a JMS Module Configure JMS Resources
» Enable Debugging Using the Command Line Enable Debugging Using the WebLogic Scripting Tool
» Changes to the config.xml File
» JMS Debugging Scopes Debugging JMS
» Messaging Kernel and Path Service Debugging Scopes Request Dyeing
» Enabling JMS Message Logging
» JMS Message Log Record Format
» Consumer Created Event Consumer Destroyed Event Message Produced Event Message Consumed Event
» Message Expired Event Retry Exceeded Event
» Pausing and Resuming Production at Boot-time Pausing and Resuming Production at Runtime
» Pausing and Resuming Insertion at Boot Time Pausing and Resuming Insertion at Runtime
» Pausing and Resuming Consumption at Boot-time Pausing and Resuming Consumption at Runtime
Show more