Troubleshooting the sensor

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

Duplicate WebLogic domains might be created

Problem: Duplicate WebLogic domains might be created when a host of an admin server of a WebLogic domain has many IP addresses.

Solution: To remove the duplicates, make sure that the WebLogicDomainConsolidationAgent is run after the discovery of WebLogic domains.

WebLogic sensor does not start

Problem

The WebLogic sensor does not start.

Solution

Perform the following actions:

For each version of the WebLogic server, copy the JAR files from the WebLogic installation to the $COLLATION_HOME/lib/weblogic/VERSION directory. Verify the sensor configuration in the $COLLATION_HOME/etc/discover-sensors/WeblogicVersionSensor.xml file.
Verify that the WebLogic Server port and IP address are reachable and that the WebLogic server uses the Java™ Management Extensions (JMX) communication protocol that is supported by Agile Service Manager. Configure the com.collation.agent.weblogic.protocols property in the collation.properties file.
If the WebLogic Sensor starts when using the local host address (127.0.0.1) and fails or discovers nothing, set the value of the following property in the collation.properties file to true:
```
com.collation.platform.os.ignoreLoopbackProcesses=true
```

WebLogic sensor fails

Problem: The WeblogicServerVersion sensor fails.
Solution: Copy the required WebLogic JAR files to the Agile Service Manager installation. Alternatively, the authentication information is missing or incorrect.

Sensor fails in remote server

Problem

The following error is in the local-anchor*.log, which typically means that the WebLogic security authentication information is missing or incorrect:

Sensor failed in remote server:
An error occurred in the null sensor.

Solution

Ensure that you have the correct security authentication information. The Agile Service Manager server requires the WebLogic system login name and the password that is used to log in to the WebLogic Product Console.

Message states that nothing exists to be discovered

Problem

The WebLogic sensor runs and completes successfully with the following message:

There was nothing to be discovered.

Solution

This message occurs when you are discovering a WebLogic Application Server. Although this situation is not a problem, ensure that the WebLogic sensor runs against the WebLogic Admin Server.

Sensor fails with WebLogic 10.x

Problem: The WeblogicServerVersion sensor fails only with WebLogic 10.x.
Solution: WeblogicVersionSensor uses an external command to identify the version of WebLogic. On some WebLogic 10.x installations, this command returns an unexpected empty string which causes the WeblogicVersionSensor to fail.; As a workaround, use the JAR files from a WebLogic 9.x installation. WebLogic 9.x JAR files work with WebLogic 10.x.

WebLogic sensor fails to discover WebLogic Administration Server

Problem: While attempting discovery of a WebLogic Administration Server, the WebLogic sensor fails as a result of a non-functioning DNS.
Solution: Discoveries involving the sensors related to WebLogic Administration Servers must have working DNS. As a workaround, change com.collation.platform.os.disableRemoteHostDNSLookups to true, and ensure that the Agile Service Manager server always has the correct DNS search path.

WebLogic sensor fails due to timeout

Problem

The WebLogic sensor fails due to timeout.

Solution

Increase value of the com.collation.discover.agent.NAME timeout property in the collation.properties file, where NAME represents the name of the sensor that is configured in the XML file in the $COLLATION_HOME/etc/discover-sensors directory. The following examples show how to code this property:

com.collation.discover.agent.WeblogicSensor2.timeout=7200000
com.collation.discover.agent.WeblogicSensor.timeout=7200000

WebLogic sensor fails after migration

Problem: The WebLogic sensor fails after migration.
Solution: Ensure that you run the $COLLATION_HOME/bin/template-upgrade.sh script.

Sensor fails due to T3 problem

Problem

The WeblogicServerVersion sensor fails due to inaccessible T3 protocol.

Solution

In some installations, the T3 protocol might be blocked. In this case, configure the WebLogic Servers to use the http protocol, and configure the WeblogicSensors to use http as well.

For example:

com.collation.agent.weblogic.protocols=t3,http

WeblogicServerVersion fails due to timeout when issuing a version command

Problem

The weblogicServerVersion times out while issuing the version command. The problem can be due to the port being blocked by the firewall. The following example shows port number 6079 is blocked by a firewall:

2009-09-09 12:29:38,802 DiscoverManager
DiscoverWorker-11 WeblogicServerVersionSensor-169.70.70.100-6079 DEBUG
j2ee.WeblogicServerVersionAgent - Executing command: -cp
/opt/IBM/taddm/dist/lib/weblogic/10.0/weblogic.jar:/opt/IBM/taddm/dist/lib
/weblogic/10.0/webservices.jar:/opt/IBM/taddm/dist/lib/weblogic/10.0/wljm
xclient.jar -Duser.language=en -Duser.region=US weblogic.Admin -url
t3://169.70.70.100:6079 -username confadmin -password XXX VERSION 2009-09-09
12:29:39,133 DiscoverManager DiscoverWorker-11
WeblogicServerVersionSensor-169.70.70.100-6079 DEBUG util.OsCommand - Command
executed, capturing output 2009-09-09 12:33:03,526 DiscoverManager
DISCOVER_SENSOR_CLEANUP_DiscoverWorker-11
WeblogicServerVersionSensor-169.70.70.100-6079 DEBUG
j2ee.WeblogicServerVersionAgent - JavaCommand error
java.lang.InterruptedException at java.lang.Object.wait(Native Method) at
java.lang.Object.wait(Object.java:231) at java.lang.Thread.join(Thread.java:680)
at com.collation.platform.util.OsCommand.execute(OsCommand.java:411)

Solution

This sensor uses a protocol other than SSH for host access, the appropriate port needs to be open between the Agile Service Manager server and the target. In cases when a firewall prevents direct access from the discovery server to certain hosts or devices, you can specify a computer system that does have access to the hosts or devices to be an anchor host.

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

Problem

Agile Service Manager discovers both the WebLogic 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 WebLogic servers.
The JDBCDependencyAgent processes only the recently discovered application servers. If some dependencies are still missing after the agent has run, rediscover the WebLogic 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 WebLogic application server. The following databases are supported:
- Oracle
- IBM® DB2®
- Microsoft SQL Server
- Sybase

WebLogic sensor fails with error- "java.lang.OutOfMemoryError: Java heap space"

Problem

If a target machine has multiple WebLogic Servers running on different virtual IPs, Agile Service Manager might be given OutOfMemory error on running WebLogic sensors. The reason might be with WebLogic Sensors seeds which contains all the process list running on the system.

Some WebLogic process might have thousands of BindAddress and LogicalConnection objects resulting in the seed object occupying significant memory. If many WebLogic sensors are invoked, they create their separate copy of process list having the same data, resulting in increased memory consumption for the same data.

Solution

You can share the process list of same targets between seeds of different WebLogic sensors which helps in reducing the memory requirement by enabling the following properties in the collation.properties file:

com.collation.discover.WeblogicApplicationSeed.processlist.shared=true

com.collation.discover.WeblogicDomainSeed.processlist.shared=true

com.collation.discover.WeblogicLauncherSeed.processlist.shared=true

com.collation.discover.WeblogicServerSeed.processlist.shared=true

Their default value is false.

Weblogic over merging issue occurred due to wrong listenPort set by sensor in BindAddress

Problem

If SSL is enabled but the sslPort is not configured, by default it is set as 7002 by the sensor.

If the sslPort value is greater than listenPort value, listenPort value is set in BindAddress. Otherwise, the default sslPort value is set in BindAddress.

By default, the sslPort value is always less than the listenPort value due to which, this default value of sslPort (7002) is always set in BindAddress. This leads to overmerging.

Solution

To set correct listenPort of Weblogic in BindAddress, you must configure a collation to resolve this conflict :

com.ibm.cdb.discover.app.j2ee.weblogic.util.WeblogicUtilsModelObject.setBindPortToListenPort=true

The default value is false.

The possible values are true and false.