IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting administration tasks and tools > Troubleshooting Common Event Infrastructure > Problems when receiving or querying events

Event group with extended data elements contains no events

I have defined an event group that specifies extended data element predicates, but queries on the event group do not return the expected events.

Cause

The event data might be valid XML but not conform with the Common Base Event specification. This can cause unexpected results without any error messages.

Consider an event with the following content:

<?xml version="1.0" encoding="ASCII"?>
<!-- Event that will match the XPath expression CommonBaseEvent
        [@globalInstanceId] -->
<CommonBaseEvent
        xmlns:xsi="http://www.w3.org/TR/xmlschema-1/"
        xmlns:="http://www.ibm.com/AC/commonbaseevent1_0_1"
        version="1.0.1"
        creationTime="2005-10-17T12:00:01Z"
        severity="10"
        priority="60"
    >
    <situation categoryName="RequestSituation">
        <situationType xsi:type="RequestSituation"
            reasoningScope="INTERNAL"
            successDisposition="Suceeded"
            situationQualifier="TEST"
        />
    </situation>
    <sourceComponentId
        component="component"
        subComponent="subcomponent"
        componentIdType="componentIdType"
        location="localhost"
        locationType="Hostname"
        componentType="sourceComponentType"
    />
    <extendedDataElement name="color" type="string">
        <values>red</values>
    </extendedDataElement>
</CommonBaseEvent>

This event contains a single extended data element with a single child element.

Now consider an event group definition configured with the following XPath event selector string:

CommonBaseEvent[extendedDataElements[@name='color' and @type='string' 
        and @values='red']]

This event selector fails to match the event because the XML definition of the event contains a misspelling. In the event data, the extendedDataElements element is misspelled as extendedDataElement. Because this is well-formed XML, it does not cause an error; instead, it is treated as an any element, which is not searchable.

Remedy

Make sure the XML data for submitted events conforms to the Common Base Event specification.

Problems when receiving or querying events