Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Debugging WebLogic Platform Internals

Debugging WebLogic Platform Internals

If you've ever worked as a Weblogic consultant, chances are this scenario will look all too familiar:
You're at a high-profile client site as the "BEA WebLogic Expert." You were called in last minute because they are having "intermittent" problems in their newly deployed production system. The problems appear related to the WebLogic (Server/Portal/Integration) <insert here> subsystem, but you can't be sure. There is absolutely nothing unusual in the standard output; neither is there anything amiss in the WebLogic server or domain logs.

Despite poring over the docs, newsgroups, dev2dev, and the support site ("Ask BEA"), you still can't get a handle on the problem. You've double and triple checked the client's code and their WebLogic configuration, and verified that they're following the <insert here> specs. You finish off the usual checklist:

  • Is the OS Patch Level reasonably current (at least to the level required by the JVM used)?
  • How's the OS environment (file descriptors, TCP parameters, network parameters, ulimit settings, etc.)?
  • Anything really off with JVM version and/or parameters?
  • Any type-2 JDBC drivers or other native code lurking about that could cause problems?

    No smoking gun here, unfortunately, and the client senior management is beginning to breathe down your neck. You'd fire up your favorite debugger in their QA environment (can you reproduce it there?) in an attempt to track it down, but it's not really that kind of "bug." It could very well be a product issue, you think.  You check the latest release notes but nothing seems even vaguely related.  Better open up a support case.  You open up the case and the support engineer is researching the issue but can find no related CRs, so the odds of a quick fix or workaround are long.  Maybe it's not a product issue  ...

    Does this provide you with a touch of déja` vu? I've run into variations of this scenario countless times and have subsequently uncovered a set of "undocumented" debugging parameters and properties that have helped me track down the source of trouble and saved my hide on more than one occasion. Several of these parameters have been bandied about quite a bit on the various BEA newsgroups, but never specified as a whole.

    Warning: The debugging parameters I'm about to describe are undocumented. This means that they are also officially unsupported by BEA and subject to change (or removal) at any time.

    WebLogic Server 5.1
    For those who still indulge in 5.1, Table 1 lists its debugging parameters. They are specified as system properties (either on the command line or within the global, cluster, and/or server weblogic.properties files).

    WebLogic Server 6.x/7.x
    The WebLogic Server 6.x and 7.x Debugging Parameters are tied to the ServerDebug MBean within the app server's JMX infrastructure. A WebLogic Domain's admin server and each associated managed server have a corresponding <ServerDebug> element within the config.xml file (subordinate to that server's <Server> element). Note that because these parameters are undocumented, you cannot update them using the WebLogic Console but must hand-edit the config.xml file directly. For the uninitiated, the config.xml file holds the configuration for a WebLogic Domain and lives in the domain's top-level directory for the admin server. Almost all the parameters are of the "true/false" variety (a noted exception is "DebugJAXRPCDebugLevel", which is an integer value greater than 0: the higher the number, the more verbose the output). Be sure that the administration server is not running before you edit the config.xml (otherwise, your changes may get overwritten by the running server). Also be sure that you back up the config.xml file before you begin modifying it so that you have a valid configuration should you "mess up." Note that the debugging parameters I list below are based on 7.0 sp1 and some parameters are not valid in 6.1 (the server will quickly let you know which ones upon start up!). The debug information is printed to the standard output, so ensure that you are not redirecting stdout to /dev/null (as is often the case in a test or production environment). Also, setting these parameters to "true" can result in very verbose output, so flip the debug "switches" judiciously, based on the subsystem you suspect is associated with the problems you're trying to track down (e.g., if it's an EJB-related issue, set only the DebugEJB... parameters to "true"; see Listing 1).

    In addition to these JMX-based debugging parameters, there is a set of system properties you can set for additional debugging information that is written to the WebLogic log. Most of the properties are set as such:


    These debug parameters include:


  • weblogic.iiop.ots
  • weblogic.iiop.transport
  • weblogic.iiop.marshal
  • weblogic.iiop.startup

    JDBC/Data Sources

  • weblogic.JDBCConn
  • weblogic.JDBCSQL
  • weblogic.JDBCConnStackTrace


  • weblogic.commoAdmin
  • weblogic.commoProxy
  • weblogic.deployerRuntime
  • weblogic.MasterDeployer
  • weblogic.deployTask
  • weblogic.deployHelper
  • weblogic.MasterDeployer
  • weblogic.OamDelta
  • weblogic.OamVersion
  • weblogic.slaveDeployer.semaphore
  • weblogic.slaveDeployer
  • weblogic.ConfigMBean
  • weblogic.ConfigMBeanEncrypt
  • weblogic.ConfigMBeanSetAttribute
  • weblogic.management.DynamicMBeanImpl
  • weblogic.management.DynamicMBeanImpl.setget
  • weblogic.mbeanProxyCache
  • weblogic.mbeanDelete
  • weblogic.mbeanQuery
  • weblogic.MBeanInteropList
  • weblogic.mbeanProxy
  • weblogic.registerMBean
  • weblogic.getMBeanInfo
  • weblogic.getMBeanAttributes
  • weblogic.addDependenciesRecursively
  • weblogic.MBeanListener
  • weblogic.application
  • weblogic.deployer
  • weblogic.appPoller
  • weblogic.appManager
  • weblogic.BootstrapServlet
  • weblogic.fileDistributionServlet

    Application Deployment

  • weblogic.J2EEApplication
  • weblogic.application
  • weblogic.appPoller
  • weblogic.appManager


  • weblogic.JTAGateway
  • weblogic.JTAGatewayStackTrace
  • weblogic.JTA2PC
  • weblogic.JTA2PCStackTrace
  • weblogic.JTAHealth
  • weblogic.JTAPropagate
  • weblogic.JTARecovery
  • weblogic.JTAXA
  • weblogic.JTAXAStackTrace
  • weblogic.JTAResourceHealth
  • weblogic.JTAMigration
  • weblogic.JTARecoveryStackTrace
  • weblogic.JTANaming
  • weblogic.JTATLOG
  • weblogic.JTALifecycle

    A concrete example of debugging a TxDataSource problem might be to set the following on your server's start-up command line:


    There are also a few other system properties floating around WebLogic Server that are set on the command line:

  • Dweblogic.ejb.cache.debug
  • Dweblogic.ejb.cache.verbose
  • Dejb.enableCacheDump
  • Dweblogic.ejb20.cmp.rdbms.debug
  • Dweblogic.ejb20.cmp.rdbms.verbose
  • Dweblogic.ejb20.persistence.debug
  • Dweblogic.ejb20.persistence.verbose
  • Dweblogic.ejb20.compliance.debug
  • Dweblogic.ejb20.compliance.verbose
  • Dweblogic.ejb.deployment.debug
  • Dweblogic.ejb.deployment.verbose
  • Dweblogic.ejb20.dd.xml
  • Dweblogic.ejb.deployer.debug
  • Dweblogic.ejb.deployer.verbose
  • Dweblogic.ejb.verbose.deployment
  • Dweblogic.ejb20.ejbc.debug
  • Dweblogic.ejb20.ejbc.verbose
  • Dweblogic.ejb.runtime.debug
  • Dweblogic.ejb.runtime.verbose
  • Dweblogic.ejb20.jms.poll.debug
  • Dweblogic.ejb20.jms.poll.verbose
  • Dweblogic.ejb20.security.debug
  • Dweblogic.ejb20.security.verbose
  • Dweblogic.ejb.locks.debug
  • Dweblogic.ejb.locks.verbose
  • Dweblogic.ejb.bean.manager.debug
  • Dweblogic.ejb.bean.manager.verbose
  • Dweblogic.ejb.pool.InstancePool.debug
  • Dweblogic.ejb.pool.InstancePool.verbose
  • Dweblogic.ejb.swap.debug
  • Dweblogic.ejb.swap.verbose
  • Dweblogic.j2ee.dd.xml
  • Dweblogic.kernel.debug

    WebLogic Portal
    WebLogic Portal (both 4.0 and 7.0) uses System Properties to control their debug output. These Portal properties are tied to specific classes and can be set in two different ways:
    1.   Set one or more system properties on the command line. These property names are of the form:

    debug.<fully qualified class name>.

    For example, if I want debugging information on the processing of the Entitlements Access Controller class, I'd add the following to my Portal Server start-up command line:


    2.   Create a file entitled "debug.properties" in the Portal Server working directory (in 7.0, this is the domain directory; in 4.0, this is the parent of the "config" directory). For each Portal class you desire debug output from, add a line in this file of the form:

    <fully qualified class name>=true.

    For example, if I want debugging information on the Portal Management sub-system, I create a "debug.properties" file with content similar to:


    WebLogic Integration
    WebLogic Integration also uses System Properties to enable debugging information, but the scheme here is less complex (and, some would say, less flexible) than that of Portal. Simply set the following properties on your WLI Server start up command line according to your needs:

  • Dwlc.debug.signature=true
  • Deci.repository.helper.debug=true
  • Dwli.bpm.client.security.debug=true
  • Dwli.bpm.studio.timeprocessor.debug=true
  • Dwli.bpm.studio.debug=true
  • Dwli.bpm.server.common.timedevent.debug=true
  • Dwli.bpm.server.common.xmltemplate.debug=true
  • Dwli.bpm.server.eventprocessor.addrmsgdebug=true
  • Dwli.bpm.server.eventprocessor.debug=true
  • Dwli.bpm.server.jms.debug=true
  • Dwli.bpm.server.plugin.debug=true
  • Dwli.bpm.server.workflow.debug=true
  • Dwli.bpm.server.businesscalendar.debug=true
  • Dwli.bpm.server.busop.debug=true
  • Dwli.bpm.server.workflow.action.taskduedate.debug=true
  • Dwli.bpm.server.workflow.timedevent.debug=true
  • Dwli.bpm.server.xml.debug=true
  • Dwli.bpm.server.xslt.debug=true
  • Dwli.bpm.server.workflow.start.debug=true
  • Dwli.bpm.server.workflowprocessor.debug=true
  • Dwli.common.server.errorlistener.debug=true

    These debugging parameters can be of great help (BEA Support often recommends trying out particular debugging parameters to help track down specific issues) and can also aid in your understanding of how the WebLogic Server, Portal, and Integration internals operate (which in turn sharpens your troubleshooting skills). Although they are official undocumented and unsupported (who needs real "support" for a debug property?), they can truly be a lifesaver.

  • More Stories By Steve Buzzard

    Steve Buzzard is currently working as a J2EE principal architect with Anexinet Corporation (www.anexinet.com), a leading systems integration firm headquartered in Philadelphia, with offices in New York and Washington D.C. Steve has over 19 years of experience in professional software development and has been working almost exclusively with the WebLogic Technology Stack since late 1998.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    IoT & Smart Cities Stories
    The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
    A valuable conference experience generates new contacts, sales leads, potential strategic partners and potential investors; helps gather competitive intelligence and even provides inspiration for new products and services. Conference Guru works with conference organizers to pass great deals to great conferences, helping you discover new conferences and increase your return on investment.
    Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
    We are seeing a major migration of enterprises applications to the cloud. As cloud and business use of real time applications accelerate, legacy networks are no longer able to architecturally support cloud adoption and deliver the performance and security required by highly distributed enterprises. These outdated solutions have become more costly and complicated to implement, install, manage, and maintain.SD-WAN offers unlimited capabilities for accessing the benefits of the cloud and Internet. ...
    Business professionals no longer wonder if they'll migrate to the cloud; it's now a matter of when. The cloud environment has proved to be a major force in transitioning to an agile business model that enables quick decisions and fast implementation that solidify customer relationships. And when the cloud is combined with the power of cognitive computing, it drives innovation and transformation that achieves astounding competitive advantage.
    SYS-CON Events announced today that Silicon India has been named “Media Sponsor” of SYS-CON's 21st International Cloud Expo, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Published in Silicon Valley, Silicon India magazine is the premiere platform for CIOs to discuss their innovative enterprise solutions and allows IT vendors to learn about new solutions that can help grow their business.
    DXWorldEXPO LLC announced today that "IoT Now" was named media sponsor of CloudEXPO | DXWorldEXPO 2018 New York, which will take place on November 11-13, 2018 in New York City, NY. IoT Now explores the evolving opportunities and challenges facing CSPs, and it passes on some lessons learned from those who have taken the first steps in next-gen IoT services.
    SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
    Founded in 2000, Chetu Inc. is a global provider of customized software development solutions and IT staff augmentation services for software technology providers. By providing clients with unparalleled niche technology expertise and industry experience, Chetu has become the premiere long-term, back-end software development partner for start-ups, SMBs, and Fortune 500 companies. Chetu is headquartered in Plantation, Florida, with thirteen offices throughout the U.S. and abroad.
    SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.