SCX_Application_Server class

Question

Hi all,

On some monitored linux servers I've found that scx agent crashes several times a day, leaving each time a big dump file "core.xxxx" in /var/opt/omi/run eventually eating up all disk space.

Investigations led me to SCXCoreProviderModule provider and its class SCX_Application_Server.

As it turned out SCX_Application_Server class tries to enumerate running application servers, and part of this process is finding out appserver's version.

For JBoss it is done by executing "jbossbasepath/bin/standalone.sh -version" and extracting the version string from the last response line, and major version number from this string.

But on the servers with issue this command returns error, the provider code tries to tokenize response an convert needed token to long type - here comes an exception, provider crashes leaving the dump.

The "standalone.sh -version" execution error is "bind failed: Address already in use", it's something about jboss default configuration and trying to use already used resources.

Possibly the problem could be resolved by reconfiguration jboss but it is the production system and most unlikely admins will do changes.

And we do not need to monitor java applications, so it's desirable to solve the problem on the scom side.

So the question is: can the application server monitoring functions be disabled at all?

PS

SCOM 2019 UR3

There are no java monitoring management packs installed on scom.

The problem is reproduced every time I try to call this class manually:

winrm.cmd e http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Application_Server?__cimnamespace=root/scx  -r:https://jbossserver:1270/wsman -auth:basic -skipCACheck -skipCNCheck -skipRevocationcheck -encoding:utf-8 -format:pretty -username:yyyyyyyy -password:xxxxxx