Troubleshooting the sensor

This topic describes common problems that occur with the JBoss sensor and presents solutions for those problems.

JBossVersionSensor does not start

Problem
The JBossVersionSensor does not start.
Solution
  • Go to http://ipaddress:webport/jmx-console and scroll through the console to see if the JBoss server JMX console is enabled.
  • Ensure that lsof works properly.

JBoss libraries not found

Problem
When you run the sensor, the JBoss libraries not found message is displayed.
Solution
Ensure that the JBoss JAR files for your JBoss server version are in the dist directory, and that read access is enabled for User.

Some JDBC dependencies are not created between a JBoss server and database servers

Problem
TADDM discovers both the JBoss server and a related database server but does not create a relation between them. Such a relation is based on the JDBC connection properties that are defined on the application server.
Solution
The problem might be a result of one of the following issues:
  • The dependencies are created by the JDBCDependencyAgent that runs in the Dependency topology agent group. Ensure that the agent is run after the discovery of the JBoss servers.
  • The JDBCDependencyAgent processes only the recently discovered application servers. If some dependencies are still missing after the agent has run, rediscover the JBoss servers, and wait for the topology agents to run again.
  • Ensure that the database server is one of those that supports the creation of transactional dependencies between it and the JBoss application server. The following databases are supported:
    • Oracle
    • IBM® DB2®
    • Microsoft SQL Server
    • Sybase

JBossVersionSensor fails with the error message "CTJTD0030E An error occurred while executing ./run.bat -V".

Problem
JBossVersionSensor fails and the following error message can be found in logs:
  • For JBoss AS on Windows:
    ERROR sensor.JBossVersionSensor - CTJTD1573E An error occurred while executing ./run.bat -V: com.collation.platform.os.OsException: '.' is not recognized as an internal or external command,.
  • For JBoss AS on Linux:
    ERROR sensor.JBossVersionSensor - CTJTD1573E An error occurred while executing ./run.sh -V: com.collation.platform.os.OsException: '.' is not recognized as an internal or external command,.
Solution
JBossVersionSensor was unable to detect the version of JBoss AS because the full path to the run.bat or run.sh script was not provided before the application server was started. Copy the required JBoss libraries (JAR files) to the $COLLATION_HOME/lib/jboss directory to enable a version detection via JMX. Without these libraries, the JBoss server sensor does not store any model objects. See the Prerequisites section to learn which libraries must be copied.