JBoss AS

Supported Versions

Currently supported versions are JBoss 4.0 or newer and Wildfly.

Sensor (Data Collection)

Tracked Configuration

  • Version
  • Home
  • Deployments

    • Web
    • EJB
  • Sockets


  • Servlets
  • Requests, Response Times
  • Sessions
  • Connectors
  • EJB Pool
  • Datasources
  • Connection Pools (available only for JBoss 4)
  • Thread Pools (available only for JBoss 4)

Health Signatures

Health Description
Connector Errors Average errors on connector too high
Datasource Connections Connections on datasources are about to run out
Connection Pool used connections ConnectionPool is running out of connections (available only for JBoss 4)
Thread Pool used threads ThreadPool is running out of threads (available only for JBoss 4)


Required Configuration in Wildfly

Instana currently cannot automatically enable the Wildfly statistics it uses.

To have Wildfly collect the metrics Instana then uses please enable statistics for undertow and datasources like this:

<subsystem xmlns="urn:jboss:domain:undertow:3.0" statistics-enabled="true">

<datasource jta="true" jndi-name="java:jboss/datasources/DemoDS" pool-name="DemoDS" enabled="true" statistics-enabled="true">

JBoss Naming

Instana is naming a JBoss using the jboss node name that can be specified using


Sensor Configuration

On some legacy JBoss versions, calls to retrieve EJB deployments data can cause various error due to bugs.
EJB deployments data retrieval is enabled by default, but in case these bugs happen or if it’s just unnecessary, it can be disabled with the monitor-ejb-deployments flag:

  monitor-ejb-deployments: false

in the configuration file <agent_install_dir>/etc/instana/configuration.yaml.