This test monitors the index queue and promptly alerts administrators if the count of pending tasks in the queue keeps increasing. This way, the test points administrators to a probable index processing bottleneck, prompts them to investigate the reasons for the same, and enables them to arrive at the appropriate corrective action. Based on performance results reported by the test, if administrators decide to rebuild the index to clear the bottleneck, they can use the test to figure out if any re-indexing is already in progress. The test additionally reports the time taken for the last indexing/reindexing, and thus indicates if re-indexing is slow. Detailed diagnostics also reveal the precise task that was last re-indexed and is the probable cause for the indexing slowness.

This page depicts the default parameters that need to be configured for the ConfluIndexTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• In the JMX REMOTE PORT text box, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the catalina.bat file in the <<ATLASSIAN_CONFLUENCE_INSTALL_DIR>>\confluence\bin directory.

• If JMX requires authentication only (but no security), then ensure that the USER and PASSWORD parameters are configured with the credentials of a user with read-write access to JMX. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• The JNDINAME is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same.

• Specify the duration (in seconds) within which this test should wait from a response from Atlassian Confluence, in the TIMEOUT text box. The default is 10 seconds.

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.