Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Server & Application Monitor (SAM) > Outdated WebLogic Client Library in SAM

Outdated WebLogic Client Library in SAM

Updated December 19, 2017

Overview

This article details and provides steps to resolve an issue where a user is unable to maintain a stable connection to the WebLogic client library servers.

Environment

  • SAM 6.5 and later

Cause 

SAM is applying an outdated JMX Client used in WebLogic Server version 10.3.4. When using WebLogic JMX versions newer than 10.3, monitoring may not functioning as expected. For these cases, it is recommended that you upgrade the JMX Client wljmxclient.jar on the Orion main poller. 

 

When using WebLogic versions 10.3 and earlier, monitoring may not function properly due to incompatibility with wljmxclient.jar in the Orion main poller. For these cases, following the recommended resolution below for your operating system.

 

Resolution

  • Linux users: switch your polling to be Linux Agent based.
  • Windows users: use additional pollers and manually upgrade the wljmxclient.jar file on the main poller only. The file will need to be reconfigured after each upgrade to the poller.
 

 

Last modified

Tags

Classifications

Public