Troubleshooting the sensor

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

A managed domain is duplicated

Problem: When many hosts that belong to the same JBoss managed domain are discovered simultaneously for the first time, duplicates might be created in the Agile Service Manager database.
Solution: Run a discovery of the JBoss domain again. Duplicates are merged.; To avoid such problem in future, discover a host, which acts as a JBoss domain controller first, and then run a discovery of domain members.

Deployments, or JDBC data sources, or both, are not discovered

Problem: Not all deployments, or JDBC data sources, or both, are present in the Agile Service Manager database after some hosts that belong to a managed JBoss domain are discovered.
Solution: Although JBoss AS propagates deployments and JDBC data sources across a managed domain automatically, the comprehensive information about them might be available only on a host that acts as a JBoss domain controller. To get a complete picture of a JBoss environment, all hosts, which constitute the domain must be discovered, especially the domain controller.

Modules of an EAR deployment are not discovered

Problem: A Java Platform, Enterprise Edition application in a form of an enterprise archive (EAR) is deployed to JBoss AS, but the sensor does not discover modules of the application.
Solution: Configure the sensor so that the META-INF/application.xml descriptor is collected. See Configuring the sensor.

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

Problem

Agile Service Manager discovers both the JBoss server or server group and a related database server but it does not create a relation between them. Such relation is based on 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 AS.
The JDBCDependencyAgent processes only the recently discovered application servers. If some dependencies are still missing after the agent has run, rediscover the JBoss environment, and wait for the topology agents to run again.

The JBoss Application Server 7 sensor does not start

Problem

Although JBoss AS is started, the JBoss 7 Application Server sensor is not triggered.

Solution

If a JBoss stand-alone server, or a JBoss host controller listens only on a loopback address and the com.collation.platform.os.ignoreLoopbackProcesses=true property is set in Agile Service Manager, the server process is ignored, and the sensor does not start. Change the value of the property to false for the JBoss host, which was not discovered, in the following way:

com.collation.platform.os.ignoreLoopbackProcesses.x.x.x.x=false

where x.x.x.x is the IP address of the discovery target.

JBoss servers belonging to a JBoss domain are getting over merged or only JBoss server of single host is saved

Problem

When discovery is run for multiple members of a single JBoss domain server, then after discovery ends, JBoss servers belong to only one of the multiple JBoss host discovered are saved.

Solution

The problem is resolved with following conditions:

Only one discovery server at a time should be running JBoss7Sensor for targets that are members of a single JBoss Domain server. In case of load balanced discovery, this means that user should put all their JBoss target which are under a single JBoss domain server in same scope set to use this sensor, i.e. the targets should not be in different scope sets of a scope group to prevent them being run parallelly in load balanced discovery

CustomTemplateSensor defined on JBoss7Sensor causes JBoss server over merges

Problem

When we discover JBoss Server deployed in domain mode and profile includes a CustomTemplateSensor in which a template is defined which takes JBossDomain object from a JBoss7Sensor and produces same type enriched object, then over merging of JBoss Server occurs. Only JBoss servers belonging to one random host are saved.

Solution

The problem is resolved with following conditions:

For a target, both sensors - JBoss7Sensor and JBossSensor should not get invoked. They may be in discovery profile but if both gets invoked then over merging will still occur in case of CustomTemplateSensor defined on JBoss7Sensor result