Jazz Library Workaround: In configuration management scenarios, indexing of selection resources fails with an lqe.BatchWriter error
Author name

clm,elm,jazz-reporting-service

Thu, 05 May 2016
5 min read
0

Workaround: In configuration management scenarios, indexing of selection resources fails with an lqe.BatchWriter error

Author: Keith Wells, Patti Hiscock
Last Updated: December 2015
Build Basis: Lifecycle Query Engine 6.0.1

Problem Summary

During Lifecycle Query Engine (LQE) indexing of a Tracked Resource Set (TRS) feed that contains configuration managed resources, if duplicate selections are encountered, batch processing of the selection resources fails, and an lqe.BatchWriter error is generated.

Problem

In a configuration management scenario, the Quality Management (QM) application is sending duplicate selection resources in their TRS feeds, and during LQE indexing, some of these selections might not be saved in the relational database table.

In version 6.0, selection resources were moved from the LQE index to a separate relational database table to improve query performance. In version 6.0.1, the process was further refined so that selections to be added to the selections database table are batched. However, if one duplicate selection is found during the batch processing, then the entire operation is voided.

You might encounter this situation if you added a data source with configuration managed resources and the TRS feed contains duplicate selections. If this event does occur, you might not see any selection resources in the LQE query results.

Workaround

The administrator can change the selection storage location from relational database table to Jena TDB, a triple store database.
Note: Because the volume of selection resources in configurations can be huge, changing the storage location to Jena TDB might lead to other performance concerns.

  1. In the Lifecycle Query Engine Administration page navigation, under Configuration, click Advanced Properties.
  2. On the Advanced Properties page, click Show Internal.
  3. In the Internal Properties Configuration section, click Edit.
  4. Scroll down to the Indexing section of the page, and in the Selections Storage Location list, choose Main TDB Index; then click Save.

Related Information

The following link points to the related information:

Copyright © 2015 IBM Corporation

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Thu, 05 May 2016