Navigation

    Best APM Solution for Oracle WebLogic Server & FMW Product Family
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Download

    Function "possible root cause" in debug steps

    General Support & Troubleshooting
    cpu stuck threads overload
    2
    2
    441
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gitodesign
      gitodesign last edited by

      I am trying to debug an cluster communicaiton failed in my domain betwen Weblogic and Webcenter Content and an useful fonctionality for WLSDM can be as an important tool for it.
      I have SystemCpuLoad rise up to 100% and make node failed. So with WLSDL, there is a tool (in green) which can suggest a “possible root cause”.

      But I need a license to use it.
      So I’m doing step to obtain free license and processing all of best functionality of WLSDM,

      11.png

      1 Reply Last reply Reply Quote 0
      • wlsdmsupport
        WLSDM Support last edited by

        You can analyze high CPU consumers and backend events in the “possible root cause page”/ “thread analyze page”. This page gives you important tips for errors/hogger/stuck threads.

        You need to have a valid license to monitor these pages.

        WLSDM Community Support Team

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        WLSDM: Native WebLogic Monitoring & Diagnostics

        Copyright © 2021 WLSDM Community & Support Portal | WLSDM.COM | WLSDM Blog