Troubleshooting WebLogic JMS 10-3
edit cdServersmyserverServerDebugmyserver
startEdit setDebugJMSBackEnd,true
save activate
Note that you can also use WLST from Java. The following example shows a Java file used to set debugging values:
import weblogic.management.scripting.utils.WLSTInterpreter; import java.io.;
import weblogic.jndi.Environment; import javax.naming.Context;
import javax.naming.InitialContext; import javax.naming.NamingException;
public class test { public static void mainString args[] {
try { WLSTInterpreter interpreter = null;
String user=user1; String pass=pw12ab;
String url =t3:localhost:7001; Environment env = new Environment;
env.setProviderUrlurl; env.setSecurityPrincipaluser;
env.setSecurityCredentialspass; Context ctx = env.getInitialContext;
interpreter = new WLSTInterpreter; interpreter.exec
connect+user+,+pass+,+url+; interpreter.execedit;
interpreter.execstartEdit; interpreter.exec
cdServersmyserverServerDebugmyserver; interpreter.execsetDebugJMSBackEnd,true;
interpreter.execsave; interpreter.execactivate;
} catch Exception e { System.out.printlnException +e;
} }
}
Using the WLST is a dynamic method and can be used to enable debugging while the server is running.
10.2.1.4 Changes to the config.xml File
Changes in debugging characteristics, through console, or WLST, or command line are persisted in the config.xml file.
This sample config.xml fragment shows a transaction debug scope set of debug attributes and a single JMS attribute.
Example 10–1 Example Debugging Stanza for JMS
server
10-4 Configuring and Managing JMS for Oracle WebLogic Server
namemyservername server-debug
debug-scope nameweblogic.transactionname
enabledtrueenabled debug-scope
debug-jms-back-endtruedebug-jms-back-end server-debug
server
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.
