Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why are Eclipse-based CaliberRM clients unable to view Requirements?

Why are Eclipse-based CaliberRM clients unable to view Requirements?


Why are Eclipse-based CaliberRM clients unable to view Requirements?



Eclipse-based CaliberRM clients throw errors or fail to display anything when attempting to view CaliberRM Requirements. The Eclipse log (a file named ".log" in the Eclipse workspace) shows an error stack like one of the following:

java.lang.ArrayIndexOutOfBoundsException: 25970
at com.starbase.caliber.attribute.UDAListValue.(UDAListValue.java:217)
at com.starbase.caliber.attribute.UDAList.(UDAList.java:41)
at com.starbase.caliber.attribute.AttributeManager.createAttribute(AttributeManager.java:108)


java.lang.RuntimeException: java.lang.NullPointerException
at com.starbase.caliber.attribute.AttributeManager.createAttributeValue(AttributeManager.java:181)
at com.starbase.caliber.Requirement.convertSystemAttributeValue(Requirement.java:1745)
at com.starbase.caliber.Requirement.(Requirement.java:188)
at com.starbase.caliber.RequirementManager.getFromServer(RequirementManager.java:695)
at com.starbase.caliber.RequirementManager.get(RequirementManager.java:428)

Due to the common underlying code, this issue can be observed in the CaliberRM for Eclipse client, the CaliberRM view available in Caliber DefineIT, and the CaliberRM plugin for Eclipse-based releases of Together.


There is a defect in the CaliberRM 2006 Client Hotfix 39c (file version 9.0.934). In this build, editing any single-selection list attribute (whether a User Defined Attribute or a system attribute like "Requirement Status") may cause an invalid index value to be applied to one of the attribute"s available options. These invalid index values in turn cause critical faults in any SDK application that attempts to retrieve a Requirement containing that attribute.


The solution is to use an unaffected build of CaliberRM Client, such as the original client build (version 9.0.847), Hotfix 28c (version 9.0.910), or Hotfix 43c (9.0.945), to and open the affected attribute for editing, then close the edit window without making any changes. The Client will refresh the underlying index values and thus resolving the errors, even though the data is left intact.

The problem attribute should be one assigned to the types of Requirements throwing the error in the CaliberRM for Eclipse, DefineIT, or Together client. This should help localize the issue to one or a few possible attributes.

If all Requirements are affected, then the problem most likely lies with one of the system attributes and not with a UDA.

If you are not certain which attribute is the cause and cannot narrow down to a few suspects, the best course of action is simple to sort your list of UDAs by type and open and close each single-selection list UDA in turn, then address the two system attributes. Even on a large database this procedure should only take a few minutes at most; it is potentially faster than attempting to deduce which attributes could be the cause.

Old KB# 16296


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:32
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.