Showing results for 
Search instead for 
Did you mean: 
Create Post

Add Support for Wildfly - JMX Monitoring

Add Support for Wildfly - JMX Monitoring


we migrate part of our production system from Jboss 7 to Wildfly 8 and im be very surprised when i can't connect this Application Server to monitoring using jmx.

I believe that's a problem with specific configuration not with a big rebuilding you product.

So if is possible please add this Application Server to the SAM.

When we use jboss 7.1.1 i use this article to configuration connection between  Monitoring and Jboss :

I'm trying do this same with Wildfly 8.1 but for some reason i can't connect to this version of Jboss Server.

I create a Support Request for this issue [ Case # 667602 - JMXBrdige monitoring jboss8 ( wildfly ) ], and Kevin directed me here.

So someone write this article so it's very possible that you can update them if you found any method to connect to this AS using remoting-jmx.

When i try using jconsole it's working. I have only problem with JSL connection  ( your jmx brdidge ) even when I added a new library.

My jsl.conf file:


APM_HOME =C:\Program Files (x86)\SolarWinds\Orion\APM\



appname = SolarWinds JMX Bridge

servicename = SWJMXBridgeSvc

displayname = SolarWinds JMX Bridge

servicedescription = SolarWinds JMX Bridge Service

stringbuffer = 16000










params = 4

param00 = -cp

param01 = %APM_HOME%\jmxbridge\SolarWinds.JMX.Bridge.jar;%APM_HOME%\jmxbridge\lib\log4j-1.2.16.jar;%APM_HOME%\jmxbridge\lib\wlclient.jar;%APM_HOME%\jmxbridge\lib\wljmxclient.jar;%APM_HOME%\jmxbridge\lib\remoting-jmx-2.0.0.Final.jar;%APM_HOME%\jmxbridge\lib\wildfly-remoting-8.1.0.Final.jar;%APM_HOME%\jmxbridge\lib\jboss-remoting-4.0.3.Final.jar;%APM_HOME%\jmxbridge\lib\jboss-logging-3.1.4.GA.jar;%APM_HOME%\jmxbridge\lib\xnio-api-3.2.2.Final.jar;%APM_HOME%\jmxbridge\lib\xnio-nio-3.2.2.Final.jar;%APM_HOME%\jmxbridge\lib\jboss-sasl-1.0.4.Final.jar;%APM_HOME%\jmxbridge\lib\jboss-marshalling-1.4.6.Final.jar;%APM_HOME%\jmxbridge\lib\jboss-marshalling-river-1.4.6.Final.jar;%ProgramFiles%\Java\jdk1.6.0_45\lib\tools.jar

param02 = -Denv.allusersprofile=%ALLUSERSPROFILE%

param03 = com.solarwinds.jmxbridge.Service

Error which i found in logs:

[bridgeUrl=http://localhost:9191/jmxbridge, serverUri=service:jmx:http-remoting-jmx://] Exception:System.Web.Services.Protocols.SoapException: tried to access method; from class org.jboss.remoting3.remote.HttpUpgradeConnectionProvider

at SolarWinds.JMX.QueryServiceClient.JmxBridgeSession.ConvertConnectionException(SoapException ex)

at SolarWinds.JMX.QueryServiceClient.JmxBridgeSession.Connect(String serviceAddr, String username, String password)

at SolarWinds.APM.Probes.JMX.JmxSessionCache.GetConnection(String bridgeUrl, String serverUri, String userName, String password)

at SolarWinds.APM.Probes.JMX.JmxCommunicationManager.Connect(String bridgeUrl, String serverUri, UserNamePasswordCredential credential, IJobResultStatus resultStatus)

2014-08-12 15:20:29,623 [STP Pool:273 Thread #0] [C1694] DEBUG SolarWinds.APM.Probes.ProbeExecutors.RegularBatchExecutor - Component probe

I'm authorized using login and password from AD which working when i connect using jconsole but not when i using jmx from SAM.

I think that was a good ideas add a full support for this kind of product  ( jboss/wilfdly ).


Level 12

Since SAM 6.2.1 there are deployed client libraries for 3 versions of Jboss library - 8.2, 7.4, 7.1.1.

But because they are not fully compatible - with libraries from ver. 7 we are not able to poll WildFly 8.

Client libraries from WildFly 8.2 doesn't poll JBoss 7.1.1 ...

So you have to choose, which version will JMX Bridge on your poller server support.

Jo have to change accordingly commenting in JMX bridge config file "c:\Program Files (x86)\SolarWinds\Orion\APM\jmxbridge\jsl\jsl.ini"


With default JBoss settings should mBeans "Custom URL Format:" look in this way

for JBoss 7.x :    service:jmx:remoting-jmx://${IP}:9999

for WildFly 8.2:  service:jmx:http-remoting-jmx://${IP}:9990

The port number can be different if you use a different configuration.

On the JBoss side you will need change configuration in a similar way, as described here:

JMX connections to JBoss AS | Planet JBoss Developer
or here Using jconsole to connect to JMX on AS7 | JBoss Developer

Product Manager
Product Manager

Tracking via SAM-8708

Community Manager
Community Manager
Status changed to: What We're Working On
Product Manager
Product Manager
Status changed to: Implemented

Updates in SAM 2020.2 allow for monitoring of recent Wildfly versions! See the release notes to see details. 

SAM 2020.2 is GA today!